this post was submitted on 09 Jun 2023
376 points (100.0% liked)
Chat
306 readers
1 users here now
Relaxed section for discussion and debate that doesn't fit anywhere else. Whether it's advice, how your week is going, a link that's at the back of your mind, or something like that, it can likely go here.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I believe it's ban logs that are federated, not the bans themselves, but I don't have any proof. Could someone running a personal instance test this by banning a remote user and see if they can still interact with other remote instances?
Note that if a user is banned by their home instance, it's expected that they can't interact with any remote instance either, as all of their posts will pass through their home instance first.
If Beehaw bans from the site someone that is on a remote instance, that account can no longer interact with any Beehaw communities. If Beehaw bans from the community someone that is on a remote instance, that account can no longer interact in that community.
That makes sense, but I think what Smoke assumes from the federated mod logs is that if Beehaw bans me (a remote user) from beehaw.org and the ban message federates over to my home instance feddit.dk and lemmy.ml, I will be banned from feddit.dk and lemmy.ml as well. While it's unlikely that bans can federate between instances, I don't have any proof of this.
Ban logs do federate but the effects aren't in the way you describe. Otherwise, someone could just ban everyone over night by making their own little server, that'd be uh, quite chaotic to say the least? Thankfully, this is not how bans work through federation.
I can just envision the havoc that would ensue if someone could ban you from the instance you're the admin of.