

For the last ~2 weeks the infrastructure team have been actively investigating performance with our server and actions are currently being taken. You should expect us to post an announcement with more detailed information soon™.


For the last ~2 weeks the infrastructure team have been actively investigating performance with our server and actions are currently being taken. You should expect us to post an announcement with more detailed information soon™.


Appreciate you had the awareness to delete the comment before we got around to the report. It was still a breach of the instance’s Code of Conduct (1.1, 3.2) and repeated breaches may result in a temporary ban.


If you don’t have anything positive or helpful to say, it would be better to just not reply. If you think the post shouldn’t be posted here, use the report function instead.


Please don’t stalk/harass our users, it can and will lead to a site wide ban if reported.


It is a precautionary policy to avoid what is currently just a theoretical. You’ll be the first to create personal blog community so it will be interesting to see how it works out.
Nothing is set in stone of course and policies may be revised, I won’t make any claim that the current set of guidelines are perfect and immutable.


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.


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/


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


Hi, we have now published official community guidelines as announced in this post.
Please let us now in the linked post if there is still something unanswered.


Yeah, we ban the spam accounts on the first report we receive.


If you can’t see posts you make on hidden communities that you are subscribed to on your profile, that sounds like a possible bug, and I’d encourage you to report the issue to the Lemmy repo


I don’t believe the system is that granular. If you’re posting in a community that is now hidden I would recommend you to subscribe to it if you want to continue to see it.


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


I’ve replied to dessalines


It’s perhaps poorly phrased, no it will only affect that specific user.


Discussions are getting off-topic and this is an announcement post, not a discussion post, so I’m locking the post.
If local users want to have an in-depth discussion regarding admin moderation of programming.dev, you’re encouraged to make a discussion thread in !meta@programming.dev.


I can only report on what I’ve been told by those who have directly dealt with the reports, my apologies if parts of the phrasing are inaccurate/poorly made. I’ll make a note that we should probably reach out to relevant moderators beforehand next time we make similar actions.
As for differing sensibilities, I’m not sure most people would classify this kind of content as safe to browse at work/in public.
Regardless, we are not here to make demands or argue on how other instances moderate their own content. This post is made mainly to keep our actions transparent to our local users.


Hiding communities outside our predefined rules (politics, porn and bot spam) isn’t something we take lightly, and we are only hiding them now after several months of reoccurring reports that break our instance rules (3.4).
We will do our best to be transparent about when and why we hide a new communities, and be aware that subscribing to a hidden community will unhide it for your feed.
If you do have concerns and suggestions on how to alleviate those, please know that we are happy receive feedback.
Hi
Can you update the title to be the same as the updated title in the news article?
The (successful) end of the kernel Rust experiment