This reverts merge request !1877

Admin API: `PATCH /api/pleroma/admin/users/:nickname/credentials`, `GET /api/pleroma/admin/users/:nickname/credentials`.

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

- [] for options
- <> for mandatory arguments
- foo ... when foo can be repeated

[ci skip]

Closes: pleroma/pleroma#1621

[ci skip]

Needs to be backported to stable.

Related: pleroma-support#29

It could easily be confused with the Hackney settings.

A warning was added, but their were some newlines and whitespaces missing which broke the rendering of the setting. I've added them now

Related: pleroma/pleroma#1594

Add warning to the fetch_initial_posts setting. Now we sometimes have people who enable this without realising the consequences (tons of posts being fetcht as each fetch makes Pleroma discover new users)
I also made a more explicit distinction between OTP and from source installs in the general explanation

Admin API: Exclude boosts from `GET /api/pleroma/admin/users/:nickname/statuses` and `GET /api/pleroma/admin/instance/:instance/statuses`

Ilja authored 5 years ago and lain committed 5 years ago

I added a new file to explain
* where a custom theme can be created
* where themes can be downloaded
* where to add the theme on the server
* how to make the theme available on the instance
* how to set the theme as default on the instance

[#1505] Restricted max thread distance for fetching replies on incoming federation (in addition to reply-to depth restriction).