| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2017-02-11 | Make follow requests federate | Eugen Rochko | |
| 2017-02-05 | Preheat status cache | Eugen Rochko | |
| 2017-01-29 | API for apps to register for push notifications | Eugen Rochko | |
| 2017-01-24 | Make blocks create entries and unfollows instantly, but do the clean up | Eugen Rochko | |
| in the background instead. Should fix delay where blocked person can interact with blocker for a short time before background job gets processed | |||
| 2017-01-23 | Move merging/unmerging of timelines into background. Move blocking into | Eugen Rochko | |
| background as well since it's a computationally expensive | |||
| 2017-01-20 | Fix #463 - Fetch and display previews of URLs using OpenGraph tags | Eugen Rochko | |
| 2017-01-05 | Improve background jobs params and error handling | Eugen Rochko | |
| 2017-01-03 | Fix accidental distribution of hidden stream entries to PuSH subscribers | Eugen Rochko | |
| 2016-12-29 | Add API for retrieving blocked accounts | Eugen Rochko | |
| 2016-12-19 | Adding some rescues to workers, e.g. don't fail removal job when status ↵ | Eugen Rochko | |
| can't be found in the first place (already removed) | |||
| 2016-12-19 | Make unfavouriting async to prevent timeout errors from leaving orphaned ↵ | Eugen Rochko | |
| records behind | |||
| 2016-12-18 | Removing external hub completely, fix #333 fixing digit-only hashtags, | Eugen Rochko | |
| removing web app capability from non-webapp pages | |||
| 2016-12-12 | Restoring old async behaviour of thread resolving as it proved to be more robust | Eugen Rochko | |
| 2016-12-11 | Thread resolving no longer needs to be separate from ProcessFeedService, | Eugen Rochko | |
| since that is only ever called in the background | |||
| 2016-12-06 | Add filters for suspended accounts | Eugen Rochko | |
| 2016-12-02 | Fix #329 - avatar errors no longer prevent remote accounts from being saved | Eugen Rochko | |
| (without avatar). Also improved search position of exact matches | |||
| 2016-11-30 | Track successful PuSH deliveries | Eugen Rochko | |
| 2016-11-29 | Delete statuses asynchronously but provide instant feedback in the API | Eugen Rochko | |
| 2016-11-29 | Adding rack timeout of 30sec, PuSH jobs moved to push queue so they | Eugen Rochko | |
| can be processed separately | |||
| 2016-11-29 | Fix URLs in inline-rendered XML | Eugen Rochko | |
| 2016-11-28 | Fix setting of confirmed=true on successful confirmation | Eugen Rochko | |
| 2016-11-28 | More logging to ConfirmationWorker | Eugen Rochko | |
| 2016-11-28 | Adding backtracing to Salmon/Processing workers | Eugen Rochko | |
| 2016-11-28 | Adding embedded PuSH server | Eugen Rochko | |
| 2016-11-22 | Remove unneeded indices, improve error handling in background workers, don't ↵ | Eugen Rochko | |
| needlessly reload reblogged status, send Devise e-mails asynchronously | |||
| 2016-11-18 | Move Salmon processing to background as well as PuSH | Eugen Rochko | |
| 2016-11-15 | Fix rubocop issues, introduce usage of frozen literal to improve performance | Eugen Rochko | |
| 2016-11-15 | Delegate processing of incoming PuSH data to background workers | Eugen Rochko | |
| 2016-11-08 | Improve feed regeneration | Eugen Rochko | |
| 2016-10-05 | Move PubSubHubbub pinging to a background worker | Eugen Rochko | |
| It can take as much as 0.5s if not longer to complete | |||
| 2016-09-29 | Improve code style | Eugen Rochko | |
| 2016-09-21 | Fix #24 - Thread resolving for remote statuses | Eugen 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-03-26 | Moving Salmon notifications to background processing, fixing mini-profiler | Eugen Rochko | |
| behaviour with Turbolinks enabled, optimizing Rabl for production | |||
| 2016-03-25 | Add link to github project to footer, move FanOutOnWriteService calls to | Eugen Rochko | |
| DistributionWorker. That isn't the heaviest service, yet, but gotta start somewhere | |||
 |
index : mastodon | |
| Plural Café fork of Mastodon/Glitch Social |
| about summary refs log tree commit diff |