4f9b7432dd
Fix #52 - Add API versioning (v1)
8 years ago
7e14eefc81
Replace logo, fix #57 - delete/unreblog/unfavourite API, fix #45 - app
...
registration API
8 years ago
693383234c
Improved style of settings page
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
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
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
a66d34878c
Add more logging to PuSH callback
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
adffc7a495
Fix #43
8 years ago
bd5ad304ba
Adding media controller, 1 webm/compose form allowed, previews generated
8 years ago
0e9c1a297a
Improved error handling for FollowRemoteService
8 years ago
8c0b19012b
Fix #41 , debug #42
8 years ago
5b0cef9781
Setting up preliminary "detailed" routes in the UI, new API end-point for fetching status context
8 years ago
d6a64f45fd
Adding a notification stack for error messages
8 years ago
762157ee4e
Fix for single status pages
8 years ago
85d89b472d
Optimized n+1 queries in accounts Atom and HTML views
...
Added stack trace for SQL queries in development
Removed badly thought out accounts/lookup API
8 years ago
509c18eb13
Fix local follows, 404 in logs
8 years ago
0f4bc56719
Improving production logs, removing n+1 on media attachments in atom,
...
adding attachments display to static views
8 years ago
eec0dc46a6
PostStatusService can attach media to status, ProcessFeedService likewise
8 years ago
ae1fac0062
Add API to upload media attachments
8 years ago
b5ebf99439
Possibly fix issue with stale favourite/reblog information after API call
8 years ago
54ea7f5dfe
Case-insensitive search by usernames
8 years ago
92afd29650
The frontend will now be an OAuth app, auto-authorized. The frontend will use an access token for API requests
...
Adding better errors for the API controllers, posting a simple status works from the frontend now
8 years ago
bc0692d75b
Removing mini-profiler that doesn't work, formatting timelines a bit better
8 years ago
49520d6e62
Adding React.js, Redux, revamping dashboard
8 years ago
8985f8e66c
Fixing more configuration issues with ActionCable
8 years ago
8459acd123
Fix for force SSL issue with websockets
8 years ago
6426819b6f
Fix tests
8 years ago
6deb9f966e
Live timelines using ActionCable
8 years ago
10ba09f546
Upgrade to Rails 5.0.0.1
8 years ago
ff2cbc0753
Remember me enabled by default
9 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
43bb8a25e7
Remember user logins by default
9 years ago
5764d52b04
Fix Sidekiq pooling issues. Remove API docs from homepage, replace with
...
a basic home timeline
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
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
9594f0e858
Fix preloading
9 years ago
0f5bbb999c
Pre-loading polymorphic associations for Atom feeds
9 years ago
7e58303a8d
Limit Atom feeds to 20 items by default, add pagination by max_id
...
(But there are no Atom feed pagination elements yet)
9 years ago
082e1cbe5a
Fix default max_id query in paginate_by_max_id
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
c28971c70c
Fixed the lookup API method
9 years ago
02696a063e
Change default avatar, redirect to home after sign up
9 years ago
Eugen Rochko