No. The instance should moderate its own users. When they allow users to continue abuse, the instance should be blocked. Instances that condone abusive communities hurt the whole platform.
No. The instance should moderate its own users. When they allow users to continue abuse, the instance should be blocked. Instances that condone abusive communities hurt the whole platform.
You were downvoted but you’re right. What’s the cutesy nickname for people who use email? Do these people still say they’re surfing the information superhighway?
Explicit policies are better than implicit policies. A code of conduct shouldn’t consist of unwritten rules. Maybe this is why you were rejected? It seems like you didn’t understand the purpose or content of their policies when you applied.
Sure, blocking the sun will surely be easier and more effective than taxing the rich assholes causing climate change.
I would also like multi-account support. We need both alts and throwaways.
This analogy should be the top comment. Fediverse services are like email services. They’re basically interchangeable. If your email service starts to suck, you get a new email address. It’s a huge pain to move all your old email, copy your contacts, set up redirections, and then change your contact info everywhere, but what’s the alternative? Are you not going to have an email address?
If ActivityPub services become the kind of de facto standard that email did, unless you’re a server admin the instances will fade into the background noise of the internet, just like your email server has. Once we establish the standards on how a server should be maintained and moderated, it will become easier to see and ban rogue operators, just the way we do with email spammers now.
Does anybody worry about the political leanings of their office Exchange365 administrator?
This is how I do it as well. Shell scripts that I include in a project are named with a .sh extension so other users can identify them easily. Scripts that I want to run as commands often are in my $HOME/bin/ and don’t have an extension. Sometimes those are convenience symlinks with easier names, so ~/bin/example might be a link to ~/repos/example-project/example-script-with-long-name.sh.