So, is mastodon.social blocked on this instance?
@nopunincluded yes, it is
@host I understand the decision, and don't wish to challenge it. I do find it sad that we've removed access this hard. Is this a temporary measure or permanent?

@nopunincluded the decision doesnt have to be permanent, and thats a valid statement for a few other instance we have blocked.

That said, with mastodon.social it is more complex, mostly for historical reason.

It is also not moderated (well moderated automatically which we have seen being weaponised agaisnt a black user already).

Federating with it, means being m.s de facto moderation team.

Lots of moderation feature are missing because m.s admin decided agaisnt it.

@host thank you for explaining. I understand the complexity of drawing the line between moderation and inclusivity. It's hard to gauge how exclusive you need to be to be effectively moderated. I'm sorry to hear someone on this instance was targeted, that's terrible.

@nopunincluded admins have the choice between "I put the finger in my ears so I cannot hear you" & "we now live in parallel universe that mostly interests but not for me and you".

In this case the owner of the instance also steer the software project.

And the reason we don't have many moderation option is because he doesnt want them.

(Even when the code is done, reviewed, tested, basically ready to go, he still doesnt want it.)

So we are left to block a large chunk of new people, sadly.