• dansup@mastodon.socialOP
    1·
    4 months ago

    I want to mention my intent to collaborate with trusted community providers like @iftas@mastodon.iftas.org to share data and provide the community with multiple options!

    We all can agree that spam sucks, so let’s work together the best we can and fix this 💪

    #fuckSpam

        • Melroy van den Berg@mastodon.melroy.org
          1·
          4 months ago

          @dansup@mastodon.social @iftas@mastodon.iftas.org we see mainly a lot of fake user account creation. If you could help prevent bots to create accounts in the first place that would be awesome. Hcaptcha isn’t helping anymore…

          @jerry@infosec.exchange proposed to implement a manual approval step for newly created accounts. Which could of course work.
          But additional ideas and implementations are welcome!

    • Matt Baer@writing.exchange
      1·
      4 months ago

      @dansup@mastodon.social @iftas@mastodon.iftas.org Would love to join forces with you all to tackle this! It’s a huge problem on open @writefreely@writing.exchange instances.

  • Rob Bos@mastodon.novylen.net
    1·
    4 months ago

    @dansup@mastodon.social That sounds pretty cool. I’ve often wondered whether I could pipe mastodon posts into rspamd to classify them, leveraging existing email filters. It seems like it’d be the same basic idea.

  • ashakoen@mastodon.social
    1·
    4 months ago

    @dansup@mastodon.social This sounds good and reminds me of the early days of fighting email spam with Spamassasin.

  • Troed Sångberg@ioc.exchange
    1·
    4 months ago

    @dansup@mastodon.social I don’t know if this is relevant, but as one of the moderators on IOCX I see an immense amount of SEO spam signups. We ban them on sight, and thus very very few such posts get onto the local timeline. I’m certain the exact same account is created on multiple Mastodon-servers, so we should really have a sort of “two instances have banned this very same account so block it”-functionality.