Every time someone tries to use it, it goes mad and tries to scrape the
entire fediverse for no visible reason, it's better to just remove it
than continue shipping it in it's current state.
idea acked by lain and feld on irc
Closes#1595#1422
The current rate limiter disable logic won't trigger when the remote ip
is not forwarded, only when the remoteip plug is not enabled, which is
not the case on most instances since it's enabled by default. This
changes the behavior to warn and disable when the remote ip was not forwarded,
even if the RemoteIP plug is enabled.
Also closes#1620
* origin/develop: (116 commits)
streamer group & Oban crontab child
Update PleromaFE bundle for the 2.0 release
Update AdminFE build
add confirm field to filtered params
Admin API: Exclude boosts from `GET /api/pleroma/admin/users/:nickname/statuses` and `GET /api/pleroma/admin/instance/:instance/statuses`
Admin API: `GET /api/pleroma/admin/statuses` - list all statuses (accepts `godmode` and `local_only`)
unnecessary groups
instance.gen task: make example instance name less confusing
instance.gen task: remind to transfer the config to the database after migrations
instance.gen task: make instance name default to the domain
Update AdminFE build
Fix Dialyzer warnings
Add a test to ensure OAuth tokens are tied to Push subscriptions
compile fix
instance.gen task: fix crash when using custom static directory
Admin API: `GET /api/pleroma/admin/stats` to get status count by visibility scope
DOCS Theming your instance
Captcha: return invalid when answer_data is nil
captcha_test.exs: Use the same testing logic in Kocaptcha and native
Add missing invites_enabled and account_activation_required settings
...
The setting is now simply "attachment_links" and the boolean value does
what you expect. A double negative is never possible and describing the
functionality is no longer a philospher's worst nightmare.
