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
2016-11-03 16:57:44 +01:00
e4671adc25
Fix reblogged/favourited caching; add API endpoints for who favd/reblogged status
2016-11-03 14:50:22 +01:00
562044f36a
Need to disable caching again due to bug in Rabl
2016-11-03 13:59:31 +01:00
9467b900a2
Make cookies https-only if LOCAL_HTTPS is true, set X-Frame-Options to DENY,
...
add permissive CORS to API controllers
2016-11-02 12:58:15 +01:00
dd03118098
Fix follow icon changing plus to minus, add terms page stub
2016-11-01 18:05:55 +01:00
fa1cc2d05a
Limit returned followees/followers by API to 40 for now
2016-10-30 15:14:07 +01:00
e0a197650a
Adding common followers API, fixing fallback query again
2016-10-29 01:29:19 +02:00
b746a931a5
Fix OAuth authorization redirect
2016-10-23 12:05:55 +02:00
a9e40a3d80
Adding OAuth access scopes, fixing OAuth authorization UI, adding rate limiting
...
to the API
2016-10-22 19:39:44 +02:00
04bbc57690
Fix #100 - Add "back" button to certain views
...
Also fix reloading of timelines after merge-type events
2016-10-19 18:20:19 +02:00
43df35213e
Improving all forms
2016-10-18 16:37:15 +02:00
2e0a38d07c
Added e-mail edit field to settings, proper format default for webfinger
2016-10-18 03:34:26 +02:00
d5e086a47b
Adding application/jrd+json webfinger resource
2016-10-18 02:54:49 +02:00
de1f3aab86
Fix #16 - Optimize n+1 queries when checking reblogged/favourited values for status lists in API
2016-10-16 19:10:16 +02:00
e21a3fe0cd
Adding sync of follow relationships to Neo4J, accounts/suggestions API
2016-10-14 23:10:07 +02:00
7a6d95f70c
E-mail preferences page
2016-10-14 02:28:49 +02:00
33f7e1cf99
Shorten rendered links (strip protocol and www, truncate to 30 chars), redirect
...
to sign in page after sign up instead of root path which redirects to /about
2016-10-13 16:51:34 +02:00
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)
2016-10-13 13:41:06 +02:00
68eed8c61f
Stop logging incoming Atom
2016-10-10 18:16:39 +02:00
f49ed8c819
Log incoming Atom from PuSH
2016-10-10 17:40:28 +02:00
427ba27641
Public timeline to exclude users you blocked
2016-10-09 15:15:21 +02:00
22a8801dbc
Adding domain blocks
2016-10-09 14:48:59 +02:00
1f650d327d
Adding public timeline
2016-10-07 16:00:11 +02:00
943c69c65d
Fix #73 - Click on in-UI profile avatar/name to open public profile
2016-10-06 23:15:50 +02:00
3554d638b3
Fix #72 - add follow/unfollow button to public profiles
2016-10-06 21:27:58 +02:00
15d01a5e08
Better comparison of "local" domain
2016-10-06 16:36:16 +02:00
b60430fe8f
Fix sign-in redirecting "back" to a missing image because missing static files hit the raise_not_found method
2016-10-06 15:42:00 +02:00
2f5b205916
Catch Paperclip errors on /api/v1/media, return early from update profile service if XML given is nil
2016-10-06 14:40:15 +02:00
fe77921e47
Catching more exceptions that slipped through, removing AR logging from
...
production as it's very verbose and not very useful
2016-10-05 13:26:44 +02:00
7b9a4af311
API for blocking and unblocking
2016-10-03 18:17:06 +02:00
2c9e672ee2
Integrating block relationships into the API (read-only for now)
2016-10-03 17:16:58 +02:00
9d59d7b463
Adding a block model and filter mentions from blocked users ( fix #60 )
2016-10-03 17:12:13 +02:00
fc198a8b4c
Adding e-mail confirmations
2016-10-03 16:51:00 +02:00
188c6f326b
Making public pages responsive, removing reblogs/favs counts from them
2016-10-03 00:26:00 +02:00
9fd3d7b6cd
Add since_id param to feeds
2016-10-02 22:35:27 +02:00
a0f85774c4
Redirect after sign in to previous page (unless it's a sign in/up/etc page)
2016-10-02 17:11:08 +02:00
6d7290f47c
Add API for getting info about authenticated user: /api/v1/accounts/verify_credentials
2016-10-02 16:14:21 +02:00
96ad9b0db1
Meaningful validation errors in API response
2016-09-30 22:31:16 +02:00
62b057b085
Adjust client registration API
2016-09-30 00:03:08 +02:00
ef2b50c9ac
Deleting statuses from UI
2016-09-30 00:00:45 +02:00
927333f4f8
Improve code style
2016-09-29 21:28:21 +02:00
e63aebff7a
Adding landing page
2016-09-27 23:12:33 +02:00
4f9b7432dd
Fix #52 - Add API versioning (v1)
2016-09-27 16:59:08 +02:00
7e14eefc81
Replace logo, fix #57 - delete/unreblog/unfavourite API, fix #45 - app
...
registration API
2016-09-26 23:56:53 +02:00
693383234c
Improved style of settings page
2016-09-25 15:48:20 +02:00
3f9708edc4
Change output of api/accounts/:id/follow and unfollow to return relationship
...
Track relationship in redux state. Display follow/unfollow and following-back
information on account view (unstyled)
2016-09-23 20:23:26 +02:00
c6d893a71d
Uploading/undoing media modifies status text. Also: status text trimmed before validation
2016-09-22 21:39:53 +02:00
c0e9603c92
Fix #50 - Order ancestors/descendants by tree path
2016-09-21 23:18:28 +02:00
e46abc71ca
Fix notifications in UI, added new API for fetching account relationships
2016-09-21 22:07:18 +02:00
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.
2016-09-21 01:50:31 +02:00
Eugen Rochko