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.
!meta@programming.dev is for things related programming.dev, you should repost the question in !git@programming.dev or !programming@programming.dev
If it's your own blog you're free to share it in whatever manner you like. If it's not your own blog you should respect the wishes of the author, meaning ask for permission if you want to copy paste the entire blog. Otherwise, excerpts alongside credits to the author is fine.
Remember that our CoC applies even on communities outside our instance. Try to avoid personal attacks and telling people to harm themselves per CoC 3.2 and 3.7. Continued failure to do so will lead to a temporary or permanent ban.
Just a reminder that our instance CoC applies even on communities outside our instance. Please try to avoid calling people slurs per CoC 3.2 and 3.5. Failure to do so may lead to a temporary or permanent ban.
Looking at your instance handle, I hope/assume that your comment is supposed to be in lighthearted jest. However that would only be an assumption on my part and in general it's not ok to say someone's job/work tool is for [remarks directed at sex, gender, ethnicity, orientation, disabilities, etc...] per CoC 3.5.
Please take into consideration that members on this instance may be of different backgrounds than what you're used to and interpets what you say differently. Further breaches of our Code of Conduct may lead to temporary or permament ban.
I think a 30 day limit is far too restrictive. Imagine making an account to ask for help and then being told you have to wait 30 days. You'll just turn to reddit like the 99% did from the start. The fact I couldn't help/answer people's question on SO after signing up permanently turned me away from that network, just as as an example.
Most spam reports that reaches this instance is from other instances, so even with the wrong assumption that us putting up a restriction would block spammers, it would hardly put a dent in the amount of spam.
I think the real solution will be better moderator tools so that mods can effectively control their community as needed. An auto-mod can already do exactly what you're asking for on a community level, which wouldn't be as oppressive.
That should actually work great, in the absence of being part of the API, thanks! Funnily enough the copilot autocomplete suggested that when I was formatting the url param.
This is your second warning to not break our CoC (3.2).
A third warning will result in a temporary ban from programming.dev.