* origin/develop: (159 commits)
Fix CHANGELOG entry meant for next release
Revert "Merge branch 'patch-fix-open-api-spec' into 'develop'"
object_validator: Refactor most of validate/2 to a generic block
date-times are always strings
Fix function calls due to module name change
Temp file leaked, oops
Add more details to the cheatsheat for FollowBot MRF
Prefer FollowBot naming convention vs Followbot
Document new FollowBot MRF
More tests to validate Followbot is behaving
Remove Task.async as it is broken here and probably a premature optimization anyway
Only need to validate a follow request is generated for now
Revert
Do not try to follow local users. Their posts are already available locally on the instance.
Change module name to FollowbotPolicy
Add follow_requests_outstanding_since?/3 to Pleroma.Activity
Lint
Better checking of previous follow request attempts
Prevent duplicates from being processed
Make the followbot only dispatch follow requests once per 30 day period
...
* origin/develop: (185 commits)
OAuthScopesPlug: remove transform_scopes in favor of explicit admin scope definitions
OpenAPI: Add `admin:` scope prefix to admin operations
Remove `:auth, :enforce_oauth_admin_scope_usage`
Do not want these interfering with develop builds
Make it possible to generate custom docker images by prefixing the branch name with "build-docker"
Chats: Introduce /api/v2/pleroma/chats which implements pagination
ChatMessage schema: Add `unread` property
Relicense documentation under CC-BY-4.0
Add API endpoint to remove a conversation
update changelog to mention change of avatar
replace avi.png
Add myself to .mailmap
[#2053] Changed `Notification/for_user_query/2` to use join to filter out inactive actors instead of subselect of _all_ inactive AP ids from `users`.
[#2510] Improved support for app-bound OAuth tokens. Auth-related refactoring.
not used mock
OpenAPI spec: Do not show build enviroment in the spec version
OpenAPI spec task: Load pleroma application to get version info
Lint
Revert "Add plaintext support for all emails except the digest"
MRF NoEmptyPolicy: Deny posts from local users if there is no content or only mentions.
...
This setting defaults to false so the relay host will be used in an MX query so
multiple SMTP servers can be used. gen_smtp code states that all records returned from the
MX query are attempted in order and only a permanent SMTP error will stop the client from
attempting other servers in the list. Connection failures, TLS issues, etc will cause it to
try the next host.
If there is no MX record associated with the relay host, it automatically tries connecting to it
directly.
There is really no reason to expose this to end users. The default value is fine for everyone.
