Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Correct avenue to discuss a specific moderator
If you notice that a specific moderator appears to be taking a lot of inappropriate actions, what are you supposed to do about it?
Is there a way to "flag" moderator actions, so that if a moderator has too many flags the admins can review his conduct?
Simply making a post on Meta like "matthewsnyder is a bad mod remove him" seems like it would not go too well.
Relatedly, how to gather evidence of a moderator's conduct? Are we supposed to take screenshots, or is there some way to link to moderation actions?
1 answer
The easiest way to do this would be to contact the Codidact Team directly. You can do this via several different ways, including emailing us at support@codidact.org, which will create a support ticket in our system. I can confirm that all support tickets are checked.
I would recommend against any public or semi-public calling out, such as on Meta or Discord; that's likely to stir up drama and possibly start witch hunts, so a discreet report is better.
Alleged moderator misconduct is a pretty serious deal, so any admin who sees the ticket is also likely to send the "batsignal" in the relevant Discord channels, so you'll get all the relevant people looking into it sooner rather than later.
As for documentation, we do have logs of pretty much every action taken on the site, and in theory we have raw database access for the rare occasions where that would be necessary, although that access is limited to a very small number of people. Screenshots could be an added bonus, but the most helpful would be to link to the post or otherwise where the incident you're concerned about took place.
If this question was prompted by an actual concern and isn't just theoretical, please reach out to us sooner rather than later.
0 comment threads
0 comment threads