this post was submitted on 15 Jun 2023
99 points (100.0% liked)
Technology
37634 readers
173 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
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
It sounds like you are describing new user experience.
And I understand, coming from Reddit, how this can be a shock.
However, that's how Lemmy works.
Similar to how twitter users got a shock moving (or trying to move) to mastadon.
The very nature of the fediverse works better with more instances, where a single instance has fewer users and the communities are more focussed.
Beehaw hasn't "blacklisted everyone from...". They've defederated. Whilst it may seem similar, it's more nuanced. And that's what a lot of people don't understand.
Block-listing all users from lemmy.world from interacting with beehaw would be an amazing ability. That would put beehaw in a read-only state for users on lemmy.world, whilst still allowing beehaw users access to lemmy.world.
Unfortunately, the current admin/mod tools do not allow for that. And manually dealing with the huge influx of toxic users (posting death threats, illegal porn or trolling) was taking too much time.
Besides, the lemmy.world admin is working on custom tooling to deal with this issue. Because it is their users causing this issue, and it is their problem. And there is no higher authority - there are no Reddit admins to say "stop brigading".
Shitjustworks, last I heard, weren't responding to communication.
I have no doubts that beehaw will refederate as soon as Lemmy.world sorts their mod issues, or the Lemmy framework allows for more nuanced mod tools.
You have to remember that Lemmy is young.
It's been around for a few years, but the shear scale of what is happening now is less than 2 weeks old
It’s unfortunate if the sh.itjust.works folks aren’t speaking, their listed rules seem pretty reasonable and the problem users appear to be breaking the rules of that instance too.
We have talked with them and will work with other instances to push for better moderation tool. We have nothing against individual people or their communities. Let's keep that in mind.
This copy-and-pasted reply doesn't actually address what I was talking about.
The people who have a problem here aren't lemmy.world, it's beehaw. So while it's understandably polite for lemmy.world to moderate themselves, ultimately the tools you're going to need will be on beehaw's side, because even if lemmy.world does everything you could possibly desire there's going to be many other instances that allow open subscription in the future and you can't expect them all to do your policing for you.
This message was not copy-pasted nor was it addressed to you, I'm kinda confused why you think that.
But yes, beehaw needs moderations tools - we are working with other instances so that Lemmy - for everyone - can have better tools.
Also, we don't expect other instances to do policing for us, this is why we want better federation options so that people using Beehaw can interact with the outside but those that do not cultivate a culture that matches with what we want would not be able to interact on Beehaw.
Very weird, there appears to be a bug in kbin. I'm seeing your "We have talked with them..." comment as a response to dozens of different comments here, including one that I made, and now when I look through the thread my response to your comment is replicated in all those dozens of places as well. My apologies, that would explain why your response seemed like such a non-sequitur to me. I'll see if I can file a bug report about this.
Edit: here's the bug report.
Edit 2: I missed a duplicate bug report that was already filed for this issue
Thank you for filing the bug report - that is really weird... I hope kbin fixes that issue quickly because that's definitely gonna lead to some very off interpretations.