about summary refs log tree commit diff
path: root/app/workers
AgeCommit message (Collapse)Author
2017-04-04Moving the queue_at into the workerKurtis Rainbolt-Greene
2017-04-04Replacing the broadcast method with the one defined in the feed managerKurtis Rainbolt-Greene
2017-04-04By pushing this into a worker we can reduce the amount of time the feed ↵Kurtis Rainbolt-Greene
manager using workers eat up a connection
2017-04-05Remove PuSH subscriptions when delivery is answered with a 4xx errorEugen Rochko
2017-04-04Spawn FeedInsertWorker to deliver status into personal feedEugen Rochko
2017-04-04Reduce number of items in feeds, optimize regeneration worker slightly,Eugen Rochko
make regeneration worker unique, (only schedule/execute once at a time)
2017-04-04Move OStatus processing back into default queueEugen Rochko
2017-04-04Only call regeneration worker after first login after a 14 day breakEugen Rochko
2017-04-04Separate background jobs into different queues. ATTENTION: new queue "pull"Eugen Rochko
must be added to the Sidekiq invokation in your systemd file The pull queue will handle link crawling, thread resolving, and OStatus processing. Such tasks are more likely to hang for a longer time (due to network requests) so it is more sensible to not make the "in-house" tasks wait for them.
2017-04-03Make default admin UI page reports. Add admin UI for creating a domain blockEugen Rochko
2017-03-30Import feature for following/blocking lists (addresses #62, #177, #201, #454)Eugen Rochko
2017-03-04Add digest e-mailsEugen Rochko
2017-02-14Disable PuSH for blocked domainsEugen Rochko
2017-02-12Adding more unit tests. Fixing Salmon slaps XMLEugen Rochko
2017-02-12Take out private toot distribution out of PuSH againEugen Rochko
2017-02-11Make PuSH only distribute to subscriptions that match follower domainsEugen Rochko
Allow PuSH to distribute private toots with that condition
2017-02-11After FollowService, re-fetch remote account asynchronously, do nothingEugen Rochko
if account lock info was up to date, otherwise re-do the FollowService with now updated information
2017-02-11Make follow requests federateEugen Rochko
2017-02-05Preheat status cacheEugen Rochko
2017-01-29API for apps to register for push notificationsEugen Rochko
2017-01-24Make blocks create entries and unfollows instantly, but do the clean upEugen 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-23Move merging/unmerging of timelines into background. Move blocking intoEugen Rochko
background as well since it's a computationally expensive
2017-01-20Fix #463 - Fetch and display previews of URLs using OpenGraph tagsEugen Rochko
2017-01-05Improve background jobs params and error handlingEugen Rochko
2017-01-03Fix accidental distribution of hidden stream entries to PuSH subscribersEugen Rochko
2016-12-29Add API for retrieving blocked accountsEugen Rochko
2016-12-19Adding 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-19Make unfavouriting async to prevent timeout errors from leaving orphaned ↵Eugen Rochko
records behind
2016-12-18Removing external hub completely, fix #333 fixing digit-only hashtags,Eugen Rochko
removing web app capability from non-webapp pages
2016-12-12Restoring old async behaviour of thread resolving as it proved to be more robustEugen Rochko
2016-12-11Thread resolving no longer needs to be separate from ProcessFeedService,Eugen Rochko
since that is only ever called in the background
2016-12-06Add filters for suspended accountsEugen Rochko
2016-12-02Fix #329 - avatar errors no longer prevent remote accounts from being savedEugen Rochko
(without avatar). Also improved search position of exact matches
2016-11-30Track successful PuSH deliveriesEugen Rochko
2016-11-29Delete statuses asynchronously but provide instant feedback in the APIEugen Rochko
2016-11-29Adding rack timeout of 30sec, PuSH jobs moved to push queue so theyEugen Rochko
can be processed separately
2016-11-29Fix URLs in inline-rendered XMLEugen Rochko
2016-11-28Fix setting of confirmed=true on successful confirmationEugen Rochko
2016-11-28More logging to ConfirmationWorkerEugen Rochko
2016-11-28Adding backtracing to Salmon/Processing workersEugen Rochko
2016-11-28Adding embedded PuSH serverEugen Rochko
2016-11-22Remove unneeded indices, improve error handling in background workers, don't ↵Eugen Rochko
needlessly reload reblogged status, send Devise e-mails asynchronously
2016-11-18Move Salmon processing to background as well as PuSHEugen Rochko
2016-11-15Fix rubocop issues, introduce usage of frozen literal to improve performanceEugen Rochko
2016-11-15Delegate processing of incoming PuSH data to background workersEugen Rochko
2016-11-08Improve feed regenerationEugen Rochko
2016-10-05Move PubSubHubbub pinging to a background workerEugen Rochko
It can take as much as 0.5s if not longer to complete
2016-09-29Improve code styleEugen 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-03-26Moving Salmon notifications to background processing, fixing mini-profilerEugen Rochko
behaviour with Turbolinks enabled, optimizing Rabl for production
generated by cgit-pink (git 2.37.1) at 2024-11-05 15:57:43 +0000