Hello everyone,

Recently we have been dealing with a lot of spam from the kbin.social communities. There is a bug in kbin where moderation tasks are not federated to other instances. That means even if a moderator over at kbin removes a post, it will still be visible on Lemmy instances and it’s up to the instance admins to clean it up.

There have been talks about this in the Lemmy admin channels with some instances considering defederating from kbin.social - and others who have already made that step.

We don’t want to defederate, because we know this would impact the kbin community greatly - but we have to do something. That’s why we have currently removed most of the kbin communities from Lemmy World, making them unavailable to our users. But the kbin users can still view and interact with our communities and users.

This means that those spam-accounts will stil be able to post in our communities too, but at least it makes the task of moderation already a little bit lighter on our team. But it was either this or defederation. The moderation tools on kbin are in an even worse state then Lemmy’s.

We will keep monitoring the situation and will keep you up to date should anything change.

We hope you understand and support our decision.

The Lemmy World team

  • Anonymousllama@lemmy.world
    link
    fedilink
    arrow-up
    22
    ·
    1 year ago

    There’s been a heap of development going on with kbin recently, with a release upcoming. Overall the development process has been a bit slow with Ernest (the guy who owns the project) having personal issues to resolve.

    Definitely the moderation process needs to be improved so that we have better ways of addressing spam so it doesn’t bother other instances.

    Personally I’m of the opinion that we should be using a metric based system where we weigh in the users date or creation, overall interactivity, upvote / downvote ratio and other data to potentially flag spam users. But honestly fighting spam is really hard and all of that would have to be built (plus it’s a public repo so bad actors could look for how this is pieced together and find new ways to get past)