d63f0295b9
Fix public channel
8 years ago
cc10f56f66
Fix method return when rescuing
8 years ago
bcdb0dc310
Fix RemoveStatusService trying to send delete salmons on behalf of remote statuses
8 years ago
4762bb6b7a
Fix duplication of media attachments when a remote status reblogs a local one
8 years ago
7beab6b00c
Fix remove status service sending salmons
8 years ago
405f7f0541
No-op for Salmons without body, fail fast if Webfinger does not contain
...
all required resource links (profile page, salmon, atom feed, magic key)
8 years ago
dd99153ce6
Treat dfrn:owner like xmlns:author for Friendica compatibility
8 years ago
a1d34be18b
Improve Friendica support (but still not there yet)
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
d2c7d9fc4e
PuSH unsubscribe needs correct callback URL
8 years ago
7cb55af441
Fix default assumed object type (note->activity), make stream entry threaded? check aware of orphaned replies
8 years ago
9bf5a73968
Adding domain blocks
8 years ago
c3f5dfeabb
Adding public timeline
8 years ago
62498dcefd
Fix #83 - if user cannot be found (or is self) throw error, don't return empty 200
...
This prevents the undefined profile from being opened in the first place on such an error
8 years ago
b23c4b488c
Better comparison of "local" domain
8 years ago
6e8165696c
Update OStatus2 to handle malformed Salmon without raising unexpected exceptions
8 years ago
96cc77ce55
Catch Paperclip errors on /api/v1/media, return early from update profile service if XML given is nil
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
2febc6ed65
Fix typo
8 years ago
fe77921e47
Catching more exceptions that slipped through, removing AR logging from
...
production as it's very verbose and not very useful
8 years ago
70e9dd0b5b
Blocking will prevent e-mail notifications from blocked user, blocks in UI
8 years ago
7b9a4af311
API for blocking and unblocking
8 years ago
9d59d7b463
Adding a block model and filter mentions from blocked users ( fix #60 )
8 years ago
d74da1a89a
Small fixes
8 years ago
be86d4e0a3
Preparing feeds for better filtering
8 years ago
927333f4f8
Improve code style
8 years ago
e4aebad35a
Fix handling of multiple Link headers (that should not be a thing though)
8 years ago
7e14eefc81
Replace logo, fix #57 - delete/unreblog/unfavourite API, fix #45 - app
...
registration API
8 years ago
210362e665
Improve redirect handling in FetchAtomService
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
608a2bfffc
Upgrade to PubSubHubbub 0.4 (removing verify_token)
8 years ago
059ebbf48d
Separate PuSH subscriptions from following, add mastodon:push:refresh task,
...
respect hub.lease_seconds (fix #46 )
8 years ago
9863196f7b
Small rubocop offences removed
8 years ago
adffc7a495
Fix #43
8 years ago
183a23943b
Fix how other services used old FollowRemoteAccountService
8 years ago
0e9c1a297a
Improved error handling for FollowRemoteService
8 years ago
8c0b19012b
Fix #41 , debug #42
8 years ago
d6a64f45fd
Adding a notification stack for error messages
8 years ago
05b0c985b4
Send "delete" Salmons to remote mentioned accounts on status removal
...
Fixes #27
8 years ago
ce29624c6d
Fixing image upload limits, allowing webm, merge/unmerge events trigger
...
timeline reload in UI, other small fixes
8 years ago
0077fc26df
Merge and unmerge timelines on follow/unfollow, solves #21 , #22
8 years ago
Eugen Rochko