A user's e-mail address may be fluid, and the site "instance name"
may be strange or change regularly. There's no reason to use these
over the user's stable ID and the site's stable hostname for TOTP
parameters. Even if the system is built to TOLERATE changes (as it
is -- I tested it), it seems much more elegant to have these para-
meters as stable identifiers.

Release: 2.4.1

See merge request pleroma/pleroma!3501

Backport of: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3514

* Policies were put under a new module (Pleroma.Web.ActivityPub.MRF.Policy instead of Pleroma.Web.ActivityPub.MRF), but this wasn't changed in the Pleroma.Web.ActivityPub.MRF @mrf_config_descriptions
* I don't have a unit test to prevent similar problems in the future because I don't find a proper way to do it
    * The descriptions in the unit tests are defined in the unit tests, so if someone changes module names in the code, the tests wont see it
    * The list is generated in Pleroma.Docs.Generator.list_behaviour_implementations, but I can't do a check in the when clause of the function to see if the provided module is a behaviour or not.

Backport of: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3509

The original approach to search in GIN indexes is to use
`to_tsvector(text)` in the WHERE clause of the query. According to
postgres docs [pdoc], this method does not make use of the index,
while `to_tsvector(config, text)` does. This commit changed the
query to use the two-argument `to_tsvector()`.

[pdoc]: https://www.postgresql.org/docs/12/textsearch-tables.html

To obtain the search config in use, we make a query to the db first.
The `::regconfig::oid` hack is needed because Postgrex does not support
regconfig type directly [postgrexbug]. I use the conversion from and to
`oid` instead of `text` because I tested in the actual DB and querying
using the conversion via `text` is slow just as the one-argument
`to_tsvector()` variant.

[postgrexbug]: https://github.com/elixir-ecto/postgrex/issues/502

Backport of: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3519

Closes: https://git.pleroma.social/pleroma/pleroma/-/issues/2758

* To see what front ends are installed, it ls static/frontends. When this folder doesn't exists yet, it will return an empty array.
* Installing still works since the folder is created during installation already

Backport of: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3510

Backport of: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3512

Backport of: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3508

Backport of: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3507

Backport of: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3504

Backport of: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3505

Backport of: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3503

Backport of: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3503

Backport of: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3500

AFAIK OTP releases are the recomended way of installing, but

  * People seem unaware of that and use from source installations because they use the guide with the name of their distro
  * People don't know what OTP releases are or what it means

I added a warning on all installation-from-source guides and added the same explanation on the two OTP pages (the miigration to OTP and installing OTP)

Backport of: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3485

Backport of: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3499

Release/2.4.0

See merge request pleroma/pleroma!3493

based on 51d3d8d255

Visibility: check Tombstone objects in visible_for_user?/2

See merge request pleroma/pleroma!3490

Fix errors in ErrorView

See merge request pleroma/pleroma!3489

Fixes ErrorView rendering

MastodonAPI: Fix list timelines

Closes mastofe#89 and #2693

See merge request pleroma/pleroma!3477

AdminAPI: sort new users at the top

Closes #2709

See merge request pleroma/pleroma!3481

AdminAPI: add created_at date to users

See merge request pleroma/pleroma!3482

Pipeline Ingestion: Page

See merge request pleroma/pleroma!3097

AP C2S: Remove restrictions and make it go through pipeline

See merge request pleroma/pleroma!3203

Update Linkify

See merge request pleroma/pleroma!3478

Fix user deletion problems

See merge request pleroma/pleroma!3476