

I give Nazis all the rights they want to give to me. And all the lefts too.
If you follow an ideology of intolerance, you are no longer entitled to tolerance from others. I will not engage in discourse with followers of an ideology that would enslave my family and likely deport, imprison or exterminate those who are of color and/or disabled.
That’s what it comes down to. You can’t have any sort of discussion after that point. The conversation has been reduced to either I stop you or you destroy my life. There’s nothing more to be said.
If I’m not human in your eyes, you’ve already proven your inhumanity to me.
This is a core issue with ActivityPub, one that I noticed myself when I started working with it. Unless a server is setup to keep a user’s private marked posts completely off the ActivityPub feed, they’re accessible within it to any script that ignores the opt-out request.
My personal example was setting up wordpress to interact with a Mastodon instance, and suddenly finding private conversations published from Mastodon to my wordpress site that weren’t visible to me at all on Mastodon.
Needless to say, that gave me pause about building anything with the protocol until I really understand the access control behind publishing, because even instance owners don’t seem to fully grasp it themselves.