I noticed responding to posts in communities hosted at lemmy.ml gives the following warning:

This post is hosted on lemmy.ml which will ban you for saying anything negative about China, Russia or Putin. Tread carefully.

While I see where this is coming from and I agree with the general sentiment, I’m not sure it’s a great idea to include such a message. I basically read it as an invitation to be off-topic and to derail conversations in order to annoy the admins. While it comes from a point of good intentions, it can be disheartening for the people running communities on Lemmy.ml to receive comments about Russia from users basically trying to get banned, in communities that has nothing to do with this issue.

It’s unfortunate, but a lot of valuable older communities are still hosted on lemmy.ml, and I think PieFed users should be encouraged to be constructive and on-topic users there as they should be everywhere else.

An alternative suggestion: Maybe it could be useful to remind people which community they are posting in? Like, “This community is dedicated to renewable energy. Please keep this in mind when contributing to the discussion”. Then again, that would be a mess to implement in a good way.

  • db0
    link
    fedilink
    23 months ago

    Is this a piefed feature? To add warnings about other instances?

    • cabbageOP
      link
      fedilink
      52 months ago

      It’s an experimental feature. If you post on Beehaw it shows a reminder that Beehaw has a stricter code of conduct than most instances, and remind you to be nice.

      PieFed is also developed specifically to be unappealing to tankies and fascists, which I think is generally wise, but of course certain measures might be more successful than others. :)

      • Praise Idleness
        link
        English
        114 days ago

        PieFed is also developed specifically to be unappealing to tankies and fascists,

        I like you

    • RimuM
      link
      fedilink
      4
      edit-2
      2 months ago

      Yeah.

      Often people will not be aware of the rules a community has (they don’t read the sidebar or are on mobile where there sidebar is hard to find) OR, as in the case of [email protected], the rules are written deceptively and there are many unwritten rules. Having an additional message that is front and center above the ‘compose a comment’ input field is an attempt to deal with that.

      We need alternatives to defederation which is too extreme and total. Mastodon has muting and silencing, for example. I’d like to figure out whatever the threadiverse equivalent of that is - some way to allow access to those who want it while steering naive users away from places where they’re going to have a bad time.

      • db0
        link
        fedilink
        52 months ago

        I agree as well. Fediseer supports censures and hesitations towards instances. You could ingest those and allow piefed to report how they see others and how other see them

        • RimuM
          link
          fedilink
          32 months ago

          Great idea.

          I’ve been trying to get into fediseer but piefed does not provide the necessary API to let me claim my instance. I think that’s what it is - I get an error message "There was an api error: Only admins of that piefed are allowed to claim it. ". Do you have any docs I can look at which might help me know what endpoints I need to make?

          • db0
            link
            fedilink
            42 months ago

            Fediseer tries to understand the api of each software and then looks for the admins of the site to pm. Do you have an api endpoint which lists the admin usernames?

            • RimuM
              link
              fedilink
              4
              edit-2
              2 months ago

              Yes, I have tried to copy Lemmy’s /api/v3/site endpoint because I saw a lot of requests to it in the server logs.

              https://piefed.social/api/v3/site

              Actually I can see a few differences that need tidying up… ‘name’ is not correct and ‘displayName’ is missing, for example.

            • RimuM
              link
              fedilink
              32 months ago

              I’ve fixed up the name and display_name parts of the JSON, incase that endpoint is the one you’re after.

      • cabbageOP
        link
        fedilink
        22 months ago

        An idea that has been spinning in my head a bit is to allow people to subscribe to different levels of moderation. Basically allowing users to choose a “curated”, “moderate”, or “liberal” experience.

        Curated: Whitelist of servers rather than blacklist. Well-moderated instances only.

        Moderate: Blacklist rather than whitelist, but blocking annoying instances like Lemmygrad and Hexbear. Aiming at a wide yet enjoyable experience.

        Liberal: Blacklist, but only blocking instances that allow (or are incapable of handling) content that goes against the content policy.

        It’s probably more difficult to implement than what it’s worth. What I like about it however is that it would make the whole process of content curation much more transparent. Right now it’s often not so clear to people signing up to an instance what kind of moderation policy they will be signing up for. At least this would allow the user some agency even after sign-up.