Skip to main content


FediMeta, blocklist update, 1/3

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

This entry was edited (2 weeks ago)
in reply to Seirdy

FediMeta, blocklist update, 2/3

I also retired my tier-1 blocklist. It’s the least-used blocklist I have, and I’m managing several; it’s not worth the effort. Every new severity level demands more instances to carefully consider.

Without willingness to spend that effort, its existence encourages me to treat it like a dumping ground for other entries that don’t qualify for other lists instead of evaluating entries’ severity properly.

I will maintain it in private to shine a light on the latter phenomenon, but I won’t share it.

Before you protest, know that I’m maintaining six other blocklists:

  • FediNuke.txt
  • My tier0 list (might re-name)
  • BirdSiteLive, bird.makeup
  • Other bridges
  • Corporate social media (Threads, Medium, Minds, etc)
  • Spammy subdomains

They will be unaffected. If anything, they’ll improve.

#blocklists