this post was submitted on 17 Oct 2023
0 points (NaN% liked)
Fediverse
19 readers
2 users here now
This magazine is dedicated to discussions on the federated social networking ecosystem, which includes decentralized and open-source social media platforms. Whether you are a user, developer, or simply interested in the concept of decentralized social media, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as the benefits and challenges of decentralized social media, new and existing federated platforms, and more. From the latest developments and trends to ethical considerations and the future of federated social media, this category covers a wide range of topics related to the Fediverse.
founded 2 years ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
kbin.social's admin (and kbin currently only supports one admin per instance) is also the main dev.
As I understand it, the sudden unexpected popularity of kbin caused infrastructure issues and made fixing bugs and limitations more important, while he still has to reach his feature goals to secure funding so he can actually continue working on kbin full-time. Additionally, real life had a lot of negative surprises in store he had to deal with.
All in all, he hasn't had much time at all to properly moderate the instance, And the past two weeks he's been gone entirely for real life reasons, leaving the instance unmoderated.
It's not an issue with the software itself, just with kbin.social (and of course other badly moderated instances) specifically.
Yes, there's clearly a moderation problem, but it's not just kbin.social.
To rephrase the question: why is it that practically all the insufficiently moderated sites are kbin instances?
An overwhelmed admin could partially explain why a lot of spam comes from a particular instance. But it wouldn't explain why most of the small instances generating spam have chosen kbin instead of lemmy.
that's not entirely accurate.
the main problem for non-kbin users, as @ono@lemmy.ca is using lemmy, is that kbin moderation actions, such as a moderator or admin removing spam will not federate to lemmy, as this is not implemented yet.
for a lemmy user, it appears that kbin doesn't have any moderation at all, while spam is being removed for kbin(.social) users at least.
for this reason, several lemmy instances have already either defederated from kbin or removed kbin communities from their instance.