aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorAriadne Conill <ariadne@dereferenced.org>2019-08-13 02:15:21 +0000
committerAriadne Conill <ariadne@dereferenced.org>2019-08-13 02:15:21 +0000
commitf46cd7e9c750b9c4c36f0a6c4b3a1ffd2f94a6d0 (patch)
tree837a101fb853c673caec14bfee51aaca82331dd6 /docs
parentb0fad153e1d4bf6c95c18bdab92a42978b729108 (diff)
downloadpleroma-f46cd7e9c750b9c4c36f0a6c4b3a1ffd2f94a6d0.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.md1
1 files changed, 0 insertions, 1 deletions
diff --git a/docs/config.md b/docs/config.md
index 55311b76d..d0247ef9c 100644
--- a/docs/config.md
+++ b/docs/config.md
@@ -329,7 +329,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