Signed-off-by: Marcin Mikołajczak <me@m4sk.in>

* Use instance name in "password changed" mail

instead of "Mastodon".

Fixes tootsuite#2620.

* Use instance name in password reset mail

instead of "Mastodon".

* feat(components/media_gallery): Responsive images

* fix(components/media_gallery): Link to image URL

* Fix #3910 - Require OTP authentication to disable 2FA. Also, remove ability
to generate new OTP backup codes *after* initial backup codes were handed
out during activation

* Restore recovery code re-generation

* Improve display of some 2FA elements

* Add overview of active sessions

* Better display of browser/platform name

* Improve how browser information is stored and displayed for sessions overview

* Fix test

* Fix #2347 - Bind web UI access token to session

When you logout, session also destroys the access token, so it's no longer
valid. If access token is destroyed some other way, the session is also
destroyed, requiring a re-login.

Fix #1681 - Add scheduler to remove revoked access tokens and grants

* Fix test

* Add overview of active sessions

* Better display of browser/platform name

* Improve how browser information is stored and displayed for sessions overview

* Fix test

* Remove unused column_collapsable.js
* Remove old styles
* Extract `> div`  style to independent class

ref https://tc39.github.io/proposal-decorators/

* feat: Revocable sessions

* fix: Tests using sign_in

* feat: Configuration entry for the maximum number of session activations

* Introduce domains method to Account relation

Account had followers_domains method, which was excessively specific.
Let relation of Account have domains method instead.

* Move follow_mapping in Account to AccountInteractions

* Introduce shared examples for AccountAvatar inclusion

* Cover Account more

* Fix regression from #3842

Simplify the query by omitting all direct statuses. Private statuses
are allowed because they are from accounts we are following (so
by definition)

Resolves #3887 (alternative)

* Adjust test

(This patch has been merged as bugfix and reverted, but still valuable as
improvement)

Previously, we've attached IntersectionObserver twice for boosted statuses:
wrapper Status and wrapped Status. but wrapped Status don't need to manage
intersection and visibility by itself, because it's a part of wrapper Status.

* Revert "Bump version to 1.4.4"

This reverts commit 1585b0c6.

* Revert "Fix conversations (fixes #3869) (#3870)"

This reverts commit 15b43f55.

* Revert "Fix streaming server. Redis connection subscribe for each channel. (#3828)"

This reverts commit d8ec8328.

* Revert "Filter direct statuses in Status.as_home_timeline (#3842)"

This reverts commit bab5a182.

* Revert "Fix RemoteFollow behavior (#3868)"

This reverts commit a20cf3b6.

* Revert "Update fabricator for MediaAttachment to attach a file according to type (#3862)"

This reverts commit 356df7ae.

* Revert "Upgrade React Router (#3677)"

This reverts commit 8f03fdce.

* Revert "Do not call setState from unmounted component (#3853)"

This reverts commit 1fc6cb49.

* Revert "Replace TextIconButton for SensitiveButton to IconButton (#3759)"

This reverts commit eb832e88.

* Revert "Fix RTL detection on Ruby side (#3867)"

This reverts commit b16b6935.

* Revert "i18n: Fixed typo in Polish translation (#3864)"

This reverts commit da6fa029.

* Revert "Don't attach IntersectionObserver for wrapped statuses (#3863)"

This reverts commit 94ad0706.

* Actually create conversations given explicit URIs

* Try to get the parent toot in before validation, to avoid creating a new conversation

The classes using Status.as_home_timeline, namely Feed and
PrecomputeFeedService are expected to filter direct statuses as
FanOutWriteService does, but their filtering were incomplete or missing.

This commit solves the problem by filtering direct statuses in
as_home_timeline as the other similar methods such as as_public_timeline
does.