From 07e751751a2059a50f34ca1004cfe36e892e3cd2 Mon Sep 17 00:00:00 2001 From: Bob Mottram Date: Sun, 14 Jul 2019 21:19:17 +0100 Subject: [PATCH] Notes on blocking and unblocking --- README.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/README.md b/README.md index 77d839afb..31f34977f 100644 --- a/README.md +++ b/README.md @@ -377,3 +377,19 @@ python3 epicyon.py --nickname jon --domain somedomain.net --availability ready ``` With roles, skills and availability defined tasks may then be automatically assigned to the relevant people, or load balanced as volunteers come and go and complete pieces of work. Orgbots may collect that information and rapidly assemble a viable organization from predefined schemas. This is the way to produce effective non-hierarchical organizations which are also transient with no fixed bureaucracy. + +## Blocking and unblocking + +Whether you are using the **--federate** option to define a set of allowed instances or not, you may want to block particular accounts even inside of the perimeter. To block an account: + +``` bash +python3 epicyon.py --nickname yournick --domain yourdomain --block somenick@somedomain +``` + +This blocks at the earliest possble stage of receiving messages, such that nothing from the specified account will be written to your inbox. + +Or to unblock: + +``` bash +python3 epicyon.py --nickname yournick --domain yourdomain --unblock somenick@somedomain +```