Both !infosec@kbin.social and !science@kbin.social are being spammed constantly with opioid ads and other non-sense.

It’s quite annoying if you want to use the all-feed. I’ve blocked at least 6 spam accounts just today.

Just wanted to bring that to your attention. Thanks.

  • Link.wav [he/him]@beehaw.org
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    1 year ago

    You’re not taking action. This spammer is still posting, even though I reported him nearly an entire day ago.

    For all the time you have to type excuses, you could be smashing the ban button, but you don’t. This does not look like a “top priority” from this end. Stop making excuses and just ban the spam accounts. If you have communities without moderation, then close them. You’re managing this very poorly.

    Edit: Unbelievable! This spammer created yet another account. You’re not vetting applications at all, are you? This is totally on you. Fix it.

    • PenguinCoder@beehaw.org
      shield
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      I understand this is a frustrating experience dealing with so much crud in your feed. Admins and mods for many instances of Lemmy and Kbin are trying to work with the tools available to stem this. Attack the problem, not the person. Bee nice.

      Please don’t lash out at those trying to help you and the community. We certainly do appreciate your reports as well, hopefully we’ll find a solution that won’t require so much of your report efforts.

    • ernest@kbin.social
      link
      fedilink
      arrow-up
      10
      ·
      1 year ago

      Of course, I’m taking action, and on kbin.social, those posts have been removed, which you can verify. However, for some reason, it doesn’t always federate with Lemmy. It used to work before, but practically after every Lemmy update, there’s something to fix in the code, or it could be related to API limits because some requests receive a “fail” status in the queues. The same applies to spam from Lemmy instances - I had to manually clean up hundreds of posts from other instances because they didn’t always send AP requests, which I verified in the logs.

      Do you seriously believe that it’s a matter of individual accounts, and banning a user solves the problem?

      • Link.wav [he/him]@beehaw.org
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Am I taking crazy pills? Ban the user, or they’ll keep posting spam. Vet your applications like a valid instance instead of letting any spambot create an account.

        You are not taking action if all you’re doing is removing posts. You are handling this in an entirely inadequate and incompetent way, and you’ve made kbin a blight on the fediverse. Get your shit together.

        Do you seriously believe that it’s a matter of individual accounts, and banning a user solves the problem?

        It’s certainly better than allowing these accounts to continue to post harmful spam. Then when people sign up, there should be some red flags in their application that you can watch for. It’s not like these spammers are highly intelligent. They’re pretty blatantly spam accounts, especially when they have literally just a number’s difference in their username.

        • ernest@kbin.social
          link
          fedilink
          arrow-up
          9
          ·
          1 year ago

          By the end of September, kbin.social will receive an update that will address some of the issues. For now, I’m banning spam accounts, and registration is disabled. Additionally, external links are marked as “nofollow.” I just want to emphasize that this is not solely a kbin issue - I had to manually remove spam posts from Lemmy instances as well because moderation didn’t federate, which doesn’t happen with, for example, Mastodon.

          For now, the admin of your instance can choose to defederate or remove communities, as the admin of lemmy.world did. Once I’ve dealt with the update, I will reach out to other admins and discuss the possibility of restoring valuable posts.

        • ernest@kbin.social
          link
          fedilink
          arrow-up
          7
          ·
          1 year ago

          The problem is that at this scale and with this infrastructure, hotfixes are no longer as straightforward as they used to be - when I could solve these kinds of issues in a matter of hours.