Age | Commit message (Collapse) | Author | |
---|---|---|---|
2017-03-22 | Prettier account and stream entry URLs | Eugen Rochko | |
2017-03-01 | Mute button progress so far. WIP, doesn't entirely work correctly. | Kit Redgrave | |
2017-02-11 | After FollowService, re-fetch remote account asynchronously, do nothing | Eugen Rochko | |
if account lock info was up to date, otherwise re-do the FollowService with now updated information | |||
2017-02-07 | Merge pull request #603 from evanminto/activitypub-account | Eugen | |
Expose ActivityStreams 2.0 representation of accounts | |||
2017-02-06 | Add test | Evan Minto | |
2017-02-05 | Removing failed push notification API, make context loads use cache | Eugen Rochko | |
2017-02-02 | Cleaning up format of broadcast real-time messages, removing | Eugen Rochko | |
redis-backed "mentions" timeline as redundant (given notifications) | |||
2017-01-29 | Add tests for new API | Eugen Rochko | |
2017-01-23 | Fix oembed controller test | Eugen Rochko | |
2017-01-15 | Fix tests, add applications to eager loading/cache for statuses, fix | Eugen Rochko | |
application website validation, don't link to app website if website isn't set, also comment out animated boost icon from #464 until it's consistent with non-animated version | |||
2017-01-04 | Fix #390 - fix redirect after sign-up (to login page instead of homepage) | Eugen Rochko | |
2016-12-29 | Add API for retrieving favourites | Eugen Rochko | |
2016-12-29 | Add API for retrieving blocked accounts | Eugen Rochko | |
2016-12-29 | Add ability to use remote follow function on other sites | Eugen Rochko | |
2016-12-26 | Replacing follow requests in the settings area with in-UI column | Eugen Rochko | |
2016-12-26 | Adding follow requests API | Eugen Rochko | |
2016-12-26 | Don't show statuses to blocked users | Eugen Rochko | |
2016-12-23 | Add page for authorizing/rejecting follow requests | Eugen Rochko | |
2016-12-21 | Private visibility on statuses prevents non-followers from seeing those | Eugen Rochko | |
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 | |||
2016-12-18 | Removing external hub completely, fix #333 fixing digit-only hashtags, | Eugen Rochko | |
removing web app capability from non-webapp pages | |||
2016-12-13 | Improved admin UI | Eugen Rochko | |
2016-12-06 | Add suspend account functionality to admin UI | Eugen Rochko | |
2016-12-03 | Improve notification model | Eugen Rochko | |
2016-11-30 | Add basic OEmbed provider API, fix #247 | Eugen Rochko | |
2016-11-30 | Normalize localizations, add stub for admin/accounts | Eugen Rochko | |
2016-11-29 | Unify collection caching code | Eugen Rochko | |
2016-11-28 | Add simple admin overview of PuSH subscriptions | Eugen Rochko | |
2016-11-28 | Adding embedded PuSH server | Eugen Rochko | |
2016-11-26 | Update hub URL and re-subscribe if hub URL changes | Eugen Rochko | |
2016-11-24 | Remove Neo4J | Eugen Rochko | |
2016-11-18 | Fix OAuth authorization page and add a spec for it | Eugen Rochko | |
2016-11-17 | Fix #148 - Devise mailer fixed, test spec added so it won't slip past again | Eugen Rochko | |
2016-11-08 | Move timelines API from statuses to its own controller, add a check for | Eugen Rochko | |
resources that require a user context vs those that don't (such as public timeline) /api/v1/statuses/public -> /api/v1/timelines/public /api/v1/statuses/home -> /api/v1/timelines/home /api/v1/statuses/mentions -> /api/v1/timelines/mentions /api/v1/statuses/tag/:tag -> /api/v1/timelines/tag/:tag | |||
2016-11-05 | Improve @mention regex | Eugen Rochko | |
2016-11-05 | Adding hashtags | Eugen Rochko | |
2016-11-03 | Add tests for recently added API end points | Eugen Rochko | |
2016-10-14 | E-mail preferences page | Eugen Rochko | |
2016-10-07 | Adding public timeline | Eugen Rochko | |
2016-10-03 | API for blocking and unblocking | Eugen Rochko | |
2016-10-03 | Adding a block model and filter mentions from blocked users (fix #60) | Eugen Rochko | |
2016-10-02 | Add API for getting info about authenticated user: ↵ | Eugen Rochko | |
/api/v1/accounts/verify_credentials | |||
2016-09-30 | Fix tests, update goldfinger to catch XML errors | Eugen Rochko | |
2016-09-27 | Fix tests | Eugen Rochko | |
2016-09-27 | Adding landing page | Eugen Rochko | |
2016-09-27 | Fix #52 - Add API versioning (v1) | Eugen Rochko | |
2016-09-26 | Replace logo, fix #57 - delete/unreblog/unfavourite API, fix #45 - app | Eugen Rochko | |
registration API | |||
2016-09-26 | Fix #54 - Fetch remote accounts by URL from mentions | Eugen Rochko | |
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. | |||
2016-09-21 | Fix notifications in UI, added new API for fetching account relationships | Eugen Rochko | |
2016-09-21 | Fix #24 - Thread resolving for remote statuses | Eugen 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-20 | Upgrade to PubSubHubbub 0.4 (removing verify_token) | Eugen Rochko | |