Skip to main content

Search

Items tagged with: FediNuke


Got two blocklist updates today, and a non-update with private visibility. First, a FediNuke/tier0.csv transparency update:

I override-added an instance to FediNuke using my documented override process: caekis.love.

Was already near consensus, and the admin was already in receipts for the gleasonator.com FediNuke entry.

See the many receipts for caekis.love in my receipt archive. The severity was enough to warrant inclusion.

#FediNuke


FediNuke/tier0.csv transparency update:

I override-added an instance to FediNuke using my documented override process.

feministwiki.org (subdomain “fedi.”): I blocked this on envs back in June proactively after it was automatically queued for manual review. The decision was easy, given the blatant transmisia on their root domain.

Since then, additional receipts have cropped up and they’ve been blocked by enough bias sources for me to do the override process. I added it to my shared lists, inc. FediNuke. Receipts on my receipt archive.

Severity is on par with the likes of spinster.xyz.

#FediNuke


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


FediNuke/tier0.csv transparency update:

Added some new bias sources to replace a removed one, and increased the consensus requirement. This caused some removals.

No new instances added to FediNuke. Two dead instances removed:

  • noagendasocial.nl
  • theapex.social

Removed 16 dead instances from my larger tier0.csv list. After these changes, another 9 instances failed to meet the consensus requirement for inclusion without overrides. I used my override process to add back 5 that were of sufficient severity. See more about my override process: I can force-add instances that almost have the minimum consensus requirement, with minimal overhead.

#FediNuke


Sensitive content


#FediNuke updates:


Added zhub.link to #FediNuke. zhub.link receipts.

Not tagging #/FediBlock since it’s been there a couple times.


#Fedinuke updates from the past few weeks:

  • promote crlf.ninja to FediNuke. crlf receipts.
  • Nuke fsebugoutzone.org, the new home of FreeSpeechExtremist. FSE/FBZ receipts. Thresholds for adding a dolain to FediNuke are lower if there are receipts showing that the domain is run by the same people as another FediNuke domain.