Probably the answer is that the "federated web" needs to move more peer to peer so it's harder to squash individuals like this, or pressure a "node" to do so.

There are some decisions in ActivityPub and the linked data approaches which mean that they will survive mostly intact in a move to a peer to peer encrypted system. The main thing you'd want to do is remove HTTP as a transport protocol in favor of something more decentralized. The "being attached to a node" aspect of federated networks will need to be phased out.

Luckily, we can still use the concepts of inbox/outbox and our vocabularies and etc and things should still be roughly compatible. The only thing in ActivityPub that I think is very strictly HTTP is GET/POST, but I think that can be layered over a more peer to peer system anyway.