23 Commits (fdc17bea58f210f62ac0d9e836b68e84c6dbd15c)

Author	SHA1	Message	Date
Eugen Rochko	fdc17bea58	Fix rubocop issues, introduce usage of frozen literal to improve performance	8 years ago
Eugen Rochko	3731230c6d	Allow @username@domain/@username in follow form, prevent duplicate accounts ... created via remote look-up when domains differ but point to the same resource	8 years ago
Eugen Rochko	157f03f8bd	No-op for Salmons without body, fail fast if Webfinger does not contain ... all required resource links (profile page, salmon, atom feed, magic key)	8 years ago
Eugen Rochko	36e7eeb6b9	Treat dfrn:owner like xmlns:author for Friendica compatibility	8 years ago
Eugen Rochko	64302b3c99	Improve Friendica support (but still not there yet)	8 years ago
Eugen Rochko	22a8801dbc	Adding domain blocks	8 years ago
Eugen Rochko	15d01a5e08	Better comparison of "local" domain	8 years ago
Eugen Rochko	927333f4f8	Improve code style	8 years ago
Eugen Rochko	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
Eugen Rochko	059ebbf48d	Separate PuSH subscriptions from following, add mastodon:push:refresh task, ... respect hub.lease_seconds (fix #46)	8 years ago
Eugen Rochko	0e9c1a297a	Improved error handling for FollowRemoteService	8 years ago
Eugen Rochko	8c0b19012b	Fix #41, debug #42	8 years ago
Eugen Rochko	509c18eb13	Fix local follows, 404 in logs	8 years ago
Eugen Rochko	35dfc0fbcb	Fixed more case-sensitivity issues	8 years ago
Eugen Rochko	f14f462eaf	Adding Turbolinks, adding status posting form on homepage	8 years ago
Eugen Rochko	0e8f59c16f	Refactoring Grape API methods into normal controllers & other things	8 years ago
Eugen Rochko	ad5ae3f60e	Update profile information and download avatar of remote accounts	8 years ago
Eugen Rochko	44c5958203	Fixed small bugs and code style offences	8 years ago
Eugen Rochko	fa7868675d	Send Salmon interactions	8 years ago
Eugen Rochko	10eb47a33e	Do not PuSH-subscribe to remote accounts when creating them for salmon	8 years ago
Eugen Rochko	fa33750105	Adding reblogs, favourites, improving atom generation	8 years ago
Eugen Rochko	1dad72bf13	Fixes and general progress	8 years ago
Eugen Rochko	709c6685a9	Made some progress	8 years ago