News for hackers. Stuff that matters.
Re:Mastodon: Add end-to-end encryption API by progval on Tuesday May 26, 2020 @07:58AM (#23310005)
If the spammer spams thousands of people, it's a better use of everyone's time if an admin bans it once and for all.
Re:Mastodon: Add end-to-end encryption API by Hitton on Tuesday May 26, 2020 @08:32AM (#23310276)
Spamming thousands of people can be detected without knowing the content. And if you accept messages from other people than those you are following, you have to accept you will inevitably get some spam. It's like getting PGP encrypted email - you can't expect server spam filter to catch it based on its content and if you report it as a spam, server spam filter doesn't see the content.
Re:Mastodon: Add end-to-end encryption API by macieklaskus on Tuesday May 26, 2020 @08:19AM (#23310185)
There are other solutions to this problem that don't require 3rd party intervention. For example, users could follow each other's block lists.

If Bob spams thousands of accounts he'd quickly get on multiple block lists.

Re:Mastodon: Add end-to-end encryption API by loceng on Tuesday May 26, 2020 @08:22AM (#23310211)
Is Bob a verified, known identity, or does he simply create unlimited accounts and continue the spamming or abuse?
Re:Mastodon: Add end-to-end encryption API by drngdds on Tuesday May 26, 2020 @08:45AM (#23310399)
Mastodon is federated, so you already get to choose who your content moderators will be when you pick a server. Blocklists are just an informal and spammy-by-default version of that.