Like many of you, I woke up this morning to discover that our instance, along with lemmy.world, had been unexpectedly added to the beehaw block list. Although this development initially caught me off guard, the administrators at beehaw made an announcement shedding light on their decision.
The primary concern raised was our instance’s policy of open registration. Given my belief that the fediverse is still navigating its early stages, I believe that for it to mature, gain traction, and encourage adoption, it is crucial for instances to offer an uncomplicated and direct route for newcomers to join and participate. This was one of the reason I decided to launch this instance. However, I do acknowledge that this inclusive approach brings its unique challenges, including the potential for toxicity and trolls. Despite these hurdles, I maintain the conviction that our collective strength as a community can overcome these issues.
After this happened, the beehaw admins and I had a good chat about their decision. While our stances on registration policies might diverge, we realized that our ultimate goals are aligned: we both strive to foster communities that thrive in an atmosphere of safety and respect, where users can passionately engage in discussions and feel a sense of belonging.
Although the probability of an immediate reversal are slim given the current circumstances, I believe we have managed to identify common ground. It’s evident that, even in separation, we can unite to contribute positively to the broader fediverse community.
In the coming weeks or months, we plan to collaborate with other lemmy instance administrators to suggest enhancements and modifications to the lemmy project. Primarily, our proposals will concentrate on devising tools and features that empower us, as instance administrators, to moderate our platforms effectively.
In the meantime, while I understand may not be ideal for everyone, users who choose to participate on the beehaw instance will be required to register a separate account on their instance.
Thank you all for continuing to make this community great!
There has been an individual who flamed beehaw via our server. It happened fast and while we can moderate what this user does locally, we cannot moderate on other instances… as others have stated, there is not much moderation granularity, yet.
Ohhhhh, that was an interesting nugget of information that I didn’t previously understand. Thank you for sharing that.
So, the only way to keep a bad actor registered in your instance from flaming in another one would be to revoke their account completely, then?
Other servers probably need to be able to block individual users from posting anywhere on their instance if we don’t want to end up as mostly disfederated, isolated servers.
The only downside with that is that since this is a server with no join restrictions, trolls can keep spinning up new accounts to troll with and the current mod tools don’t have other ways to handle that.