aiden
/
mastodon
mirror of https://github.com/mastodon/mastodon
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
4,150 Commits
139 Branches
281 Tags
1.1 GiB
Commit Graph

12 Commits (7d16bb379d1463471faf264bb89e24d5b8a505ca)

Author SHA1 Message Date
Eugen Rochko 4e75f0d889 Hook up URL-based resource look-up to ActivityPub ()
Matt Jankowski 83435c49ea Clean up api/subscriptions controller ()
Eugen Rochko bafd22ecf4 Fix - Always respond with 200 to PuSH payloads () 
Fix  - Respond with 201 when Salmon accepted, 400 when unverified
Fix  - Correctly handle confirm_domain? for local accounts
Unify rules for extracting author acct from XML, prefer <email>, fall back
to <name> + <uri> (see also , )
Eugen Rochko 2cb3dc5e5a Update hub URL and re-subscribe if hub URL changes
Eugen Rochko c6b0311b86 Fix - Fetch remote accounts by URL from mentions 
Fetching atom extracted from FetchRemoteAccountService and FetchRemoteStatusService
into FetchAtomService. Mentions of the constant "http://activityschema.org/collection/public"
skipped as it's not a real URL/user.
Eugen Rochko 4bec613897 Fix - Thread resolving for remote statuses 
This is a big one, so let me enumerate:

Accounts as well as stream entry pages now contain Link headers that
reference the Atom feed and Webfinger URL for the former and Atom entry
for the latter. So you only need to HEAD those resources to get that
information, no need to download and parse HTML <link>s.

ProcessFeedService will now queue ThreadResolveWorker for each remote
status that it cannot find otherwise. Furthermore, entries are now
processed in reverse order (from bottom to top) in case a newer entry
references a chronologically previous one.

ThreadResolveWorker uses FetchRemoteStatusService to obtain a status
and attach the child status it was queued for to it.

FetchRemoteStatusService looks up the URL, first with a HEAD, tests
if it's an Atom feed, in which case it processes it directly. Next
for Link headers to the Atom feed, in which case that is fetched
and processed. Lastly if it's HTML, it is checked for <link>s to the Atom
feed, and if such is found, that is fetched and processed. The account for
the status is derived from author/name attribute in the XML and the hostname
in the URL (domain). FollowRemoteAccountService and ProcessFeedService
are used.

This means that potentially threads are resolved recursively until a dead-end
is encountered, however it is performed asynchronously over background jobs,
so it should be ok.
Eugen Rochko 608a2bfffc Upgrade to PubSubHubbub 0.4 (removing verify_token)
Eugen Rochko 87576e1ab1 Fixing atom feeds for accounts, adding tests that would catch such bugs in future
Eugen Rochko 10ba09f546 Upgrade to Rails 5.0.0.1
Eugen Rochko 35aafdba96 Ancestors and descendants of statuses
Eugen Rochko b640f35621 Writing out more tests, fixed some bugs
Eugen Rochko 0e8f59c16f Refactoring Grape API methods into normal controllers & other things