I’m sure you all remember the very very funny time we voted to ban the admins of DBZero but stay federated with the instance. It’s still very funny, but it turns out that banning them has had an side effect that I, at least, didn’t consider at the time: their mod actions don’t federate anymore either.
See Hexbear post here: https://hexbear.net/post/4342876
After commenting, I went to look at what people were saying on the original post, and as you can see yourself, the post has been deleted on .ee and DBZero. Looking in the modlog over there it was deleted almost immediately after posting, but still exists as a federated post.
The above post is a non-issue and I don’t have examples of harmful content making it through, but the implication here is that db0 and unruffled’s (and indeed any admin or mod we’ve banned without defederating from) attempts to remove harmful content will not federate, unintentionally exposing our users to it.
Unless our admins have some way to bridge the gap I’m afraid we may have to defederate in order to maintain the safety of our user base.
Someone needs to update the API specifically for this bit.
We should impose posting tariffs on them and give our admins an External Radlib Censoring Service special privilege to keep those posts under control.
Edit: Seriously though, couldn’t we just get each comm to ban the DB0 admins separately, then unban them from the site? It’s functionally the same as having them sitebanned but should still let their mod actions be federated.
@CARCOSA@hexbear.net @liberal@hexbear.net @ella@hexbear.net @Alaskaball@hexbear.net @KiraNerys@hexbear.net @Lyudmila@hexbear.net @therestoftheadminsigotboredoftyping
Ty we’re now aware of it.