Yep! I was talking about it over on this thread: https://pawb.social/post/52012537/25027493 xD
verify you're a human
...lmao, oops
Feel free to reach out to network[at]pawb.social if you think there's issues we haven't resolved. Lemmy reports can also get resolved by community mods in which case the admin team won't see it. Masto is far better in that dept.
How can we fix LW and large instances being a problem we have to even care about?
Move. Leave those instances. Make communities elsewhere. Be the change you want to see.
There are no rules to who or what communities can be made here, other than I won’t platform hate, harassment, or abuse of any kind.
I’ve posted a response as a top-level distinguished comment: https://pawb.social/comment/22002225.
After discussing with the team internally (admins & mods), we’ve come to a few points:
tl;dr We call on Lemmy.World to be fully transparent and explain their actions to the whole community, and we’re setting more concrete policies for our own moderation actions going forward.
——
While we won’t be formally joining the boycott of Lemmy.World, for reasons I’ll go into in due course, we do call on them to be transparent with the community and act in good faith in regards to whom of their staff came to the decision, why they felt a non-directed comment is worthy of banishing an entire instance, and what they’ll be doing going forward to course correct.
Defederation should not be a bludgeon to be waved around. Individual users commentary (admin or not) should never be the sole, snap reason that an instance is defederated due to the potential for irreversible damage to federation (loss of posts, comments, users, etc.) and the subsequent impact on users.
There’s a way to handle problematic users who say things you don’t like, but they’re allowed to say: Block, and move on. Rash defederation instead demonstrates behavior akin to schoolyard bickering, not that of an admin, a custodian, operating a service for the good of their users.
If allegations are true, LW has some cleaning up to do with their moderation policies, especially not using abusive tactics to hide or manipulate the Mod Log.
On moderation policies, we have an internal document that explains our federation policies with other instances. We’ll be making this public in due course, but here’s a snippet from it that we’ve been using since Day 1:
We are an open-first instance, however in rare cases where an instance has been identified as being, indifferent to, permissive of, or actively encouraging abusive conduct, that instance will be blocked from federation.
At this time, while we have distain for how LW handled things and for their actions (if the allegations are true), we will not use defederation as a weapon as we believe it irresponsible and an avenue for subjective defederation actions in the future.
Also, if the subtext is not clear: It is childish behavior to wield your admin powers as a bludgeon, and to use your admin tools for a personal grudge instead of blocking an offending user. “Go kill yourself” or anything akin is not a reason to defederate an instance, that’s overkill and I’m fucking disappointed, but when anyone can become a “fediverse admin” that’s the shit situation we’re in.
Confirming we've seen this and are discussing internally with the whole team.
👋 Apologies-- I think I just re-discovered the Scunthorpe Problem in real-time. You should be good to attempt to create an account again without issue! :3
Maintenance has concluded!
Whoops-- Turns out, no it wasn't. I didn't realize public channels weren't searchable by default over federation XD
The #pawb:pawb.social space and its channels should be public to everyone + federated; If you're still getting issues, let me know!
Yes! We've got one up at https://matrix.pawb.social/ via web, or pawb.social via apps. You should be able to sign in using your Lemmy (pawb.social), furry.engineer, or pawb.fun account :3
