The goal of this change is to enhance Mastodon's handling of remote domains
for which the APIs reside on a different host (see issue #1032).

Indeed, when a remote user unknown to Mastodon is mentionned, only its profile
URL (e.g. https://social.example.org/users/User) is known, and Mastodon has to
build a @username@domain handle for it. To do so, Mastodon fetches the user's
atom feed (e.g., https://social.example.org/users/User.atom) and uses its
content to get the username part of the handle, and the URL's host part to
build the domain (e.g., @User@social.example.org). This handle is then used
for a Webfinger request.

In the case where example.org serves the Webfinger info for @User@example.org
and all feeds and APIs are hosted at social.example.org, Mastodon will still
build @User@social.example.org and fail at resolving the account's details
through Webfinger.

This patch changes this behaviour by using the author's email address from
the atom feed to build the handle. In Mastodon-generated atom feeds, the
email address is always the handle it expects for federation.

* Fix #1141, fix #1126 - Work through UpdateRemoteProfileService for both <feed> and <entry> top-level tags

* Improve code quality, remove line unrelated to fix

The async action is send before persist, account.id not yet generated

Pull queue receive 'nil' so no profile update.

These are currently user facing errors, but are not localized. This adds the
ability for these messages to be localized.

* Rewrite Atom generation from stream entries to use Ox instead of Nokogiri::Builder

StreamEntry is now limited to only statuses, which allows some optimization. Removed
extra queries on AccountsController#show. AtomSerializer instead of AtomBuilderHelper
used in AccountsController#show, StreamEntriesController#show, StreamEntryRenderer
and PubSubHubbub::DistributionWorker

PubSubHubbub::DistributionWorker moves n+1 DomainBlock query to PubSubHubbub::DeliveryWorker
instead.

All Salmon slaps that aren't based on StreamEntry still use AtomBuilderHelper and Nokogiri

* All Salmon slaps now use Ox instead of Nokogiri. No touch from status on account

slightly optimized FanOutOnWriteService again

make regeneration worker unique, (only schedule/execute once at a time)

add ability to open status by URL from search (fix #53)

Returns accounts, statuses, hashtags arrays

adjusted to allow choosing it, yet

about them would be processed only after the entire status is processed

Add ability to search accounts by display name

make status pagination headers generation more lax about next page
existing

upon un-reblogging. Check if the reblog was in the feed in the first
place. It might have been filtered on distribution.

of mix of video and images in status, just wasn't rendering
the show action. I moved the validation before the status creation

Moved validation to services/post_status_service.rb

in case of debugging incoming salmons. Add <thr:in-reply-to /> to favourite
salmons because it seems to be required by GS.

StreamEntry model. Simply render Salmon slaps as they are needed

if account lock info was up to date, otherwise re-do the FollowService
with now updated information

status is not in the system at time of distribution; fix #607 - reset privacy
settings to defaults when cancelling replies