2146ac91a0
Follow requests send e-mail notifications, but are excluded from notifications API
...
Better initial state for unlisted/nsfw toggles
8 years ago
7376af90f7
Don't show statuses to blocked users
8 years ago
05b13c38b5
Re-enable Webfinger for locked accounts but don't handle "follow" events
...
coming in via Salmon.
Currently no way to prevent remote follows, but they will only receive public
and unlisted posts
8 years ago
f729cfc881
Private posts mentioning non-followers should not notify them, neither locally nor via Salmon
8 years ago
b891a81008
Follow call on locked account creates follow request instead
...
Reflect "requested" relationship in API and UI
Reflect inability of private posts to be reblogged in the UI
Disable Webfinger for locked accounts
8 years ago
2d2154ba75
Add "locked" flag to accounts, prevent blocked users from following, force-unfollow blocked users
8 years ago
80e02b90e4
Private visibility on statuses prevents non-followers from seeing those
...
Filters out hidden stream entries from Atom feed
Blocks now generate hidden stream entries, can be used to federate blocks
Private statuses cannot be reblogged (generates generic 422 error for now)
POST /api/v1/statuses now takes visibility=(public|unlisted|private) param instead of unlisted boolean
Statuses JSON now contains visibility=(public|unlisted|private) field
8 years ago
6de079a5af
Removing external hub completely, fix #333 fixing digit-only hashtags,
...
removing web app capability from non-webapp pages
8 years ago
668013265c
Restoring old async behaviour of thread resolving as it proved to be more robust
8 years ago
e90fcb46e3
Sensitive content federates using the "nsfw" hashtag
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
2ef9f36cf2
Improve suspend account service
8 years ago
f978b06dd1
Add suspend account functionality to admin UI
8 years ago
f406e01fcf
Add filters for suspended accounts
8 years ago
2488162733
Adding suspend account service
8 years ago
39cc9fde8a
Add account suspension
8 years ago
00e9dac1d3
Automatically block outgoing notifications from silenced accounts to users
...
who don't follow them
8 years ago
3114e55c7a
Fix #323 - self-replies to appear in public timelines again
8 years ago
58b3f4fd67
Fix #329 - avatar errors no longer prevent remote accounts from being saved
...
(without avatar). Also improved search position of exact matches
8 years ago
14bd46946d
Per-status control for unlisted mode, also federation for unlisted mode
...
Fix #233 , fix #268
8 years ago
1e99a2bb03
Fix trying to PuSH-publish updates of remote removals
8 years ago
5b076cbafb
Fix delete Salmons
8 years ago
4eba76711b
Adding backtracing to Salmon/Processing workers
8 years ago
7e5e33df48
Fix Pubsubhubbub::UnsubscribeService
8 years ago
2d2c81765b
Adding embedded PuSH server
8 years ago
8a4913fde0
Public and hashtag timelines now exclude reblogs and replies
...
Fix #289 - don't download avatar unless the URL is http/https
Fix #293 - reblog/reblogged is now boost/boosted
8 years ago
054138797f
Fix #288 - Strip first @ from search query, don't search accounts if it begins with #
8 years ago
950312bada
Fix #278 - Use mb_chars.downcase on hashtags
8 years ago
2cb3dc5e5a
Update hub URL and re-subscribe if hub URL changes
8 years ago
71401659b8
Fix #65 - Options to block notifications from people you don't follow/who don't follow you
8 years ago
4f1d863615
Only distribute statuses to followers who signed in in the last 2 weeks, add rake task for clearing feeds of inactive users
8 years ago
7cee27f517
Fix unfollows not clearing reblogs, fix blocks not clearing reblogs and notifications,
...
skip ActionCable for follow/unfollow/block events, instead clear UI from
blocked account's posts instantly if block request succeeds. Add forgotten
i18n for sensitive content
8 years ago
0603971894
Adding sensitive marker to statuses in API
8 years ago
fc90d38893
Moving some counter queries out of subqueries in the API
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
7944ed6fe5
Adding option to specify asset server, filter followers query by local accounts
...
during Fan Out On Write to load less stuff into memory
8 years ago
93577f74e7
Use old rules for mention notifications as for mentions timeline
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
afded319d2
Add limit to search results
8 years ago
09218d4c01
Use full-text search for autosuggestions
8 years ago
bf5f55a6bb
Fix live status removal from public/hashtag channels
8 years ago
aabf884c5f
Discard misattributed remote statuses, improve timelines filter
8 years ago
c5e03a2e0d
Status removal is broadcast to public/hashtag timelines too
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
bb4d1eb2e8
Improve feed regeneration
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
93212bc2c4
Add test for FanOutOnWriteService
8 years ago
7bb28bf780
Improve @mention regex
8 years ago
48b9619439
Adding hashtags
8 years ago
3731230c6d
Allow @username@domain/@username in follow form, prevent duplicate accounts
...
created via remote look-up when domains differ but point to the same resource
8 years ago
4b357ecf98
Fix subtle bugs, new icon button
8 years ago
909d0d5e88
Adding public timeline silencing
8 years ago
abb8f5837e
Fix public channel
8 years ago
852c82435d
Fix method return when rescuing
8 years ago
0895ff414e
Fix RemoveStatusService trying to send delete salmons on behalf of remote statuses
8 years ago
91144d46ec
Fix duplication of media attachments when a remote status reblogs a local one
8 years ago
244d1307a3
Fix remove status service sending salmons
8 years ago
157f03f8bd
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
36e7eeb6b9
Treat dfrn:owner like xmlns:author for Friendica compatibility
8 years ago
64302b3c99
Improve Friendica support (but still not there yet)
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
65ae9637d6
PuSH unsubscribe needs correct callback URL
8 years ago
5f737c7228
Fix default assumed object type (note->activity), make stream entry threaded? check aware of orphaned replies
8 years ago
22a8801dbc
Adding domain blocks
8 years ago
1f650d327d
Adding public timeline
8 years ago
d772db4344
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
15d01a5e08
Better comparison of "local" domain
8 years ago
5cfc9efad3
Update OStatus2 to handle malformed Salmon without raising unexpected exceptions
8 years ago
2f5b205916
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
Eugen Rochko