| Age | Commit message (Collapse) | Author |
|---|
|
|
|
show stuff for remote users. Subscriptions, groups, roles, etc are all on profiles now so go ahead and use em.
|
|
|
|
File_redirection::lookupWhere()'s HTTP handling -- when we get a 204 on a HEAD, double-check it by re-running as a GET. yfrog.com returns a 204 incorrectly for this case.
|
|
|
|
|
|
Conflicts:
actions/apistatusesshow.php
actions/apitimelineuser.php
|
|
added a chance to whitelist sites that don't show discovery info but do have oEmbed API endpoints, and to provide alternate APIs for some common services.
Newly supported:
- TwitPic: added a local function using TwitPic's API, since the oohembed implementation for TwitPic produced invalid output which Services_oEmbed rejects. (bug filed upstream)
Tweaked...
- Flickr: works, now using whitelist to use their endpoint directly instead of going through oohembed
- Youtube: worked around a bug in Services_oEmbed which broke the direct use of API discovery info, so we don't have to use oohembed.
Not currently working...
- YFrog: whitelisting their endpoint directly as the oohembed output is broken, but this doesn't appear to work currently as I think things are confused by YFrog's servers giving a '204 No Content' response on our HEAD checks on the original link.
|
|
thumbnail_url entry in the return data. This fixes thumb saving for Flickr photo references.
|
|
listing attachments/thumbs
|
|
defaulting to 100x75.
This is used as the max thumb width/height for oEmbed requests (replacing the old default of 500x400 which was more suitable for the lightbox).
|
|
|
|
attachments system. Currently hardcoded to 100x75, needs aspect-sensitivity etc.
|
|
|
|
they're really oembedable. HTML-y things now excluded properly.
|
|
|
|
prolific posters
The old code attempted to compare the value of the notice.created field against now() directly, which tends to explode in our current systems. now() comes up as the server/connection local timezone generally, while the created field is currently set as hardcoded UTC from the web servers. This would lead to breakage when we got a difference in seconds that's several hours off in either direction (depending on the local timezone). New code calculates a threshold by subtracting the number of seconds from the current UNIX timestamp and passing that in in correct format for a simple comparison. As a bonus, this should also be more efficient, as it should be able to follow the index on profile_id and created.
|
|
adjusting the PEAR error handling temporarily around MIME_Type_Extension usage.
|
|
the "fullname (nickname)" vs "nickname" logic and allows for localization of the parentheses in a common place.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* superfluous whitespace removed.
|
|
Four new events for when roles are granted or revoked.
|
|
lowest bytes reserved" error in Memcache > 3.0.3
|
|
|
|
Conflicts:
actions/apioauthauthorize.php
lib/apioauthstore.php
|
|
request tokins with OAuth client applications and profiles.
|
|
* moved some translator comments that were not directly above the line with the message to the correct location.
* i18n for UI text.
* superfluous whitespace removed.
|
|
by site owner in router setup.
I've consolidated the checks for which user to use for single-user mode into User::singleUser(), which now uses the configured nickname by preference, falling back to the site owner if it's unset.
This is now called consistently from the places that needed to use the primary user's nickname in routing setup.
Setting $config['singleuser']['nickname'] should now work again as expected.
|
|
back to (profile_id, application_id). I think we can get away without
a DB change by only issuing one anonymous access token per user.
|
|
small DB tweak. Oauth_application_user needs to have the primary
compound key: (profile_id, application_id, token).
http://status.net/open-source/issues/2761
This should also make it possible to have multiple access tokens
per application.
http://status.net/open-source/issues/2788
|
|
|
|
|
|
|
|
|
|
Doesn't clear all possible cached entries, but this should get the ones that matter most: lookups by id, nickname, and alias. This should ensure that if a group name gets reused as a new group or alias, it should work properly.
There are some user-visible areas that aren't clear such as the 'top groups' lists on the GroupsAction sidebar; if a deleted group appears in those lists it'll go away within an hour when the cached query expires.
|
|
|
|
|
|
registration descriptions; now using the field max of 255 rather than $config['site']['textlimit'] as fallback if $config['application']['desclimit'] is unset or out of bounds.
|
|
updates (%1$s etc)
|
|
set of groups on registration; and/or to force posts by members of particular groups to be posted into those groups even if not explicitly mentioned. The posting feature requires a couple quick hook additions in core.
|
|
|
|
|
