• 13 Posts
  • 216 Comments
Joined 2 years ago
cake
Cake day: July 7th, 2023

help-circle




  • The intention of requiring a 3rd party to act as a moderator is to avoid mod abuse from the blog author such as deleting comments or banning people for unreasonable reasons. E.g. someone correcting an error in a blog post and then having their comment deleted and banned by the author in retaliation.

    Ideally Lemmy would have more granular level of mod authorisation so that we could just remove access to deleting and banning people.

    If someone makes a non-relevant post in the community, it would be removed. If it becomes a recurring problem, we can look into automating that process.



  • The mod tools are unfortunately pretty poor on Lemmy. For adding/removing moderators via the GUI the person must first post/comment in that specific community. You can then via the context menu of that post/comment add someone as a mod.

    The alternative is to interact with the Lemmy API directly via a script.

    I’ve added myself as a moderator, although the whole admin team may operate as moderators, similar to [email protected].

    If you got additional changes you want to make to the community, e.g. add additional rules like make it explicit that only you can post, or add a banner to the community you should do it now before you’re removed as a moderator. Otherwise you can always DM me/the admin team if you want to make changes to it.

    Edit: As Blaze pointed out, you can use alternate frontends like https://t.programming.dev/ to gain additional GUI mod tools








  • Does this instance have a concrete guideline or precedent for that or would be able to decide at the discretion of an admin?

    Communities with no connection to programming culture are removed as a general rule. Other than that, it’s decided on a case by case basis. It’s not that uncommon for us to remove new communities that are created. We’ve removed the community + one another






  • You could theoretically just loop through every community via “get_communities” and then com_obj["community_view"]["community"]["hidden"] :: boolean *I’m writing this on memory, the json structure may be slightly different

    and then just subscribe to every community that pops up.

    It will likely be slow though, and it’s mostly NSFW + [email protected] that would pop up on c/all if you did. I also *think* lemmygrad as an instance is hidden, so those communities may pop up if they tend to reach c/all.

    I’ll discuss with the team about making a public list of hidden communities.