home.social

#fedinuke — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #fedinuke, aggregated by home.social.

fetched live
  1. @gryzor @gryzor They keep you from using certain instances with them. #Moshidon uses the #Fedinuke list specifically to censor instances.
  2. @gryzor @gryzor They keep you from using certain instances with them. #Moshidon uses the #Fedinuke list specifically to censor instances.
  3. @nikclayton @nikclayton #NoAuthority is the instance I want to use on it. #Moshidon uses a blocklist called #Fedinuke which prevents certain instances from being used. It's intentional, like the same decision for #Tusky was (I don't know if #Tusky still does censorship or not though)
  4. @nikclayton @nikclayton #NoAuthority is the instance I want to use on it. #Moshidon uses a blocklist called #Fedinuke which prevents certain instances from being used. It's intentional, like the same decision for #Tusky was (I don't know if #Tusky still does censorship or not though)
  5. CW: blocklists, 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

  6. CW: blocklists, 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

  7. CW: re: hot take, moderation tooling

    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

  8. CW: re: hot take, moderation tooling

    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

  9. CW: FediMeta, bloclists update

    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

  10. CW: FediMeta, blocklists update

    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

  11. CW: FediMeta, blocklists update.

    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

  12. CW: FediMeta, blocklists update.

    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

  13. CW: FediMeta, blocklist update

    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

  14. CW: FediMeta, blocklist update

    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

  15. My Friendica instance got hit with #fedinuke / activitypub-troll.cf. Took abit to properly clean up after that. What's with some people

  16. CW: 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

  17. CW: 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

  18. 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

  19. 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

  20. CW: blocklists

    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

  21. CW: blocklists

    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

  22. CW: FediMeta, FediNuke blocklist

    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

  23. CW: FediMeta, FediNuke blocklist

    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

  24. CW: FediMeta, FediNuke

    #FediNuke blocklist transparency update:

  25. CW: FediMeta, FediNuke

    #FediNuke blocklist transparency update:

  26. CW: Federated Moderation / Staff Notice to all Fediverse Staff: potential mass-signup from bad actor

    Someone is making accounts on multiple instances, usually with names like...
    - FuckPoon
    - FuckPooners
    ...with the specific purpose of threatening, harassing, and doxing, mainly targeting transgender / queer users. This is not the first I have heard, nor the only instances I have heard of being hit with this.

    All #Moderation / #Moderators / #FediMods / #Admin / #Admins / #FediAdmin / #Staff / #Fedistaff should be on the lookout for new users with those account names, and should likely ban on sight.

    #FediBlock / #FediNuke tag for good measure: keep an eye out for them.

    I will update this post if I see more information about who it is.

    ...

    For the non-staff bystanders looking at this, I want to point out, this happens on every social network, but the difference is here, you can see staff going on mass alert over it.

    CC @rangaku, whose post this is an extension of

  27. CW: Federated Moderation / Staff Notice to all Fediverse Staff: potential mass-signup from bad actor

    Someone is making accounts on multiple instances, usually with names like...
    - FuckPoon
    - FuckPooners
    ...with the specific purpose of threatening, harassing, and doxing, mainly targeting transgender / queer users. This is not the first I have heard, nor the only instances I have heard of being hit with this.

    All / / / / / / / should be on the lookout for new users with those account names, and should likely ban on sight.

    / tag for good measure: keep an eye out for them.

    I will update this post if I see more information about who it is.

    ...

    For the non-staff bystanders looking at this, I want to point out, this happens on every social network, but the difference is here, you can see staff going on mass alert over it.

    CC @rangaku, whose post this is an extension of

  28. Well, that was an adventure. Today I learned how to defederate trolls. Is there a good list out there I can import to prevent this?

    UPDATE: Just found the #FediNuke list. That’ll be a good start. I see some of today’s miscreants’ domains in there.

    #Mastodon #MastodonAdmins #MastodonModeration

  29. Well, that was an adventure. Today I learned how to defederate trolls. Is there a good list out there I can import to prevent this?

    UPDATE: Just found the #FediNuke list. That’ll be a good start. I see some of today’s miscreants’ domains in there.

    #Mastodon #MastodonAdmins #MastodonModeration

  30. CW: FediMeta, FediNuke

    #FediNuke updates:

  31. CW: FediMeta, FediNuke

    #FediNuke updates:

  32. CW: FediMeta, FediNuke

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

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

  33. CW: FediMeta, FediNuke

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

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

  34. #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.
  35. #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.
  36. CW: FediBlock: turturea.online - racism, sexism, use of admin tools for cross server harassment

    #FediBlock #FediNuke
    turturea.online

    Seems to be a single user instance, unsure because they are clearly rules, but the admin, luciferian, has been trying to figure out who is making reports and publicly posting their accounts, even tagging one of them out right.

    This is a clear case of harassment and violation of all good faith standards, warranting an immediate block on our end.

    This is on top of the fact that luciferian was getting reported for a bunch of vaguely racist/sexist bad takes, which he apparently thinks were "fun", so I'm going to go ahead and assume he's a #troll.

  37. CW: FediBlock: turturea.online - racism, sexism, use of admin tools for cross server harassment


    turturea.online

    Seems to be a single user instance, unsure because they are clearly rules, but the admin, luciferian, has been trying to figure out who is making reports and publicly posting their accounts, even tagging one of them out right.

    This is a clear case of harassment and violation of all good faith standards, warranting an immediate block on our end.

    This is on top of the fact that luciferian was getting reported for a bunch of vaguely racist/sexist bad takes, which he apparently thinks were "fun", so I'm going to go ahead and assume he's a .

  38. CW: FediBlock

    Some #FediBlock entries:

    shortstacksran.ch: run by admin of needs.vodka and the former tnd.lol, continuation of squid.kids and shortstackran.ch. (note the extra “s” this time).

    social.immibis.com: sealioning, block-evasion, generally being a huge asshole. Less major than the prior entry.

    Blocklist updates:

    Short Stacks Ranch has been added to my #FediNuke and my tier-0 blocklists, as it’s the successor to an older FediNuke entry (squid.kids) and run by the admin of another FediNuke entry (needs.vodka). Documentation and receipts.

    #FediBlockDetails

    RE: https://pleroma.envs.net/objects/75b0992c-28e9-4422-a373-06ee986ed334

  39. CW: FediBlock

    Some #FediBlock entries:

    shortstacksran.ch: run by admin of needs.vodka and the former tnd.lol, continuation of squid.kids and shortstackran.ch. (note the extra “s” this time).

    social.immibis.com: sealioning, block-evasion, generally being a huge asshole. Less major than the prior entry.

    Blocklist updates:

    Short Stacks Ranch has been added to my #FediNuke and my tier-0 blocklists, as it’s the successor to an older FediNuke entry (squid.kids) and run by the admin of another FediNuke entry (needs.vodka). Documentation and receipts.

    #FediBlockDetails

    RE: https://pleroma.envs.net/objects/75b0992c-28e9-4422-a373-06ee986ed334

  40. Now might be the time to implement the #FediNuke blocklist as one of these instances may have temporarily taken Calckey Social out of action.

    #fediadmin #calckeyadmin #mastoadmin

    RE:
    https://atomicpoet.org/objects/259cfadc-90b5-442b-bb3f-20a4f1a67fc7