UlrikHD

joined 1 year ago
[–] UlrikHD@programming.dev 1 points 1 month ago

This is your second warning to not break our CoC (3.2).

A third warning will result in a temporary ban from programming.dev.

[–] UlrikHD@programming.dev 3 points 1 month ago

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.

[–] UlrikHD@programming.dev 3 points 1 month ago (1 children)

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.

[–] UlrikHD@programming.dev 7 points 1 month ago

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.

 

We have over a period of time gotten repeated reports of unmarked NSFW posts in certain communities. All of these communities share the same singular mod, who have shown indifference when content has been reported. As leaving NSFW posts unmarked is against our instance rules, we have moved to set the rule-breaking communities to hidden.

Those of you who subscribe to hidden communities will continue to see them as normal, for everyone else these communities will look empty and hidden from c/all.

The newly hidden communities are:

We would also like to take this opportunity to remind everyone that programming.dev's policy is to by default hide political communities, pornographic communities and communities hosting bot spam. Users seeking such content can subscribe to hidden communities so see them as normal.

Just recently we also went ahead and hid communities from lemmygrad due to the politics clause.

As always we encourage our local users to report content that break our instance rules. All content you report are seen by the admin team and helps inform the team of what's going on across the fediverse.

[–] UlrikHD@programming.dev 2 points 2 months ago (1 children)
[–] UlrikHD@programming.dev 2 points 2 months ago

!meta@programming.dev is for things related programming.dev, you should repost the question in !git@programming.dev or !programming@programming.dev

[–] UlrikHD@programming.dev 4 points 2 months ago

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.

[–] UlrikHD@programming.dev 10 points 2 months ago

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.

[–] UlrikHD@programming.dev 33 points 2 months ago (1 children)

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.

[–] UlrikHD@programming.dev 5 points 3 months ago

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.

[–] UlrikHD@programming.dev 5 points 3 months ago* (last edited 3 months ago)

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.

 

Sorry if this is the wrong community, not sure where else to post the question, and I'd rather avoid creating an issue over on Github.

Is there a way to check if a federated user is an administrator via the API? .get_person_details() will have the admin field set to false for all other than local admins and .get_community() only reveals the list of moderators.

I know I could scrape the admin list from the main page html, but scraping html is prone to errors if an instance uses an alternative frontend or the frontend is updated. Getting the data via the API should be a more stable solution.

Based on #3703 it seems like a decent chance that this information isn't currently exposed to federated instances though?

 

Describe the problem

3/4 moderators of the community are inactive, leading to a backlog of unresolved reports from the community.

Suggested solution

Find 1-2 active programming.dev users in the community volunteering to moderate c/programmer_humor in the comments of this post.

Expected time cost

A few minutes each week, the volume of the reports from the community is currently low.

Temporary solution

The community will be moderated by the admin community team until new moderators are found.

 

Are there any websites or posts where one can see planned features for the app? It would be nice to know what's missing from the initial release. I see plenty of feature requests, but none contains confirmation of whether that feature will be worked on or not.

view more: next ›