Comment on Piefed admin settings that allow to enable or disable content filters (they are disabled by default, see body for details)

• anarchiddy@lemmy.dbzer0.com ⁨1⁩ ⁨month⁩ ago

  That’s admin and community dependent - an admin or community can take that reputation metric and use it to automate moderation. There is/was an entire community whose whole gimmick was auto-banning users from every instance for activity across the entire federated network. But beyond that, piefed already drops content instance-wide for as little as a single user blocking another.

  if parent_comment.author.has_blocked_user(user.id) or parent_comment.author.has_blocked_instance(user.instance_id): log_incoming_ap(id, APLOG_CREATE, APLOG_FAILURE, saved_json, ‘Parent comment author blocked replier’) return None

  The codebase is riddled with shit like this.

  source

  • Skavau@piefed.social ⁨1⁩ ⁨month⁩ ago

    There’s no inbuilt system to automation moderating out low reputation accounts to my knowledge. Any instance that would do this would have to be using a third-party tool.

    The Piefed system of blocking is more aligned with how most other sites do blocking. Lemmy doesn’t prevent blocked users from replying, but Piefed does. So from Piefed, if it’s working properly, you shouldn’t be able to reply to users who have blocked you. Lemmy doesn’t operate like that, so it just throws out replies. It’s due to different blocking philosophies.

    source

    • anarchiddy@lemmy.dbzer0.com ⁨1⁩ ⁨month⁩ ago

      The Piefed system of blocking is more aligned with how most other sites do blocking

      I don’t know any other site that allows blocked users to reply to the blocking user but deletes the reply on the backend server for everyone on it.

      But regardless - that decision was made unilaterally by piefed and corrupts the federation of the rest of the network. Huge holes of mis-matched comment threads are being created everywhere because piefed chose to implement a destructive blocking system rather than a front-end filter, or by working with the other implementations on a solution that doesn’t misalign data across the network.

      I understand that you agree with how piefed restricts certain content - my point is that the way piefed has implemented those features corrupts the integrity of the entire network. They’ve made it clear that they have no interest in collaborating with the other developers, even if it means creating incompatibilities between the integrations to the point of functional defederation.

      “Move fast and break stuff” isn’t something anyone should be aspiring to.

      source

      • Skavau@piefed.social ⁨1⁩ ⁨month⁩ ago

        It doesn’t. On Piefed if you are blocked, you should be unable to reply. It is whited out. But Lemmy obviously doesn’t work like that so incoming replies from users who are blocked, coming from Lemmy, just have it automatically thrown out.

        Did Lemmy take a democratic vote about how they wanted blocking to be handled? Some users prefer someone they block being unable to reply to them. I have even seem this expressed on Hexbear.

        source

        • -> View More Comments