diff options
| author | Ariadne Conill <ariadne@dereferenced.org> | 2019-08-13 02:15:21 +0000 |
|---|---|---|
| committer | Ariadne Conill <ariadne@dereferenced.org> | 2019-08-14 01:50:26 +0000 |
| commit | 29db8dc79945026d2024e2462f86b1795859c574 (patch) | |
| tree | 7785f96e76b312ec61999678a3bee474a85cdbea /docs | |
| parent | 54405919d86ce803bf1a17a55c382c2bc59db3b0 (diff) | |
| download | pleroma-29db8dc79945026d2024e2462f86b1795859c574.tar.gz | |
config: remove legacy activitypub accept_blocks setting
Anyone who is interested in dropping blocks can write their own MRF
policy at this point. This setting predated the MRF framework.
Disabling the side effect (unsubscription) is still a config option
per policy.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/config.md | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/docs/config.md b/docs/config.md index 22799af23..3b9be73ec 100644 --- a/docs/config.md +++ b/docs/config.md @@ -319,7 +319,6 @@ config :pleroma, Pleroma.Web.Endpoint, This will make Pleroma listen on `127.0.0.1` port `8080` and generate urls starting with `https://example.com:2020` ## :activitypub -* ``accept_blocks``: Whether to accept incoming block activities from other instances * ``unfollow_blocked``: Whether blocks result in people getting unfollowed * ``outgoing_blocks``: Whether to federate blocks to other instances * ``deny_follow_blocked``: Whether to disallow following an account that has blocked the user in question |