@itorres This! Thank you 💚

@itorres It's a great way to build an echo chamber.

@itorres Well, to be honest. That wasn't about a single mod. That was about admins' response.
I completely agree with you that a single mod shouldn't be the reason. And they kinda wasn't.
When I discovered that something is going on my first thought was that surely admins will jump in and the issue will be solved one way or another.
But after reading a lot (a lot) of the Fosstodon hashtag it started to look differently. I've tried asking admins on the instance about what's going on.

@itorres

From what I've read and seen, a lot of people did try to resolve it, and were met with a brick wall from the fosstodon admin and their active support of a fascist mod.

When only one side is trying to resolve it and the other sticks their fingers in their ears to protect a bigoted POS... the only option then is to defederate to protect the majority of users from that individual.

It's shame that others may get caught up in the crossfire, but they can move to another instance or they can support the hateful rhetoric and fascistic behaviour of their mod... which makes them enablers and facilitators of and fully deserving of being defederated.

(EDIT) After reading OP's responses to others and their ignorance, arrogance refusal to understand simple concepts and their apparent tolerance of right wing bigots... I have to conclude that this person is a troll and trolls get the same treatment from me, an immediate block.

@itorres Groups which appoint far-right mods are, by definition, shitholes.

I'm optimistic fosstodon can move in a non-shithole direction if they own that mistake and commit to not doing anything like it again - but all I've seen so far is handwringing about how tiring it is to be admin for a site when folks notice you appoint far-right mods.

@itorres But that again is a proof there shouldn't be masive, huge instances, that when become toxic, are "too big to ban"

@itorres it's not the first problem with the way fosstodon manages its community, and not the first time the owners/admins decline to (a) acknowledge the issue and (b) take responsibility for making a bad decision.

it is also grossly irresponsible to allow to grow an instance to such size (60k users overall, 8k active users) without taking care of the succesion of management; accidents and health problems happen, and if the instance is not just a vanity project, the admins should have worked it out at some stage.

fosstodon

@itorres

"What I know is that deciding to block a historical instance because one of their mods misbehaved is a ShitMove™.

Good news then, because as far as I've seen it's been taken into consideration as one of many incidents involving the server.

You can only shit in the river so many times before people move upstream of you.

@itorres Ah, yes, that excellent social media tradition of weighing in on a topic which you admit you know nothing about. Very good, carry on.

@itorres It's fine if you've opted not to read into the situation with Fosstodon in detail, nobody is required to do that, but then I would suggest also not trying to pass a value judgment on a situation that by your own admission you have no idea about.

@itorres

Nazi Bar rule.

Even worse when one of the bartenders is a Nazi.

fosstodon