GitLab

Merge/develop 20200713

See merge request mfc/pleroma!81

fix markdown rendering withing <details>; typo parent**s**_visible

See merge request pleroma/pleroma!2781

Don't enable Pleroma.HTTP.Middleware.FollowRedirects unless Gun is used

Closes #1966 and #1961

See merge request pleroma/pleroma!2778

OpenAPI: Add :id to follower/following endpoints, fixes #1958

Closes #1958

See merge request pleroma/pleroma!2772

Expose the post formats in /api/v1/instance

See merge request pleroma/pleroma!2776

Improve TOTP token and recovery input fields in OAuth login

See merge request pleroma/pleroma!2769

Bug issue template: remove choice in "Installation type"

See merge request pleroma/pleroma!2774

It made gitlab display "1 of 2 tasks completed" when one is chosen,
which is totally not what this was used for.

Refactor gun pooling and simplify adapter option insertion

Closes #1834, #1700, and #1680

See merge request !2479

Refactor notification settings

See merge request pleroma/pleroma!2602

Add rejection reason to our MRFs

See merge request pleroma/pleroma!2759

Bring back oban job pruning

Closes #1945

See merge request pleroma/pleroma!2768

Include port in host for signatures

See merge request pleroma/pleroma!2766

Closes #1945

This produced error log messages about GenServer termination
every time the connection was not open due to a timeout.

Instead we stop with `{:shutdown, <gun_error>}` since shutting down
when the connection can't be established is normal behavior.

- `verify_fun` is not useful now
- use `customize_check_hostname` (OTP 20+ so OK)
- `partial_chain` is useless as of OTP 21.1 (wasn't there, but hackney/..
uses it)

The new pooling code just removes the connection when it's down,
there is no need to reconnect a connection that is just sitting idle,
better just open a new one next time it's needed

The numbers of the native time unit were so small the CRF was always 1,
making it an LRU. This commit switches the time to miliseconds and changes
the time delta multiplier to the one yielding mostly highest hit rates according
to the paper

When the application restarts (which happens after certain config
changes), the limiters are not destroyed, so `ConcurrentLimiter.new`
will produce {:error, :existing}