Gregory's Server@ajroach42 But this is a super extreme case don't you think?
and also, this is not the case of one instance being troublesome, in which case yeah sure just cut off ties. People could just block that account preemptively.
If the account was active then 100% he would have been ejected. But who's to know what kind of content someone might post when the account isn't even used? Do you pre-ban people "just in case"? Is that ethical? How far will you go to protect your users?
@bl00dberri I don't know the details of this case, so I won't comment on it.
I will say that when a notorious bigot made an account on mastodonapp.uk, I notified them that the person in question was a notorious bigot, and suspended the instance 24 hours later.
They said, essentially "this person hasn't violated our rules yet" which is kind of like saying "That white supremacist hasn't attacked anyone in front of me"
When someone shows you who they are, you have to believe them. If an instance is willing to accept a known bigot, because they haven't done anything bigoted "on this platform yet" that's just providing cover.
Again, I don't know the details of this instance, maybe folks are blowing it out of proportion, but it sounds like an instance admin choosing to protect an unused account from a known abuser, rather than proactively take a stance against bigotry.
@bl00dberri I don't know the details of this case, so I won't comment on it.
I will say that when a notorious bigot made an account on mastodonapp.uk, I notified them that the person in question was a notorious bigot, and suspended the instance 24 hours later.
They said, essentially "this person hasn't violated our rules yet" which is kind of like saying "That white supremacist hasn't attacked anyone in front of me"