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
    ·
    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
      8
      ·
      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
      6
      ·
      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.