Fediverse

That seems like something that is very reasonably within the discretion of an instance admin to do. Also pretty neat feature. Not a de-federation so you can still interact with users from that instance, but it doesn't push your own users into communities on problem instances.

I find it hilarious that this was originally posted on Lemmy.ml, an instance where mods ban you for saying anything bad about China.

Second, a feature of piefed is curating a more positive feed so you don’t have to see all the political hatred.

This is a feature not a bug.

As someone who doesn’t follow stuff like this why should I care? It all seems like drama for the sake of people getting to cosplay as people with authority.

It is funny how all the biggest crybullies on Fedi have all gathered around to demonstrate exactly the behaviour they're being silenced for.

"Why would rimu silence me, all I do is things like lie about him being an anti-left transphobe!?"

The amount of disinformation here should not be nearly as shocking to people as it seems to be. e.g. the non-conditional title statement of this post, even if its text walks the situation back a bit, is now being called "de-escalation"? Or the GIANT letters calling for the immediate defederation of Lemmy's most popular instance in this comment? These are the very epitome of escalation.

And as for AI moderation, see this comment, where the AI output went entirely unreviewed by any kind of intelligence, and iirc the moderation reason stated was also written entirely by AI? Every single time I have chased down the accusations to find the real story, I become more and more disappointed in certain Lemmy instances that are now expanding the influence of hexbear, Lemmygrad, and lemmy.ml.

If they want to cut themselves off from the rest of the Threadiverse by defederating not only Lemmy.world but also every single PieFed instance, regardless of the stance of the admin team (in one of the multiple calls for defederation, click on the username of the commentor and read the statement), then at this point I am no longer against that outcome. It will create an echo chamber for them, but they do not seem to be listening anyway, and increasingly I find myself not listening to their incel-based arguments anymore either (where they must be free to do whatever they please but everyone else owes them something, somehow).

Edit: even the title of this very post screams disinformation - like how is this "Shadowbanning Instances from Discoverability", when instead it is plainly simply a banning? If it were a shadow-ban, then it would still appear to the end-user to not be a ban, but then to everyone else it would be handled differently. Instead, it is an even ban, always looking the same way to everyone. Calling it a "shadowban" is a fallacy that appeals to emotion, rather than explaining the situation logically. i.e. it is clickbait, presenting a false front in order to entice people to read it, but when the details become understood the term is seen to be the polar opposite of what it attempted to portray. This is not what I hoped to get out of the Threadiverse, personally. I came here to get away from the right-wing Reddit, not find another Reddit 2.0, moar tankie drama version.

Its pretty obvious to anyone that these instances are problem instances. I dont know why people are muddying the water arguing over the minor details and its insane to try paint it as if the reason is their left leaning protrans views. They are problem instances and quieting their notifications is fine if thats the action the admin wants to take. The other option is defederate.

Most of this stuff is functionally over my head, but an instance leaving out others from it's 'picker' for whatever reasons seems like a Fediverse working in healthy fashion. That is, with individual instances getting to choose their own policy, exactly as you'd expect, and want.

If this stuff is really the worst that you can complain about in terms of PF.S, then I think you've had a pretty good day. By contrast, other stuff I could mention on the Lemmy.ml side (etc) are far more concerning to me.

join-lemmy.org and piefed.social is not the same thing. One is a page about software and the other is an instance. Why shouldn't rimu be able to run piefed.social they way they see fit?

I am not seeing any political influence at join.piefed.social. join.piefed.social even links to the instance chooser of https://nord.pub/auth/instance_chooser

And don't tell me lemmy.ml on lemmy.ml is neutral lol

I'm not gonna get into this one, but as a rule, if you're on one of the default instances for a given fediverse service, such as mastodon.social, you should be using it to actively shop for a smaller instance more closely aligned with your interests.

The "obvious reasons" come from the drama I tried to summarize in this comment: https://lemmy.ml/post/47022286/25575766

If we go down to the core of the issue, there's a fundamental disagreement between some instances on a niche use case: can the modlog be used for permanent slander, without giving people the option to reply?

Dbzer0, quokk.au and anarchist.nexus instance admins didn't see the value in allowing admins to act on other instances modlogs. Rimu and other people in the Piefed staff were interested in this, hence the new feature regarding the modlog.

There was some additional tension between Quokk.au admins and Rimu on the way he handled the AI moderation disclosure, leading to a quokk.au admin leaving the channel.

Now remember that all of this only affects Piefed.social. I've been a Piefed.zip user for 11 months now, and that's the instance I recommend to everyone. Even from a federation perspective, Piefed.zip doesn't defederate from for instance hexbear or lemmygrad (but the Piefed instance blocking is an actual blocking compared to Lemmy's incomplete one).

Switching between Piefed instances is as easy as it can be.

Some people will see these decisions for Piefed.social and the new Piefed feature as "drama", but they seem to be a way to deal with what triggered the drama in the first place (slander in modlogs)