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.

  • Rimu@piefed.socialM
    2·
    7 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@lemmy.dbzer0.com
      4·
      7 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?

      • Rimu@piefed.socialM
        3·
        7 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.

      • Rimu@piefed.socialM
        2·
        7 months ago

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