about summary refs log tree commit diff
path: root/app/services
AgeCommit message (Collapse)Author
2016-10-23Fix public channelEugen Rochko
2016-10-20Fix method return when rescuingEugen Rochko
2016-10-16Fix RemoveStatusService trying to send delete salmons on behalf of remote ↵Eugen Rochko
statuses
2016-10-14Fix duplication of media attachments when a remote status reblogs a local oneEugen Rochko
2016-10-14Fix remove status service sending salmonsEugen Rochko
2016-10-13No-op for Salmons without body, fail fast if Webfinger does not containEugen Rochko
all required resource links (profile page, salmon, atom feed, magic key)
2016-10-12Treat dfrn:owner like xmlns:author for Friendica compatibilityEugen Rochko
2016-10-12Improve Friendica support (but still not there yet)Eugen Rochko
2016-10-12Fix up a few exceptionsEugen Rochko
2016-10-10Fixing namespaces issueEugen Rochko
2016-10-10Fix namespace parsing in Atom feedsEugen Rochko
2016-10-10Use Account#find_remote method when possibleEugen Rochko
2016-10-10Don't return unsaved status from ProcessFeedServiceEugen Rochko
2016-10-10Adding test for ProcessFeedServiceEugen Rochko
2016-10-10Improve process feed serviceEugen Rochko
2016-10-10PuSH unsubscribe needs correct callback URLEugen Rochko
2016-10-10Fix default assumed object type (note->activity), make stream entry ↵Eugen Rochko
threaded? check aware of orphaned replies
2016-10-09Adding domain blocksEugen Rochko
2016-10-07Adding public timelineEugen Rochko
2016-10-06Fix #83 - if user cannot be found (or is self) throw error, don't return ↵Eugen Rochko
empty 200 This prevents the undefined profile from being opened in the first place on such an error
2016-10-06Better comparison of "local" domainEugen Rochko
2016-10-06Update OStatus2 to handle malformed Salmon without raising unexpected exceptionsEugen Rochko
2016-10-06Catch Paperclip errors on /api/v1/media, return early from update profile ↵Eugen Rochko
service if XML given is nil
2016-10-05Move PubSubHubbub pinging to a background workerEugen Rochko
It can take as much as 0.5s if not longer to complete
2016-10-05Fix typoEugen Rochko
2016-10-05Catching more exceptions that slipped through, removing AR logging fromEugen Rochko
production as it's very verbose and not very useful
2016-10-03Blocking will prevent e-mail notifications from blocked user, blocks in UIEugen Rochko
2016-10-03API for blocking and unblockingEugen Rochko
2016-10-03Adding a block model and filter mentions from blocked users (fix #60)Eugen Rochko
2016-10-02Small fixesEugen Rochko
2016-10-02Preparing feeds for better filteringEugen Rochko
2016-09-29Improve code styleEugen Rochko
2016-09-27Fix handling of multiple Link headers (that should not be a thing though)Eugen Rochko
2016-09-26Replace logo, fix #57 - delete/unreblog/unfavourite API, fix #45 - appEugen Rochko
registration API
2016-09-26Improve redirect handling in FetchAtomServiceEugen Rochko
2016-09-26Fix #54 - Fetch remote accounts by URL from mentionsEugen Rochko
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.
2016-09-22Handle remote account mentions a little better by trying a URL lookup in the dbEugen Rochko
2016-09-22Fix #51 - prevent duplicate attachments for remote statusesEugen Rochko
2016-09-21Fix #24 - Thread resolving for remote statusesEugen Rochko
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.
2016-09-20Upgrade to PubSubHubbub 0.4 (removing verify_token)Eugen Rochko
2016-09-20Separate PuSH subscriptions from following, add mastodon:push:refresh task,Eugen Rochko
respect hub.lease_seconds (fix #46)
2016-09-18Small rubocop offences removedEugen Rochko
2016-09-18Fix #43Eugen Rochko
2016-09-17Fix how other services used old FollowRemoteAccountServiceEugen Rochko
2016-09-17Improved error handling for FollowRemoteServiceEugen Rochko
2016-09-17Fix #41, debug #42Eugen Rochko
2016-09-12Adding a notification stack for error messagesEugen Rochko
2016-09-12Send "delete" Salmons to remote mentioned accounts on status removalEugen Rochko
Fixes #27
2016-09-12Fixing image upload limits, allowing webm, merge/unmerge events triggerEugen Rochko
timeline reload in UI, other small fixes
2016-09-10Merge and unmerge timelines on follow/unfollow, solves #21, #22Eugen Rochko