@[email protected] @timbray I gave up on crowdsourced blacklists long ago. My experience, in the context of email spam, is that eventually the admin has a tantrum and ends up blocking all of AWS or some shit.

@jwz @lwndow

Hmm interesting. Given the structure of the Fediverse, with thousands of instances, and the fact that brand-new troll instances pop up regularly, it'd be nice to have some sort of shared-block capability.

@timbray @[email protected] Sure, and it's probably necessary to try... but there seems to be something about operating a blocklist that eventually makes the operator lose their damn mind and double down on some scorched-earth change that, while probably "in accordance with policy", also ends up just breaking everything for everybody.
@jwz too much overlap with node module developer perhaps
@donw @jwz open source developers breaking dependency chains because they're being exploited is not the same as block list owners becoming unaccountable and abusive when maintaining a widely used block list, although i understand why it may seem similar at first. there's a power differential, and making a library unusable does not cause interpersonal harm
@hipsterelectron every tantrum-thrower thinks they have a good reason for their tantrum.