Notices tagged with fediblock, page 4

@nus
For reference, the FediBlock tag is a special hashtag used as a sort of early warning system for content that server administrations or individuals on less moderated servers may want to preemptively block.

In order to use it, you take some screenshots as you did here, perhaps some links, of the most egregious behavior being done or accepted by server staff, and make a post beginning with the hashtag #FediBlock, followed by the URL of the server or account, then give at least a paragraph of explanation after that. Attach links / screenshots, CW accordingly (Begin with "FediBlock"), and post.

Staff of servers will see this and verify your report, then choose how to respond. Do not expect every server to block, as it is really a matter of how much bullshit people are willing to put up with. I also don't recommend doing it with single accounts unless you know they've been reported and their staff has done nothing, because we often investigate whole servers.

Hope that helps.

#FediBlock catposter.club

After a long time of hesitation, I finally come across a post from them that warrants an immediate server block: the admin went on a rant about how he doesn't use "N***** software". I'm going to go ahead and include TechHub and anyone else who wants to block in that category for him.

#Fediblock seal.cafe (Rebased) and subdomains like pl.seal.cafe (Pleroma). Site operator is a bigot.

@lanodan @natalie @ashten @Drand
just btw wanted to point out:
1) I make a throwaway instance and user that just says BEEP BOOP NOW ARCHVIING, follow like 5 instance admins from it, there's a *massive* fediblock campaign and related domains appear on "tier 0" blocklists years after the domain expired
2) I make a tool that makes a single request that's indistinguishable from a web browser, there's a *massive* fediblock campaign and the FBI appears at my house

and finally....

3) this guy literally bogs down and causes performance issues for server admins, absolutely *nothing* on #fediblock.

Anywhere I make an account, the admins are harassed for "harbouuuuuuuring" me. Something tells me techhub has gotten zero (0) complaints about this dude.

Really makes ya think.

#fediblock my nuts itch
btw never use oliphant and other bullshit blocklists

I'm sure, just like I used to do, people followed back without looking at the profile.

The reason I'm shocked it was here is the name of the server and the handle. I reported it immediately and the server was immediately blocked from the instance I'm on (Thank you!).
Edit: THEY HAVE NOT BEEN BLOCKED BY THE FEDIVERSE

#Fediblock PLEASE.

What I've learned:

1. Always check profiles before following back
2. MAP is code for "Minor Attracted Person"

(2/2)

@Mastodon@mastodon.social seriously? You are the very last people I'd expect to censor #Palestinian #media. Are you really that desperate to become like #Twitter or mainstream social media? I really hope that this is a sincere mistake, and that whoever pressed that #suspend button is reprimanded. This gives a very wrong signal to #Palestinians and independent #journalists / #press people who are seeking a friendly platform for their voices in the #fediverse.

If you dear reader are reading this post, please boost both Mondoweiss's original post (which will be displayed as a RE: link if you're in #Mastodon) to show your support for @mondoweiss@social.mondoweiss.net as well as this quote #boost so that it may reach mastodon.social (because for all we know they could decide to just #fediblock their self-hosted instance altogether, thankfully that didn't happen yet and it's an account suspension for now)

@palestine@a.gup.pe @israel@a.gup.pe #Palestine #Israel #Gaza #GazaStrip #WestBank #Journalism #Journalist #PressFreedom #Mondoweiss

RE: https://social.mondoweiss.net/users/mondoweiss/statuses/111295806945919826

#fediblock ubiqueros.com, admin engaged in deliberate misgendering

@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 @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).

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