* origin/develop: (193 commits)
Remove search result order for non-RUM indexes
Update `auto_linker` dependency
Document TagPolicy in `rewrite_policy` section
Import release config from env variable or /etc/pleroma/config.exs and warn if the file is missing
Add option to restrict all users to local content
Better default parameters for suggestion
Update `plug` dependency
Update `ex_rated` dependency
Replace `MastodonAPIController.account_register/2` rate limiter
Update CHANGELOG
Add rate limiting for search endpoints
Add RateLimiter
Remove unused imports and aliases from migration
Update pleroma_ctl
Add more tests for using media_proxy and whitelists
Add a changelog entry for releases
specify that a version is needed for rollback
Add migrate/rollback to release tasks
Fix wrong placement of serve_endpoints
Use Mix.shell().yes? if available
...
In my tests the interaction between thread containment and other restrictions
makes postgresql create some very bad query plans. This caused direct messages
to time out on soykaf, for example.
* origin/develop: (218 commits)
http: bump connection timeout to 10 seconds
Fix prometheus-ecto error when not configured
Document MRF.Simple :report_removal
Add virtual :thread_muted? field
Move default mascot configuration to `config/`
Add changelog entry for mascot config
Use string map for default mascot
Format mascot tests
Add mascot get/set tests
Add API endpoints for a custom user mascot
Add report filtering to MRF.SimplePolicy
add Changelog entry
also suppress link previews from posts marked #nsfw
add CHANGELOG entry
config: make sending the user agent configurable, disable sending the user agent in tests
http: request builder: send user-agent when making requests
rich media: suppress link previews if post is marked as sensitive
mrf: simple policy: mark all posts instead of posts with media as sensitive if they match media_nsfw
CI: Use the correct image with the correct hostname.
RUM: Set rum status by the environment.
...
As discussed on irc. Unlike Mastodon our web interface for registrations
is using the same APIs regular apps would be using, so 5 requests per 30
minutes per IP could hurt valid use-cases when Pleroma-FE switches to
it. Also enable the endpoint by default, it makes no sense to
have it disabled when
1. TwitterAPI endpoint is there and always enabled
2. Unlike Mastodon, there is no way to get an account without using the APIs (makes me wonder why the setting is even there)
Also in this commit: minor changelog improvements.
