#fedinuke — Public Fediverse posts

FediNuke transparency update:

Added four domains to FediNuke:

• volk.love
• volk.network
• peertube.se
• tsundere.love

Receipts are available in my blocklists page.

#FediNuke

FediNuke transparency update:

Added four domains to FediNuke:

• volk.love
• volk.network
• peertube.se
• tsundere.love

Receipts are available in my blocklists page.

#FediNuke

FediNuke transparency update:

Added four domains to FediNuke:

• volk.love
• volk.network
• peertube.se
• tsundere.love

Receipts are available in my blocklists page.

#FediNuke

FediNuke transparency update:

Added four domains to FediNuke:

• volk.love
• volk.network
• peertube.se
• tsundere.love

Receipts are available in my blocklists page.

#FediNuke

FediNuke transparency update:

Added four domains to FediNuke:

• volk.love
• volk.network
• peertube.se
• tsundere.love

Receipts are available in my blocklists page.

#FediNuke

I updated my blocklists article to say something similar (diff).

I already include canary domains and document which ones they are to signal when staff imports a list without reading the docs, but I think a proper disclosure for use without review is still necessary. I document how to use the lists with review.

As always: none of this applies to small and private, or single-user instances.

#FediNuke

I updated my blocklists article to say something similar (diff).

I already include canary domains and document which ones they are to signal when staff imports a list without reading the docs, but I think a proper disclosure for use without review is still necessary. I document how to use the lists with review.

As always: none of this applies to small and private, or single-user instances.

#FediNuke

I updated my blocklists article to say something similar (diff).

I already include canary domains and document which ones they are to signal when staff imports a list without reading the docs, but I think a proper disclosure for use without review is still necessary. I document how to use the lists with review.

As always: none of this applies to small and private, or single-user instances.

#FediNuke

I updated my blocklists article to say something similar (diff).

I already include canary domains and document which ones they are to signal when staff imports a list without reading the docs, but I think a proper disclosure for use without review is still necessary. I document how to use the lists with review.

As always: none of this applies to small and private, or single-user instances.

#FediNuke

I updated my blocklists article to say something similar (diff).

I already include canary domains and document which ones they are to signal when staff imports a list without reading the docs, but I think a proper disclosure for use without review is still necessary. I document how to use the lists with review.

As always: none of this applies to small and private, or single-user instances.

#FediNuke

I have added parcero.casa to FediNuke. sorry for the delay.

See receipts

Sorry for being less active lately; I should have used the override process earlier. It is at consensus. By the time I added it, the domain stopped resolving. It replaced the old domain on FediNuke. If it stays down, I will eventually remove it altogether.

#FediNuke

I have added parcero.casa to FediNuke. sorry for the delay.

See receipts

Sorry for being less active lately; I should have used the override process earlier. It is at consensus. By the time I added it, the domain stopped resolving. It replaced the old domain on FediNuke. If it stays down, I will eventually remove it altogether.

#FediNuke

I have added parcero.casa to FediNuke. sorry for the delay.

See receipts

Sorry for being less active lately; I should have used the override process earlier. It is at consensus. By the time I added it, the domain stopped resolving. It replaced the old domain on FediNuke. If it stays down, I will eventually remove it altogether.

#FediNuke

I have added parcero.casa to FediNuke. sorry for the delay.

See receipts

Sorry for being less active lately; I should have used the override process earlier. It is at consensus. By the time I added it, the domain stopped resolving. It replaced the old domain on FediNuke. If it stays down, I will eventually remove it altogether.

#FediNuke

I have added parcero.casa to FediNuke. sorry for the delay.

See receipts

Sorry for being less active lately; I should have used the override process earlier. It is at consensus. By the time I added it, the domain stopped resolving. It replaced the old domain on FediNuke. If it stays down, I will eventually remove it altogether.

#FediNuke

contemplating making my tier-0 blocklist less easy to import but keeping FediNuke importable. now’s your chance to change my mind before i do that. also clarified some FediNuke criteria in my docs: one of it’s shortcomings is that entries must require minimal context, so it’s as clear-cut as possible. as always, it was never meant to be comprehensive.

#FediNuke

contemplating making my tier-0 blocklist less easy to import but keeping FediNuke importable. now’s your chance to change my mind before i do that. also clarified some FediNuke criteria in my docs: one of it’s shortcomings is that entries must require minimal context, so it’s as clear-cut as possible. as always, it was never meant to be comprehensive.

#FediNuke

contemplating making my tier-0 blocklist less easy to import but keeping FediNuke importable. now’s your chance to change my mind before i do that. also clarified some FediNuke criteria in my docs: one of it’s shortcomings is that entries must require minimal context, so it’s as clear-cut as possible. as always, it was never meant to be comprehensive.

#FediNuke

contemplating making my tier-0 blocklist less easy to import but keeping FediNuke importable. now’s your chance to change my mind before i do that. also clarified some FediNuke criteria in my docs: one of it’s shortcomings is that entries must require minimal context, so it’s as clear-cut as possible. as always, it was never meant to be comprehensive.

#FediNuke

contemplating making my tier-0 blocklist less easy to import but keeping FediNuke importable. now’s your chance to change my mind before i do that. also clarified some FediNuke criteria in my docs: one of it’s shortcomings is that entries must require minimal context, so it’s as clear-cut as possible. as always, it was never meant to be comprehensive.

#FediNuke

FediNuke transparency update:

• Added drinkanddrive.africa. See receipts on my receipt archive.
• Removed three dead domains (catgirl.life, vtuberfan.social, natehiggers.online). They have no DNS records, or redirect to a subdomain with no DNS records. Will properly comb through for dead domains at some point later.

#FediNuke

FediNuke transparency update:

• Added drinkanddrive.africa. See receipts on my receipt archive.
• Removed three dead domains (catgirl.life, vtuberfan.social, natehiggers.online). They have no DNS records, or redirect to a subdomain with no DNS records. Will properly comb through for dead domains at some point later.

#FediNuke

FediNuke transparency update:

• Added drinkanddrive.africa. See receipts on my receipt archive.
• Removed three dead domains (catgirl.life, vtuberfan.social, natehiggers.online). They have no DNS records, or redirect to a subdomain with no DNS records. Will properly comb through for dead domains at some point later.

#FediNuke

FediNuke transparency update:

• Added drinkanddrive.africa. See receipts on my receipt archive.
• Removed three dead domains (catgirl.life, vtuberfan.social, natehiggers.online). They have no DNS records, or redirect to a subdomain with no DNS records. Will properly comb through for dead domains at some point later.

#FediNuke

FediNuke transparency update:

• Added drinkanddrive.africa. See receipts on my receipt archive.
• Removed three dead domains (catgirl.life, vtuberfan.social, natehiggers.online). They have no DNS records, or redirect to a subdomain with no DNS records. Will properly comb through for dead domains at some point later.

#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

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

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

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

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

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

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

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

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

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