#blocklist update:
Added ts.net to my spammy-subdomains.txt list. While I have been aware of this for the past year, the number of subdomains on fedi has increased and the spam risk is too great (at least one person reported spam).
I should have added this months ago, to be honest: free easily-created subdomains and partially-managed hosting (networking) all in one for a product with sufficient popularity without heavy moderation of spam generally spells out a terrible place way to run an instance. Get a domain name.
For more about spammy-subdomains, see the supplementary blocklists section of my fediverse blocklists.
Seirdy
in reply to Seirdy • • •Moreover, I’ve had an increase in requests to add entries to shared blocklists. I normally don’t take requests for shared lists except in extreme situations, and in those cases I only do overrides as part of the process documented in the article. If I think an override is controversial, I ask a couple sources most likely to disagree; if multiple sources are opposed to adding an entry that overrides consensus, I don’t.
The point of FediNuke is to show what basically everyone agrees should be blocked, and that leaves out a lot of awful (and less-awful) entries. The goal isn’t to make a blocklist that’s enough; it’s to make a blocklist whose entries you probably agree with. As the docs say, this list is not comprehensive. It’s a huge compromise. There’s a reason why our blocklist isn’t just FediNuke; FediNuke is a list to compare other lists to, or a starting point for blocklist-skeptics. If you choose to trust FediNuke (and it’s fine if you don’t; I’m not “making” anybody use it on principle), then your list should eventually be a superset of what you import from it.
#FediNuke