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
76c40cbfb1
Disallow self-follow
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
509c18eb13
Fix local follows, 404 in logs
8 years ago
499beb4484
UI for uploading media attachments (and cancelling them)
...
Mostly resolves #8 , though attachments are still not displayed in public view
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
926eea89b5
RemoveStatusService fleshed out, still doesn't send Salmon slaps though
8 years ago
35dfc0fbcb
Fixed more case-sensitivity issues
8 years ago
29996a7e8b
Fix wrongful mentions breaking status update
8 years ago
54ea7f5dfe
Case-insensitive search by usernames
8 years ago
a289c1d52f
Handle delete Salmons, todo: clean up timelines
8 years ago
49520d6e62
Adding React.js, Redux, revamping dashboard
8 years ago
6426819b6f
Fix tests
8 years ago
6deb9f966e
Live timelines using ActionCable
8 years ago
85b00d19b8
Moving Salmon notifications to background processing, fixing mini-profiler
...
behaviour with Turbolinks enabled, optimizing Rabl for production
9 years ago
da4b675aca
Fix favourite handling in ProcessInteractionService
9 years ago
e24bfbde1a
Fixing FanOutOnWriteService, fixing Sidekiq not having enough DB connections
...
in the pool, adding a throttle of 60rpm per IP, adding mini profiler, adding
admin status to users
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
12559b01ea
Add pagination by max_id instead of offset/limit
9 years ago
f14f462eaf
Adding Turbolinks, adding status posting form on homepage
9 years ago
9d55529318
Fix text color in dashboard inputs, sanitize remote status content in UI,
...
simplify FanOutOnWriteService, add /api/accounts/lookup method
9 years ago
46cbb9c551
Increase note truncation length on account grids, improve FanOutOnWrite a bit,
...
fix tests (the recorded Salmon fixture expects LOCAL_DOMAIN to be something
specific unfortunately)
9 years ago
b640f35621
Writing out more tests, fixed some bugs
9 years ago
7e53efae31
Fix for incoming favourites
9 years ago
2b116131d7
Adding e-mail notifications about mentions, follows, favourites and reblogs. Fixing another mention recording bug
9 years ago
d4892ace62
Adding more test stubs
9 years ago
66a2107527
Turns out that replies don't have to have the type comment. Changed handling
...
of those to depend on presence of <thr:in-reply-to /> instead
9 years ago
f97fc9744f
Use FanOutOnWriteService AFTER processing mentions
9 years ago
Eugen Rochko