Crashdoom (he/him)

Network Administrator for Pawb.Social, furry, and a programmer

Mastodon: @crashdoom@furry.engineer

  • 64 Posts
  • 80 Comments
Joined 3 years ago
Cake day: June 2nd, 2023
  • Crashdoom (he/him)@pawb.socialMtoPawb.Social General Lounge@pawb.social•I am calling for pawb.social to join in solidarity with other instances against lemmy.world's zionist admin teamEnglish
    10·
    6 months ago

    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.

  • Crashdoom (he/him)@pawb.socialMtoPawb.Social Announcements@pawb.social•Update Regarding Pawb.Social Media LossEnglish
    10·
    1 year ago

    We haven’t yet got the images reimported so existing images and profile pictures will still be broken. The base URL without the format link would have been cached most likely, but the format link would error as pict-rs isn’t aware of the file you’re trying to reference.

    For now, reuploading things like profile pictures is my recommendation rather than waiting for us to get the images reimported.

    We did discuss briefly with Asonix but they weren’t sure it’d be possible, so we’re exploring options using an external database for pict-rs but that seems relatively new.

    tl;dr we have the files, but are still working on getting them reimported!

Moderates