It looks like a new spamming tactic will be to set up your own instance and then just mass spam to other instances from there. Case in point, vive.im I’ve been noticing spam in one magazine from a user of this. I banned them, but they can still post for some reason. Decided to visit the instance and it looks like some default front page with ‘3’ active users. If you look at the user’s account on there they’ve made 12k posts already and seem to have a script set up to push their blogspam 3-4 times per minute.

  1. We need a clear process to report and get these kinds of things removed quickly.

  2. Bans need to work properly and stop these users from posting.

  • duringoverflow@kbin.social
    17·
    1 year ago

    i don’t agree. I think it is important to maintain a blacklist instead of a whitelist where people would then submit what they need to add which will then will need to be approved etc. It will decrease the federated experience.

    • crossmr@kbin.socialOP
      6·
      1 year ago

      That only works if you have a group of responsive admins who can watch that for abuse. It really hasn’t taken long for someone to figure out how to abuse that for spam.

      • SirNuke@kbin.social
        6·
        1 year ago

        I’m inclined to say I’m not a fan of my idea on a philosophical level, but we can’t ignore the practical considerations here either. Endlessly banning spam instances is not going to be fun and takes away time and effort on the admin’s part that could be better spent on useful things. A site clogged by spam is also not going to be useful, in which case it doesn’t matter how well you adhered to your principles.

        These interests are competing, but I think there’s a compromise to be found. I’m going to suggest rate limiting for new instances until they’ve produced a certain amount of content (so say until they’ve produced X comments+links with a minimum Y days), plus a system that automagically puts new instances in the timeout box if enough users report their content. Admins can manually skip the warm up period for new instances, and also review the timeout box to see if it’s actually a concern.

        • Haily@kbin.social
          3·
          1 year ago

          I think Lemmy may be doing something similar, actually. At least, I’ve noticed that smaller instances don’t seem to be federating nearly as well as larger instances. Obviously Mastodon have figured out a way around this as well, so it’s clearly doable.

      • Books@kbin.social
        1·
        1 year ago

        Can you share an example of an instance that is linked to kbin.social that has been spammy? I’m an example based learner, it will help me wrap my head around it.