bea03b4553
Moving in the inline render
8 years ago
dd66bce930
I don't actually think we need that.
8 years ago
7d887cea4b
Moving the queue_at into the worker
8 years ago
4f2985cddc
Replacing the broadcast method with the one defined in the feed manager
8 years ago
de1bb4bd56
By pushing this into a worker we can reduce the amount of time the feed manager using workers eat up a connection
8 years ago
d2b7daf6bb
Remove PuSH subscriptions when delivery is answered with a 4xx error
8 years ago
fa2a1af90a
Spawn FeedInsertWorker to deliver status into personal feed
8 years ago
e60c473917
Reduce number of items in feeds, optimize regeneration worker slightly,
...
make regeneration worker unique, (only schedule/execute once at a time)
8 years ago
1484df2db5
Move OStatus processing back into default queue
8 years ago
7a56845060
Only call regeneration worker after first login after a 14 day break
8 years ago
8eca42b265
Separate background jobs into different queues. ATTENTION: new queue "pull"
...
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.
8 years ago
6ebe31e716
Make default admin UI page reports. Add admin UI for creating a domain block
8 years ago
244da78105
Import feature for following/blocking lists (addresses #62 , #177 , #201 , #454 )
8 years ago
0cb5a2a0a7
Add digest e-mails
8 years ago
94a6dfab3a
Disable PuSH for blocked domains
8 years ago
8550d32165
Adding more unit tests. Fixing Salmon slaps XML
8 years ago
79f3ee31df
Take out private toot distribution out of PuSH again
8 years ago
ffd58aad9d
Make PuSH only distribute to subscriptions that match follower domains
...
Allow PuSH to distribute private toots with that condition
8 years ago
1e66536797
After FollowService, re-fetch remote account asynchronously, do nothing
...
if account lock info was up to date, otherwise re-do the FollowService
with now updated information
8 years ago
59c8c2b28a
Make follow requests federate
8 years ago
efa4065029
Preheat status cache
8 years ago
9327d05bf7
API for apps to register for push notifications
8 years ago
ea8b548ee9
Make blocks create entries and unfollows instantly, but do the clean up
...
in the background instead. Should fix delay where blocked person
can interact with blocker for a short time before background job
gets processed
8 years ago
98660a76d9
Move merging/unmerging of timelines into background. Move blocking into
...
background as well since it's a computationally expensive
8 years ago
f748a91ec7
Fix #463 - Fetch and display previews of URLs using OpenGraph tags
8 years ago
a893746e5a
Improve background jobs params and error handling
8 years ago
0471207cc3
Fix accidental distribution of hidden stream entries to PuSH subscribers
8 years ago
2bc6e7c96e
Add API for retrieving blocked accounts
8 years ago
0f4c9d1124
Adding some rescues to workers, e.g. don't fail removal job when status can't be found in the first place (already removed)
8 years ago
b2945b025f
Make unfavouriting async to prevent timeout errors from leaving orphaned records behind
8 years ago
9d4f96f440
Removing external hub completely, fix #333 fixing digit-only hashtags,
...
removing web app capability from non-webapp pages
8 years ago
b7c2c5d81d
Restoring old async behaviour of thread resolving as it proved to be more robust
8 years ago
fb36684678
Thread resolving no longer needs to be separate from ProcessFeedService,
...
since that is only ever called in the background
8 years ago
7752662f97
Add filters for suspended accounts
8 years ago
211049ae59
Fix #329 - avatar errors no longer prevent remote accounts from being saved
...
(without avatar). Also improved search position of exact matches
8 years ago
a692318382
Track successful PuSH deliveries
8 years ago
d26b8f3cce
Delete statuses asynchronously but provide instant feedback in the API
8 years ago
3c1c2b0e06
Adding rack timeout of 30sec, PuSH jobs moved to push queue so they
...
can be processed separately
8 years ago
79075e1303
Fix URLs in inline-rendered XML
8 years ago
02da8fdcbe
Fix setting of confirmed=true on successful confirmation
8 years ago
bf7c9e826d
More logging to ConfirmationWorker
8 years ago
0cc5410e03
Adding backtracing to Salmon/Processing workers
8 years ago
b5ad0eb4ea
Adding embedded PuSH server
8 years ago
f07b0dc82f
Remove unneeded indices, improve error handling in background workers, don't needlessly reload reblogged status, send Devise e-mails asynchronously
8 years ago
fbaddca49e
Move Salmon processing to background as well as PuSH
8 years ago
e71b152d89
Fix rubocop issues, introduce usage of frozen literal to improve performance
8 years ago
a7332acba3
Delegate processing of incoming PuSH data to background workers
8 years ago
f1d2c46ded
Improve feed regeneration
8 years ago
3319473b2c
Move PubSubHubbub pinging to a background worker
...
It can take as much as 0.5s if not longer to complete
8 years ago
927333f4f8
Improve code style
8 years ago
4bec613897
Fix #24 - 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.
8 years ago
85b00d19b8
Moving Salmon notifications to background processing, fixing mini-profiler
...
behaviour with Turbolinks enabled, optimizing Rabl for production
9 years ago
8eeec389c1
Add link to github project to footer, move FanOutOnWriteService calls to
...
DistributionWorker. That isn't the heaviest service, yet, but gotta start
somewhere
9 years ago
Kurtis Rainbolt-Greene
Eugen Rochko