Features/mastoapi/2.7.0 registration

Based on !1005 (closed) Closes #773 (closed) Part of #734 (closed)

added 6 commits

• 926d0503...8d13c429 - 4 commits from branch pleroma:develop
• f3aa480f - capture error messages in tests
• bfa7bd05 - Merging develop

Compare with previous version

added 1 commit

• 1b3adec7 - test fix

Compare with previous version

added 1 commit

• e849b617 - test fixes

Compare with previous version

added 1 commit

• 4f6f4c5e - credo fix

Compare with previous version

added 1 commit

• 8a2950a5 - config changes & docs

Compare with previous version

added 13 commits

• 8a2950a5...17f7c5e2 - 12 commits from branch pleroma:develop
• ce2cfed0 - Merging

Compare with previous version

unmarked as a Work In Progress

changed the description

added 1 commit

• ea44d9bc - removing comments

Compare with previous version

Do we want it to be possible to disable this API endpoint? I'm wondering if it would make more sense to migrate our registration form to use this API and then reap the benefit of the new account throttling as a bonus to help slow down spam accounts, especially when there is no captcha.

Not a perfect solution, but it's an improvement.

I don't see the point in making it disable able. We already have a registration API on TwAPI side.

mentioned in commit f3e8f5b1

merged