* 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)
* ./configuration/mrf.md
* Change example
* ./configuration/cheatsheet.md
* Change descriptions to include that a reason is given
* CHANGELOG.md
* Add as breaking change
Added a new field in the nodeinfo called quarantined_instances_info
This holds an object like `"quarantined_instances_info":{"quarantined_instances":{"quar.inst":{"reason":"whatever reason"}}}}`
It's easiest (and imo most proper) to use tuples {"instance, "reason"} in BE,
but for FE maps like %{"instance": "instance", "reason", "reason"} are better.
I changed it so that node_info returns maps now for simple_policy and quarantined instances.
When a setting was deprecated, the code would stop checking for the rest of the possible deprications. This also meant that the settings weren't rewritten to the new settings for deprecated settings besides the first one.
No test was done for quarantined instances yet. I added a factory for followers_only notes and checked
* That no followers only post is send when the target server is quarantined
* That a followers only post is send when the target server is not quarantined
