mastodon - Plural Café fork of Mastodon/Glitch Social

Age	Commit message (Collapse)	Author
2016-10-02	Add API for getting info about authenticated user: ↵	Eugen Rochko
	/api/v1/accounts/verify_credentials
2016-10-02	Preparing feeds for better filtering	Eugen Rochko

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

2016-09-18	Small rubocop offences removed	Eugen Rochko

2016-09-18	Fix #43	Eugen Rochko

2016-09-16	Test case for new api endpoint	Eugen Rochko

2016-09-12	Fixing image upload limits, allowing webm, merge/unmerge events trigger	Eugen Rochko
	timeline reload in UI, other small fixes
2016-09-09	Refactored generation of unique tags, URIs and object URLs into own classes,	Eugen Rochko
	as well as formatting of content
2016-09-08	Optimized n+1 queries in accounts Atom and HTML views	Eugen Rochko
	Added stack trace for SQL queries in development Removed badly thought out accounts/lookup API
2016-09-08	Removing default avatars	Eugen Rochko

2016-09-08	Fix local follows, 404 in logs	Eugen Rochko

2016-09-08	Fixing atom feeds for accounts, adding tests that would catch such bugs in ↵	Eugen Rochko
	future
2016-09-05	Adding enclosures to Atom and statuses JSON	Eugen Rochko

2016-09-05	PostStatusService can attach media to status, ProcessFeedService likewise	Eugen Rochko

2016-09-05	Add API to upload media attachments	Eugen Rochko

2016-09-05	Enhancing test suite but I think the problem might have been caching setting	Eugen Rochko

2016-09-04	Handle delete Salmons, todo: clean up timelines	Eugen Rochko

2016-09-04	Normalized data in Redux, fix for asset URLs when rendered outside request	Eugen Rochko

2016-08-18	Fixing more configuration issues with ActionCable	Eugen Rochko

2016-08-17	Upgrade to Rails 5.0.0.1	Eugen Rochko

2016-03-28	Remember me enabled by default	Eugen Rochko

2016-03-27	Fix mentions regex to exclude usernames in Medium URLs	Eugen Rochko

2016-03-27	Fix issue with unresolvable usernames	Eugen Rochko

2016-03-26	Moving Salmon notifications to background processing, fixing mini-profiler	Eugen Rochko
	behaviour with Turbolinks enabled, optimizing Rabl for production
2016-03-25	Fix subscriptions:clear task, refactor feeds, refactor streamable activites	Eugen Rochko
	and atom feed generation to some extent, as well as the way mentions are stored
2016-03-24	Sanitize remote html in atom feeds, API (not just UI), use cached mention	Eugen Rochko
	relations on Status#mentions
2016-03-22	Only re-download avatar if URL changed (fix #19)	Eugen Rochko

2016-03-21	Adding Turbolinks, adding status posting form on homepage	Eugen Rochko

2016-03-21	Fixed the lookup API method	Eugen Rochko

2016-03-21	Fix text color in dashboard inputs, sanitize remote status content in UI,	Eugen Rochko
	simplify FanOutOnWriteService, add /api/accounts/lookup method
2016-03-21	Ancestors and descendants of statuses	Eugen Rochko

2016-03-20	Adding more tests for helpers	Eugen Rochko

2016-03-20	Writing out more tests, fixed some bugs	Eugen Rochko

2016-03-19	Adding e-mail notifications about mentions, follows, favourites and reblogs. ↵	Eugen Rochko
	Fixing another mention recording bug
2016-03-19	Adding public following and followers pages, fix #3	Eugen Rochko

2016-03-19	Removing some unused gems, adding pagination to profiles, fix #10	Eugen Rochko

2016-03-19	Adding more test stubs	Eugen Rochko

2016-03-19	Fix #13, Atom feeds now contain formatted post content	Eugen Rochko

2016-03-18	Removing autogenerated test stubs that were not needed	Eugen Rochko

2016-03-14	Bind oauth applications to users	Eugen Rochko

2016-03-12	Adding simple_form, adding profile settings, header image	Eugen Rochko

2016-03-07	Adding doorkeeper, adding a REST API	Eugen 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.