about summary refs log tree commit diff
path: root/app/controllers/stream_entries_controller.rb
AgeCommit message (Collapse)Author
2016-11-15Fix rubocop issues, introduce usage of frozen literal to improve performanceEugen Rochko
2016-10-05Catching more exceptions that slipped through, removing AR logging fromEugen Rochko
production as it's very verbose and not very useful
2016-10-03Making public pages responsive, removing reblogs/favs counts from themEugen Rochko
2016-09-29Improve code styleEugen Rochko
2016-09-21Fix #50 - Order ancestors/descendants by tree pathEugen Rochko
2016-09-21Fix #24 - Thread resolving for remote statusesEugen Rochko
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-08Fix for single status pagesEugen Rochko
2016-09-04Case-insensitive search by usernamesEugen Rochko
2016-03-07Adding doorkeeper, adding a REST APIEugen Rochko
POST /api/statuses Params: status (text contents), in_reply_to_id (optional) GET /api/statuses/:id POST /api/statuses/:id/reblog GET /api/accounts/:id GET /api/accounts/:id/following GET /api/accounts/:id/followers POST /api/accounts/:id/follow POST /api/accounts/:id/unfollow POST /api/follows Params: uri (e.g. user@domain) OAuth authentication is currently disabled, but the API can be used with HTTP Auth.
2016-03-06Adding routes to follow, unfollow, favourite and reblog (locally known models)Eugen Rochko
2016-03-05Adjusting design of profile and entry pages, linkify mentions in statusesEugen Rochko
2016-02-29Refactoring Grape API methods into normal controllers & other thingsEugen Rochko