@dansup Anti-spam for email works in a similar way--abusive hosts are reported to and listed by a variety of different providers, and each independent email host has the ability to refer to whichever lists it trusts. We can already see something similar shaping up for fedi in the form of Oliphant's lists, Ro's TheBadPlace, and such. Having lists that break down block reasons (i.e. spam, harrassment, scraping, etc) is probably the next step. Get ten of those running and we're good to go lol.

@dansup why couldn't this service be based on federation? Thus there could be more than one, with different standards, and admins could migrate between them?

@dansup

> > "I know centralization is the anti thesis to federation, but when it comes to abuse and spam detection/mitigation, I think the fediverse needs an optional centralized and trusted service to share abuse/spam intelligence across instances so admins can better moderate their services"

I know of one guy who is working something like that: https://thebad.space/about . "Spam" here also includes instances who give power to people who are abusive and hateful. It is run by @Are0h

@dansup Why don't we start with Mastodon support for captcha first....

@dansup what if the structure & data were singular (for a distribution), but distributed like torrents. Contributions via source-control. Any folks could PR / MR changes to an upstream and torrent out local copies. That way it's still not centralised as such.

@dansup essentially what wordpress did with the kismet spam detection Plugin for comments.