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
ca0757a6cf
Add account suspension
8 years ago
8d4ef0b6c3
Per-status control for unlisted mode, also federation for unlisted mode
...
Fix #233 , fix #268
8 years ago
23162b2893
Update hub URL and re-subscribe if hub URL changes
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
3fc7820d6e
Call NotifyService about remote reblogs
8 years ago
38025dfea3
Adding unified streamable notifications
8 years ago
b373fb0ff6
Catch validation errors in ProcessFeedService so that one failing entry wouldn't stop others from going through
8 years ago
d2029a8845
Don't create attachments if remote file cannot be fetched
8 years ago
e71b152d89
Fix rubocop issues, introduce usage of frozen literal to improve performance
8 years ago
6f0d312dc3
Force utf-8 encoding when processing XML
8 years ago
0b03bbad67
Discard misattributed remote statuses, improve timelines filter
8 years ago
c0ee14756f
Adding more logging
8 years ago
ac79369f2b
Fix for thread resolve service and process feed service url method
8 years ago
9da30e31c8
Fix region setting for AWS gem
8 years ago
663c0edd8d
Fix typo
8 years ago
434c3fb2f7
ProcessFeedService refactor
8 years ago
8f0869876b
Improved configuration from ENV, cleaned up timeline filter methods
...
to be more readable, add extra logging to process feed service
8 years ago
cb22dce970
Adding hashtags
8 years ago
4762bb6b7a
Fix duplication of media attachments when a remote status reblogs a local one
8 years ago
34bfc0f0dc
Fix up a few exceptions
8 years ago
1af00c8193
Fixing namespaces issue
8 years ago
61d7c88408
Fix namespace parsing in Atom feeds
8 years ago
80217fd58b
Use Account#find_remote method when possible
8 years ago
3d229e3937
Don't return unsaved status from ProcessFeedService
8 years ago
33668b91f8
Adding test for ProcessFeedService
8 years ago
5da603fb6f
Improve process feed service
8 years ago
7cb55af441
Fix default assumed object type (note->activity), make stream entry threaded? check aware of orphaned replies
8 years ago
b23c4b488c
Better comparison of "local" domain
8 years ago
70e9dd0b5b
Blocking will prevent e-mail notifications from blocked user, blocks in UI
8 years ago
d74da1a89a
Small fixes
8 years ago
927333f4f8
Improve code style
8 years ago
c6b0311b86
Fix #54 - 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.
8 years ago
b1a670af8d
Handle remote account mentions a little better by trying a URL lookup in the db
8 years ago
4a670780f0
Fix #51 - prevent duplicate attachments for remote statuses
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
059ebbf48d
Separate PuSH subscriptions from following, add mastodon:push:refresh task,
...
respect hub.lease_seconds (fix #46 )
8 years ago
adffc7a495
Fix #43
8 years ago
183a23943b
Fix how other services used old FollowRemoteAccountService
8 years ago
3cc47beb6e
Refactored generation of unique tags, URIs and object URLs into own classes,
...
as well as formatting of content
8 years ago
1efa8e48d1
Fix enclosures not being parsed for reblogged statuses
8 years ago
eec0dc46a6
PostStatusService can attach media to status, ProcessFeedService likewise
8 years ago
a289c1d52f
Handle delete Salmons, todo: clean up timelines
8 years ago
da4b675aca
Fix favourite handling in ProcessInteractionService
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
a08e724476
Fix subscriptions:clear task, refactor feeds, refactor streamable activites
...
and atom feed generation to some extent, as well as the way mentions are
stored
9 years ago
97d5aba1ec
Do not try to send notification e-mails for reblogs if the reblog is not of a
...
local account
9 years ago
b640f35621
Writing out more tests, fixed some bugs
9 years ago
2b116131d7
Adding e-mail notifications about mentions, follows, favourites and reblogs. Fixing another mention recording bug
9 years ago
Eugen Rochko