Conversation

Notices

1. :verified_2:防空識別區𝒔𝒐𝒄𝟶 (adiz@soc0.outrnat.nl)'s status on Wednesday, 27-Sep-2023 02:52:59 JST :verified_2:防空識別區𝒔𝒐𝒄𝟶

   Wrote about this 2 days ago. Appears today that this instance is now on the Oliphant "tier 0" block-list ("[r]equires 60-80% consensus on blocks to appear on this list"). For reference, soc0.outrnat.nl is, effectively, a single-use instance at the moment. I am virtually the sole inhabitant. Regardless, I maintain a robust terms of service which I hold myself to, I widely defederate from hostile or offensive instances, I'm a pretty open leftist, and I don't tolerate hateful rhetoric or harmful content here. I have regularly described the content curation objective here to prune the Fediverse into a comfortable, constructive, friendly environment.
   
   Additionally, I know my inclusion on these block-lists is wholly inorganic, not only due to the laughable logic surrounding "algorithmic" block-lists (detailed in the quoted post), but, also, because I can trace the original blocks that started the ball rolling on this Fediverse butterfly-effect: pleroma.envs.net, cathode.church, and mastodon.art.
   
   These 3 hostile instances blocked this instance almost immediately, and they did it by blocking the top-domain, not the sub-domain: outrnat.nl. Anyone who would have come across this instance and found the content objectionable or harmful would, one would think, organically block this instance's sub-domain: soc0.outrnat.nl; Right? Not the top-domain, which isn't a Fediverse instance. Instead, what I've seen is that the 3 bad actor instances listed above blocked the top-domain here in quick succession (it only takes 1 for others to immediately and blindly follow).
   
   What happened then is others, also, quickly and blindly followed suit. I cannot find any instances blocking the soc0.outrnat.nl sub-domain, but there are now plenty blocking the top-domain, outrnat.nl. Why? Because they saw it blocked by an instance and followed along. What happens then? Others see it blocked by an instance and follow along. Like a feedback-loop this festers and grows. Then, these major, centralized, "algorithmic" block-lists decide that, "algorithmically", due to a certain "consensus" of block-happy instances they reference, an instance must merit inclusion on their "tier 0", "worst of the worst" list! This just further accelerates the feedback-loop, as others blindly adopt these centralized block-lists, because, surely, these major block-lists would have definitely vetted and investigated the instances they've included on their lists, right? They're trustworthy! Etc. etc..
   
   #Fediblock is a fucking cancer.
   
   RE: https://soc0.outrnat.nl/notes/9k1bohd10k

   • this ad CAN be blocked, bitch (kirby@lab.nyanide.com)'s status on Wednesday, 27-Sep-2023 02:52:55 JST this ad CAN be blocked, bitch

     in reply to
     @adiz well uhh.. you're federating with me and the rest of my users, my instance has been blocked a lot because of "hate speech"
     
     Guilt by association is the real culprit here, and is why everyone and their mothers gets defederated for no reason
     † top dog :pedomustdie: likes this.
   • :verified_2:防空識別區𝒔𝒐𝒄𝟶 (adiz@soc0.outrnat.nl)'s status on Wednesday, 27-Sep-2023 02:52:57 JST :verified_2:防空識別區𝒔𝒐𝒄𝟶

     in reply to

     • this ad CAN be blocked, bitch

     @kirby@lab.nyanide.com The thing is that I don't interact with "duh nazeeys and hate speach poesters". I, myself, am pretty block-happy with stuff like that, considering the virtual single-user-instance nature of this instance + the fact that I just don't want negativity and hateful trash on my timeline.

   • this ad CAN be blocked, bitch (kirby@lab.nyanide.com)'s status on Wednesday, 27-Sep-2023 02:52:58 JST this ad CAN be blocked, bitch

     in reply to
     @adiz yeah, I mean, welcome to dark fedi? Your instance gets hit eventually if you interact with "duh nazeeys and hate speach poesters"
   • thegreatape (thegreatape@thechimp.zone)'s status on Wednesday, 27-Sep-2023 13:35:24 JST thegreatape

     in reply to

     • Hoss Delgado
     • this ad CAN be blocked, bitch
     @Hoss @kirby @adiz That's gotta be my favorite reason. "Federates/Associates with the usual suspects." Even if you don't technically break any rules, you are communicating with the untouchables, so you must be cast aside.
     † top dog :pedomustdie: likes this.
   • Hoss Delgado (hoss@shitpost.cloud)'s status on Wednesday, 27-Sep-2023 13:35:25 JST Hoss Delgado

     in reply to

     • this ad CAN be blocked, bitch
     I'm a pretty big chud, and he's interacted with me a few times. If you interact with me or my users, it's expected you will end up on the tier-0 list eventually.
   • Silent Sinner in Scarlet (silsinn9801@pawoo.net)'s status on Wednesday, 27-Sep-2023 13:37:56 JST Silent Sinner in Scarlet

     in reply to

     • dotnet
     • this ad CAN be blocked, bitch
     • RyokoPilled

     @RyokoPilled @adiz @dotnet @kirby
     One of the things I hate of this #fediblock is that some instances are added to the blocklist merely because of the actions of a tiny minority of users in such instances, i.e.: few Westerners posting nazism on Mstdn.jp (dominated by Japanese); weebs posting loli on Misskey.io (even though not all users there are lolicons); or pedos posting CP here on Pawoo (fact: pedos comprise a tiny fraction here, plus they often get banned by reports & their CP removed).

   • Silent Sinner in Scarlet (silsinn9801@pawoo.net)'s status on Wednesday, 27-Sep-2023 13:37:56 JST Silent Sinner in Scarlet

     in reply to

     • dotnet
     • this ad CAN be blocked, bitch
     • RyokoPilled

     @RyokoPilled @adiz @dotnet @kirby
     & in the specific case of Pawoo: even after the Pawoo admins increased their crackdown on pedo shit (up to the point of banning various hashtags, mostly thanks to my own reports against such accounts) & this month alone did upgrade their Mastodon software (briefly locking me out because of a 2FA-related glitch on their part), the majority (if not all) of the #Fediblock-preaching instance admins choose instead to double down on keeping Pawoo blocked.

   • Silent Sinner in Scarlet (silsinn9801@pawoo.net)'s status on Wednesday, 27-Sep-2023 13:37:56 JST Silent Sinner in Scarlet

     in reply to

     • pistolero :thispersondoesnotexist:
     • dotnet
     • this ad CAN be blocked, bitch
     • RyokoPilled

     @RyokoPilled @adiz @dotnet @kirby
     In such cases where only a tiny fraction commit digital crimes, rather than blocking whole instances, they should either only block media attachments (refuse to cache them while still letting text go through) or do like @p & block only specific users from such instances so that only that tiny guilty fraction pays the consequences of their own actions without dragging along the innocents into the mud that is #Fediblock drama.

   • RyokoPilled (ryokopilled@shitpost.cloud)'s status on Wednesday, 27-Sep-2023 13:37:57 JST RyokoPilled

     in reply to
     the entire concept of fediblocks was a mistake and this platform won't recover until it's addressed. making it so instance admins can make it so their userbase can't see someone or an instance because of some stupid drama and users have no control over it was such a profoundly stupid idea.
   • pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Wednesday, 27-Sep-2023 13:38:28 JST pistolero :thispersondoesnotexist:

     in reply to

     • dotnet
     • this ad CAN be blocked, bitch
     • RyokoPilled
     • Silent Sinner in Scarlet
     @SilSinn9801 @RyokoPilled @adiz @dotnet @kirby Yes, agreed; usually it's not a large number of people causing a problem.
     
     (FSE did have to implement a special filter for Pawoo; someone was making an account with a CP avatar and then spamming "Like" or "Follow" activities at other servers. This was clever because it didn't create a lot of noise locally, and there was no post to report. In those cases, FSE just rejects the activity if the user doesn't have any posts.)
   • † top dog :pedomustdie: (dcc@annihilation.social)'s status on Wednesday, 27-Sep-2023 15:33:44 JST † top dog :pedomustdie:

     in reply to

     • PC-9801 Enjoyer
     • this ad CAN be blocked, bitch
     @Pawlicker @kirby @adiz
   • PC-9801 Enjoyer (pawlicker@bae.st)'s status on Wednesday, 27-Sep-2023 15:33:45 JST PC-9801 Enjoyer

     in reply to

     • this ad CAN be blocked, bitch
     @adiz @kirby you're now in dark fedi
     yt5s.com-welcome to le club buddy.mp4