Please have a second read of our Code of Conduct which you agreed to follow when signing up to our instance. Being purposefully hostile is not in line with that agreement.

Please follow our instance’s Code of Conduct and avoid using slurs, repeated breaches will lead to a temporary ban from our instance.

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

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™.

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.

@JackbyDev@programming.dev @fuzzzerd@programming.dev As you requested

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 + !news@lemmy.world 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.