b3c7c8700d
Fix most pages on small screens
8 years ago
188c6f326b
Making public pages responsive, removing reblogs/favs counts from them
8 years ago
d74da1a89a
Small fixes
8 years ago
9fd3d7b6cd
Add since_id param to feeds
8 years ago
a0f85774c4
Redirect after sign in to previous page (unless it's a sign in/up/etc page)
8 years ago
6d7290f47c
Add API for getting info about authenticated user: /api/v1/accounts/verify_credentials
8 years ago
31a0202546
Slightly improved e-mail notifications
8 years ago
2d4f9ecebf
Validate against multiple reblogs of same status by same account
8 years ago
be86d4e0a3
Preparing feeds for better filtering
8 years ago
1fce687f8e
Unreblogging and unfavouriting from the UI
8 years ago
4909bbf415
Add logging for outgoing http requests
8 years ago
96ad9b0db1
Meaningful validation errors in API response
8 years ago
62b057b085
Adjust client registration API
8 years ago
ef2b50c9ac
Deleting statuses from UI
8 years ago
a4f7eca5fa
Fix #25 - Only latest reblog of status kept on feed as zset value is set to "true" status ID
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
e63aebff7a
Adding landing page
8 years ago
45a96e899e
Fix #58 - disable compose form while image is uploading
8 years ago
4f9b7432dd
Fix #52 - Add API versioning (v1)
8 years ago
3f75f52285
Fix subtle home feed filtering bug
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
0bd4608ad1
Fix #55 - Filter self from pre-filled mentions
8 years ago
693383234c
Improved style of settings page
8 years ago
e9bc4a4a08
Limit usernames to 30 chars, statuses to 500, open account after follow form success
8 years ago
62b384824d
Improved styling for media/videos in detailed status view
8 years ago
15f51dbf8c
Better styling for selected status in detailed view
8 years ago
1215ab57ff
Some extra scopes for user sorting
8 years ago
a706f1af04
Don't generate stream entries for streamables of remote accounts
8 years ago
fb94013796
Improved partial rendering for threads
8 years ago
db6df6ddb3
Only load JS on homepage, no other page uses it
8 years ago
57583f3fb8
Improve partial rendering and Haml performance (Haml->Hamlit)
8 years ago
95d72b2249
Temporarily link "settings" to the static version of the form
8 years ago
0c75ce1122
Improved ColumnsArea on smaller windows, improved how ActionBar looks
8 years ago
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)
8 years ago
c6d893a71d
Uploading/undoing media modifies status text. Also: status text trimmed before validation
8 years ago
b1a670af8d
Handle remote account mentions a little better by trying a URL lookup in the db
8 years ago
2a84271e85
Infinite scroll for account timelines
8 years ago
4a670780f0
Fix #51 - prevent duplicate attachments for remote statuses
8 years ago
2c0261ac25
Infinite scroll for timeline columns
8 years ago
74dfefabd3
Make in-text mentions open account detailed view when possible
8 years ago
bc98865c1a
API returns mentions for statuses, compose form pre-fills all relevant usernames into the form when replying
8 years ago
c0e9603c92
Fix #50 - Order ancestors/descendants by tree path
8 years ago
e46abc71ca
Fix notifications in UI, added new API for fetching account relationships
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
6d89edc4f7
Fix #47 by renaming TIMELINE_SET action to TIMELINE_REFRESH_SUCCESS
8 years ago
1d2856c2af
Since GNU Social hubs don't seem to return a hub.lease_seconds param in the subscription confirmation request,
...
we'll have to default that value to the GS "minimum" (from their code) which is 24 hours.
8 years ago
246330493b
More debugging for PuSH confirmations
8 years ago
Eugen Rochko