(What makes this an unpopular opinion is that I’m basically advocating for jettisoning an entire Fediverse platform rather than just riding out the rough patch.)

I admin a Lemmy instance, and the amount of spam we get from Kbin and have to deal with is absolutely insane. Every morning I have to spend at least 15 minutes cleaning it up: responding to reports, banning accounts, purging posts, and pruning the images. And it’s more of that all through the day, just in smaller bites.

Many times I’ve toyed with the idea of de-federating Kbin instances completely, but I don’t want to cut off interactions with their legit users. The legit users are not the problem and are very much welcome.

Side note: If you’re reading this and thinking “What Kbin spam?”, then you should reach out to your instance admin(s) and give them a big ‘thank you’. The spam from Kbin is not just a “me” problem.

The underlying issue is that Kbin mod actions do not federate to Lemmy. At all. The mods of their magazines can (and probably are) doing a great job cleaning up spam, but once that spam goes out, it’s a one-way trip to Lemmy and completely up to the instance admins to deal with. For comparison, on Lemmy, the community mods can remove the spam which will then issue a removal action on instances that received it via federation.

I’ve tried various ways to unsubscribe and remove Kbin communities on my instance, but the “unsubscribe” doesn’t seem to be honored by Kbin, either. So I’m stuck receiving content that’s 90%+ spam and having to deal with it every day with no end in sight (barring de-federating Kbin completely). The only thing that sort-of works is hiding the Kbin magazines on my end, but that just hides the spam, too, and I’m still stuck storing it on my system.

So yeah, life for Lemmy admins would be easier if Kbin users would make the switch and I could just de-fed from Kbin without losing the good people.

  • Seraph@kbin.social
    link
    fedilink
    arrow-up
    5
    ·
    1 year ago

    Ernest has been working on a major update, but it appears to be delayed.

    Thank you for not simply defederating. Understood that something has to change with the spam problem and it’s been over a month of it being bad. Thanks again for managing the spam.

  • Electromagnetic@lemmynsfw.com
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    I would just defederate and tell those users if they want to see your instance then they’d better clean up their own first.

    Would you invite someone over to your house who makes a mess every time? Eventually you’re going to get sick of cleaning up their messes and tell them to stop coming to your house.

    • towerful@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Kbin mods probably do clean up their own.
      But their cleaning doesn’t federate (ie a mod deleting a post won’t issue a federation deletion request)

  • inasaba@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    The amount of spam is horrendous. Once we get the instance blocking feature, I’ll be blocking Kbin immediately.

  • Zellith@kbin.social
    link
    fedilink
    arrow-up
    0
    arrow-down
    1
    ·
    1 year ago

    I’m against lemmy for the fact that introducing new users is a pain in the ass. Tell em to type lemmy into google and you get stuff about a musician. Tell them about kbin and they get stuff about the fediverse. Lemmy is just a really bad name.

    • rentar42@kbin.social
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      As a kbin user myself I don’t think that’s a good solution to the issue. If one vehicle on the road is splashing all the others with manure then the solution isn’t just for everyone to get into that one vehicle …

      • MxM111@kbin.social
        link
        fedilink
        arrow-up
        0
        arrow-down
        1
        ·
        1 year ago

        Well, it solves the problem. I agree the solution is ridiculous. But that’s my point - it is as ridiculous as the “unpopular opinion” of the original post.