| Age | Commit message (Collapse) | Author |
|---|
|
* twitter-facebook-mods:
Make Facebook plugin look for API key and secret before doing anything
Show global key and secret, if defined, in Twitter bridge admin panel
Remove double word from Twitter bridge README
- Have Twitter bridge check for a global key and secret if it can't
stupid mistake... let's not talk about this.
Updated some references to the long gnone "isEnclosure" function to the new "getEnclosure"
Update Facebook plugin README with info about new admin panel
Initial Facebook admin panel
Some wording / spelling fixes
- Make 'Sign in with Twitter' optional
Remove un-needed config variable for enabling/disabling Twitter integration
Initial Twitter bridge admin panel
Upgrade XML output scrubbing to better deal with newline and a few other chars
|
|
|
|
"getEnclosure"
|
|
|
|
|
|
|
|
its descendants. Was breaking notice URL transfer, pulling a profile link by mistake.
|
|
When it sneaks in it can cause some very slow queries due to mismatches with the indexing.
Twitter removed 'since' support some time ago, and we've already removed it from the public timeline, so it shouldn't be missed.
|
|
mentioned in the replied message.
|
|
This reverts commit 19ec0e3a62d4c60d7e5581b4e38ec705650b1d18.
|
|
|
|
|
|
|
|
|
|
In a federated system, "@nickname" is insufficient to uniquely
identify a user. However, it's a very convenient idiom. We need to
guess from context who 'nickname' refers to.
Previously, we were using the sender's profile (or what we knew about
them) as the only context. So, we assumed that they'd be mentioning to
someone they followed, or someone who followed them, or someone on
their own server.
Now, we include the notice information for context. We check to see if
the notice is a reply to another notice, and if the author of the
original notice has the nickname 'nickname', then the mention is
probably for them. Alternately, if the original notice mentions someone
with nickname 'nickname', then this notice is probably referring to
_them_.
Doing this kind of context sleuthing means we have to render the
content very late in the notice-saving process.
|
|
|
|
|
|
|
|
|
|
|
|
Conflicts:
EVENTS.txt
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
otherwise if none labeled takes the first)
|
|
* 'testing' of gitorious.org:statusnet/mainline:
init_conversation.php script to copy old notice conversations into the conversation table
cache results of webfinger lookups
Parse an hcard for hints, if available
use new hcard method for webfinger
add hkit for hCard parsing
use new dedicated hcard method for Webfinger profile
Add an hcard action
|
|
|
|
|
|
* 'testing' of gitorious.org:statusnet/mainline:
OStatus: if no <link> available and no profileurl hint passed in, use object id if it's an HTTP(S) URL. Fixes profile link for Google accounts.
Tweak common_url_to_nickname to take the last path component; fixes pulling nicks from Google profile pages (path is "/profile/<nickname>")
Fix bug on subscribe/unsubscribe in profile lists. Bogus call to nonexisting profile->getProfile() was masked by DB_DataObject
|
|
|
|
nicks from Google profile pages (path is "/profile/<nickname>")
|
|
|
|
A dedicated hcard action for users. Our profile page includes
an hcard, but it's so full of other hcards that it's ambiguous which
one is the "real" one. So, this one make sense for meaning, "This is
my hcard."
|
|
* 'testing' of gitorious.org:statusnet/mainline:
Not sure how this ended up in wrong-cased dir...
OStatus: fix remote groups to work with new user_groups/local_groups split.
Conflicts:
classes/User_group.php
|
|
|
|
- fix <activity:subject> generation so we get the profile info (what's available so far)
- use id instead of nickname for group join/leave forms so we can join/leave remote groups
while the rest of the groups UI remains limited to local groups
(plugins are responsible for making sure remote notifications and permission checks are done)
- fix remote notification when joining group through OStatus's remote subscribe form
|
|
|
|
typing MixedCase nicknames (if browser saved this form, it would never work again until clearing the saved form data; very icky.)
|
|
|
|
plugin. Some shorteners have ended up inserting extra newlines when the string gets extracted from tidied HTML.
|
