When you design a CoC for your #Mastodon or #GNUSocial instance, remember that you want enough strictness to:
- Kick ESR off if he shows up
- Aggressively ban botters & 4chan
- Shut up the nazi-brigade when they come
- Protect your users from abusive third parties.
Also remember that the kind of users you want to banhammer will:
- Aggressively argue that they're in the right
- Blatantly ignore your CoC
if your CoC discourages #GamerGate from showing up, that's a bonus.
Also remember that the ToC is not the CoC.
Don't go too broad on the ToC, as you may end up putting yourself in a situation where you're responsible to enforce them, and with 18k users that might be hard.
@tomharris *groan* Yah.
I've found that their native upset about CoC's "limiting" and "Policing" them is awesome and filtering them out.
Well, #GNUSocial lacks the IRC "G: Line" command, where you can ban a certain user across all servers in the network.
Thus it falls down to a set of K-Lines, individual per-server bans by the administrators.
So, you need the last point if you want to fix the first one. Since he's an elite hacker of the first degree, he'll have to be prevented from federating his own instance to yours.
( Do note the aggressive use of sarcasm in the last paragraph)
Spider
tom h
Chris