/kbin meta @kbin.social MemeCollector @kbin.social 8 mo. ago

Magazine bans not federating with lemmy.world (and potentially others)

I've just discovered that lemmy.world (and potentially other) users I've banned from my magazine are still able to comment, comments I can't see on kbin but that do show up on lemmy.world.
(E: I already knew removed comments still show up on other instances, but assumed that sorts itself out in time, but now I'm not so sure)

This makes modding futile.

I want to make sure my space is safe and not hostile to those of us who already deal with bullshit everywhere else, and I can't do that when this is the case.

How do we fix this?

12 comments

A bug was filed about this issue four months ago and ernest has commented on that thread, so he's aware of the problem. So far, no solution has been reached, which makes me as a moderator extremely demotivated. I don't want to put effort into building a community if comments that break community rules are federated but moderation is not.
- Thanks for this info, I guess it's good to know it's on the to do list, but I completely agree, since realising this my motivation to post, knowing my moderation doesn't have any effect on a large chunk of users, has dropped significantly..
  
  Is there a place to check for updates on this, is the post you shared it?
  
  The bug report is the way to track this. Tho sometimes ernest makes posts in this magazine to share what's happening.
This is actually due to the way these platforms work. When a user comments on a comment or post on their instance it will be shown on their instance. It's then sent on to the owning instance of that comment or post. That owning instance then forwards it on to all interested parties (magazine instance, commenters instance).

Any instance in that chain can refuse to forward or broadcast that message due to a block, but the users own instance will likely always show that post. Ideally they would not do that and would be made aware of a block but that is a bit of a grey area in ActivityPub implementations.
- Thanks for explaining, but wow, that's really unfortunate and seems like something that needs addressing, especially since they're the biggest instance.
  I thought the whole point was to have the freedom to associate and disassociate with the content of our choosing?
  
  Is there a way to know if/when this is fixed? Because I honestly don't feel comfortable posting the content I do to my target audience if I can't properly keep the trash out.
  
  What you're asking for is control over other intance's users. That's never gonna happen.
- @adam thank you for explaining this. Am I correct to understand, then, that this is something about which we ought to approach the #activityPub devs, rather than ernest?
  
  Ernest's comment that ActivityPub tries to federate moderation (but isn't ?why) was very interesting.
  
  It seems to me, on the face of it at least, that moderation is a key part of any social medium.
I would also love it if we could prevent microblogs from federating to a magazine, as banning currently does nothing to prevent this issue and seems a bit counterintuitive. Similar to the concerns OP raised RE: commenting, this seems like it could be another vector for bad actors to attack from.
- prevent microblogs from federating to a magazine
  
  I didn't even know this was a thing, but definitely sounds like it needs looking in to as well.
From what I've heard another big issue is that moderation actions don't get federated to lemmy anyway. Beehaw was considering (or did it already) blocking Kbin domains because for example, posts deleted by moderators here don't get deleted on the lemmy instance. So even if you do moderate it's not applied to federated instances 🙁

You've viewed 12 comments.