#Hatespeech
Hmmm, I'm on #Mastodon for four days now and already received three #insulting comments from random people (#Russian #trolls) from random domains. #Blocking works. I don't know if #reporting works (and honestly, I don't envy the #admins/#moderators). But this is certainly more than I ever received on #Birdsite (though I never got into a shitstorm). However, it's low key. So I'll keep an eye on that.
Btw: Check the federated timeline from time to time. If you see such hateful posts, consider blocking the whole domain. Some domains just gather these people.
#Hatespeech
@trinsec Just sharing my experiences. I don't have an oppinion, yet.
But imho it shows that it *is* about policies after all.
#Hatespeech
@cweickhmann Sure thing, I'm just expanding on your experiences with some explanation. :)
An additional tip for anyone wondering if that whole domain is bad and should be blocked:
With posts from people from outside your instance, you can click on those 3 dots below their post and select 'Open <their instance> timeline' so you can browse their instance's timeline to see if it's really a cesspool to be blocked or if it's only this one individual.
It's a Qoto feature. Feel free to use it to your advantage!
#Hatespeech
@trinsec Yes, that's actually very nice (well what you see may not be as much ^^).
#Hatespeech
@cweickhmann You're on a server that's not blocking other instances, so you have an increased chance of encountering those lame posts, yup.
Many other instances pre-emptively block hate-related instances for you. Qoto, however, believes that this power should be in the hands of the user.