* 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.
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
* origin/develop: (33 commits)
maybe_notify_subscribers: Don't create notifications from ingested messages
TwitterAPI: Make change_email require body params instead of query
TwitterAPI: Make change_password require body params instead of query
Make the OPT recomendation clearer
ObjectAgePolicy: Fix pattern matching on published
fix: stream out Create Activity
Improve readability
Quarantine placeholders
improve changelog entry
Make transparency_exclusions use tuples in admin-fe
Add key- and valuePlaceholders for quarantined_instances and mrf_simple
Add transparency_exclusions also to the breaking changes
Change docs
quarantine instances info
Change what nodeinfo returns without breaking backwards compatibility
Return maps in node_info
Add database migrations
Fixed deprecation warning checks
config/description.exs: Update quarantine settings to tuples
make linter happy
...
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)
* origin/develop: (252 commits)
mix.exs: 2.4.50
Update PleromaFE Bundle (2.4.0)
CHANGELOG.md: Fix instances of 2020 being actually 2021
Release 2.4.0
Update AdminFE bundle
Visibility: check Tombstone objects in visible_for_user?/2
CHANGELOG: fixed JSON error rendering
Add activity+json to Phoenix :format_encoders Fixes ErrorView rendering
CHANGELOG: AdminAPI return date with users
AdminAPI: add date to users
CHANGELOG: AdminAPI users sort
AdminAPI: sort user results by ID descending
Moderators: reorganize :admin_api pipeline in Router
Moderators: add UserIsStaffPlug
AP C2S: Remove restrictions and make it go through pipeline
Update Linkify to fix crash on posts with a URL we failed to parse correctly
fix the fucking list timelines on mastofe/soapbox-fe
Deletions: change User.purge/1 to defp, add CHANGELOG entry
Deletions: don't purge keys so Delete/Undo activities can be signed
Deletions: allow deactivated users to be deleted
...
* kePlaceholder and valuePlaceholder of quarantined_instances where in wrong case, should be snake_case
* The mrf simple and transparency exclusion were already OK
* I also added for keywordpolicy as well now. It was done in the admin-fe, but is better to be done here
* I also added comments to explain why we did the _info keys (backwards compatibility)
