I mean I agree with your description of the problem and the changes you propose.

I’m coding it now, should be deployed today.

But only those. So you could still post to communities on that instance locally that you had not posted on prior to being instance banned.

We had this happen yesterday where a troll from a currently unmoderated instance signed up to it. They were banned from everywhere else, but they were still posting gore on communities they were banned from and local subscribers would still see it.

Maybe I’m wrong, but that’s the consequence of flexibility and sandboxing.

I mean combining/integrating instance-bans with community bans could make them federate like any other community ban. So on a first glance it seems to me it’ll just propagate anywhere and solve this issue entirely? Of course it doesn’t exclude any other (prior or more specific) patching.

I feel as a user, I’d expect an instance ban to be the exact same thing as a ban in every local community. Show up a similar way in the modlog and everywhere. And of course their content on remote communities needs to be hidden as well. Unless I’m a mod, then I need to see it.

And I’d welcome if these things federated in a way. AFAIK community bans do federate. Instance bans don’t federate. So if for example someone gets banned because they molest other people, the outcome depends on who takes action in which role.

And there’s a dozen of instances I trust, and once their awesome admin team decides to ban someone, I regularly want that stuff gone on my instance as well. I think as of now it’s always up to a malicious user’s home instance to take action?! So spammers, trolls, bots… Might still be around on my instance until the specific admin team caters to them. I feel I could as well trust whatever decisions piefed.social (for example) came up with and reflect that on my website. That’s often way faster. Also faster than some (badly moderated) communities.