Programming.dev now has official community guidelines. These should help clarify what sort of local communities we allow to be hosted on the instance and the rules we expect them to follow.
As most programmers are aware, anticipating every edge case is generally not viable, so these are just guidelines, not written-in-stone rules. The admin team will still evaluate communities on a case-by-case basis, and exceptions are always possible.
If you have any feedback on the guidelines, we are more than happy to hear them, so please post them below.
😂 Thanks for the chuckle -- though also... I'd read that I think
Thanks for writing this up👍 Very reasonable guidelines.
I created a community for my blog !onlinepersona@programming.dev and wanted to add an admin as a moderator, as per the rules, but there's no interface functionality for that. How do I appoint a new moderator?
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 !meta@programming.dev.
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
Huh, I wasn't aware that the alternate frontends offered more utility. Looks pretty nice actually, thanks for the tip.
Programming.dev offers the tesseract frontend here: https://t.programming.dev/
OK thanks for adding yourself. BTW, I thought I'd be able to stay on as moderator, in order to be able to post, since only mods can post. The idea is that as a blog community, others shouldn't be able to make posts, right? Is there another way to approve users who can post without making them mod?
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.
IMO, it would be better to have it the other way around i.e blog owner being a mod and being the only one allowed to post. It makes the intention of the community clear. Mod abuses could be dealt with using the modlog once somebody notifies mods or admins of abuse. Admins will thus only need to be involved when necessary and the blog owner can update the community as necessary (images, description, sidebar text, ...) instead of having to take up admin time for such stuff.
But if the admins disagree, I can be the test chicken for this current mode of working.
Looks good, thanks for the effort!
@programming.dev
Welcome to the Programming.Dev meta community!
This is a community for discussing things about programming.dev itself. Things like announcements, site help posts, site questions, etc. are all welcome here.
Links
Credits
go to feed...
@programming.dev
Welcome to the Programming.Dev meta community!
This is a community for discussing things about programming.dev itself. Things like announcements, site help posts, site questions, etc. are all welcome here.
Links
Credits
go to feed...
I'll take my rust crate fanfiction elsewhere then.
save