9bd3b11cfb
Instead of refusing to create accounts, domain blocks auto-suspend new accounts from that domain
8 years ago
05abd977c1
Fix preview cards layout, do preview card crawling for remote statuses
8 years ago
f63f0c4625
Fix too late return
8 years ago
7951e7ffd5
Add ruby version to Gemfile, move devDependencies in package.json to dependencies,
...
fix bug in process feed service
8 years ago
668013265c
Restoring old async behaviour of thread resolving as it proved to be more robust
8 years ago
f90133d2ad
Thread resolving no longer needs to be separate from ProcessFeedService,
...
since that is only ever called in the background
8 years ago
39cc9fde8a
Add account suspension
8 years ago
14bd46946d
Per-status control for unlisted mode, also federation for unlisted mode
...
Fix #233 , fix #268
8 years ago
2cb3dc5e5a
Update hub URL and re-subscribe if hub URL changes
8 years ago
45c7ee39b3
Remove unneeded indices, improve error handling in background workers, don't needlessly reload reblogged status, send Devise e-mails asynchronously
8 years ago
29b12f9e0a
Call NotifyService about remote reblogs
8 years ago
da2ef4d676
Adding unified streamable notifications
8 years ago
2c58e7e06a
Catch validation errors in ProcessFeedService so that one failing entry wouldn't stop others from going through
8 years ago
e4f56fa942
Don't create attachments if remote file cannot be fetched
8 years ago
fdc17bea58
Fix rubocop issues, introduce usage of frozen literal to improve performance
8 years ago
7ce4670164
Force utf-8 encoding when processing XML
8 years ago
aabf884c5f
Discard misattributed remote statuses, improve timelines filter
8 years ago
b6832553ff
Adding more logging
8 years ago
cff0b03cbb
Fix for thread resolve service and process feed service url method
8 years ago
2f21f4cc01
Fix region setting for AWS gem
8 years ago
096bfbad96
Fix typo
8 years ago
11cbe49ffc
ProcessFeedService refactor
8 years ago
dbe00a4156
Improved configuration from ENV, cleaned up timeline filter methods
...
to be more readable, add extra logging to process feed service
8 years ago
48b9619439
Adding hashtags
8 years ago
91144d46ec
Fix duplication of media attachments when a remote status reblogs a local one
8 years ago
c257b29d86
Fix up a few exceptions
8 years ago
77efdfa110
Fixing namespaces issue
8 years ago
87b618ab02
Fix namespace parsing in Atom feeds
8 years ago
38ce960ff9
Use Account#find_remote method when possible
8 years ago
cfba03bd27
Don't return unsaved status from ProcessFeedService
8 years ago
81065bc06c
Adding test for ProcessFeedService
8 years ago
3306a5d524
Improve process feed service
8 years ago
5f737c7228
Fix default assumed object type (note->activity), make stream entry threaded? check aware of orphaned replies
8 years ago
15d01a5e08
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
Eugen Rochko