mastodon - Plural Café fork of Mastodon/Glitch Social

Age	Commit message (Collapse)	Author
2016-11-15	Fix rubocop issues, introduce usage of frozen literal to improve performance	Eugen Rochko

2016-11-03	Allow @username@domain/@username in follow form, prevent duplicate accounts	Eugen Rochko
	created via remote look-up when domains differ but point to the same resource
2016-10-13	No-op for Salmons without body, fail fast if Webfinger does not contain	Eugen Rochko
	all required resource links (profile page, salmon, atom feed, magic key)
2016-10-12	Treat dfrn:owner like xmlns:author for Friendica compatibility	Eugen Rochko

2016-10-12	Improve Friendica support (but still not there yet)	Eugen Rochko

2016-10-09	Adding domain blocks	Eugen Rochko

2016-10-06	Better comparison of "local" domain	Eugen Rochko

2016-09-29	Improve code style	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	Separate PuSH subscriptions from following, add mastodon:push:refresh task,	Eugen Rochko
	respect hub.lease_seconds (fix #46)
2016-09-17	Improved error handling for FollowRemoteService	Eugen Rochko

2016-09-17	Fix #41, debug #42	Eugen Rochko

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

2016-09-04	Fixed more case-sensitivity issues	Eugen Rochko

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

2016-02-29	Refactoring Grape API methods into normal controllers & other things	Eugen Rochko

2016-02-28	Update profile information and download avatar of remote accounts	Eugen Rochko

2016-02-25	Fixed small bugs and code style offences	Eugen Rochko

2016-02-24	Send Salmon interactions	Eugen Rochko

2016-02-24	Do not PuSH-subscribe to remote accounts when creating them for salmon	Eugen Rochko

2016-02-23	Adding reblogs, favourites, improving atom generation	Eugen Rochko

2016-02-22	Fixes and general progress	Eugen Rochko

2016-02-22	Made some progress	Eugen Rochko