@delores @wallfly Oh i see, thanks for the explanation (i am quite new to !gnusocial and still learning). I can't imagine a way to do that today, maybe in the future each node can have an API method to broadcast to which other nodes it is blocking and a reason. And that information should also be public in the registration page of that node, so potential new users can decide if they want to join a !gnusocial  node that is blocking certain other nodes. Blocking other nodes content can be controversial, but i think it has good use cases, and a node admin should be able to easily do it via a simple config.