I’ve set registration to Require application again, don’t like this bots creating accounts.

Also I’m running into email limitations. Using the Sendgrid Free plan of 100 emails per day, but if a couple of member have email notification on, I’m reaching that 100 very quickly. How do others handle the high email traffic ?

  • moneygrowsontrees@kbin.social
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    It serves the same point it served on Reddit. There are huge bot farms dedicated to shaping the social media landscape. There is a new social media “boom” so the bots want to get in on the ground floor.

  • godless@latte.isnot.coffee
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    Future spam accounts in the making. They are building large bot armies to either flood instances with their crap, or use them for vote manipulation, or a combination thereof.

  • bec@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I read somewhere that you can add a captcha to registration, maybe that’ll help filter some of the bots out?

  • RGB@lemmyfi.com
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    My modlog got spammed today by some script banning a lot of people for spam automatically. It’s getting wild. This was inevitable with the growth of Lemmy as a platform though.

    • majorswitcher@lemmyfly.orgOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      Mine too I see now. You can only ban a user when they have posted something right ? There is no list for admins of all users registered ? Maybe I’ll do it direct in the database…

      • thatcasualgamingguy@lemmy.nerdcore.social
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Just did that for my instance. Luckily it’s fairly easy. Since there were no human registrations after those bots I just looked up the lowest bot id in the local_user table which was 9 and then used delete from person where id in (select person_id from local_user where id >= 9);. Thanks to the references and triggers on the table, the rest of the database was also cleaned up by that, including the local_user table.

        • majorswitcher@lemmyfly.orgOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          For me it were the last 30 or something entries in local_user. They all didn’t have email_verified. I access the db through Postico. Also removed all other older accounts that didn’t verify their email address

  • sunaurus@lemm.ee
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Try enabling the captcha in your instance settings, it might help a bit as well!

    • underscores@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Captchas are mostly useless nowadays against any well designed bot. The only ones that sort of work are those ridiculously hard ones like several page math problems. And at that point a large portion of people can’t solve it either.

      They also tend to be full of trackers and are terrible for privacy. Plus they’re used to train corporate AIs.

      It can help temporarily, because a lot of bots don’t bother with captcha solvers, but all the spammers need to do is include a pre-made solver library and the bots are back.