01:03
And to date, in the long chain of comments, I'm feeling somewhat unheard, which has the unintended effect that the mod team is banding together to protect one of their own (who needs no protection from me!), rather than giving my concerns an honest audience.
I'll try to change my style so I sound less, I don't know, urgent or shrill or vindictive or however I'm coming across.
In turn, I'd like to ask the mod team, tchrist of course included, to discuss the specific observations I've made which have caused me concern.
Logistically, Chat isn't the easiest thing for me, so I imagine this conversation will be asynchronous rather than real time. I'll pop in and out, and I expect others will as well.
All that said, in case anyone is worried, I am not here to have tchrist pilloried or anything (as JAPH, I still have a bit of star-struckness around him, which has only increased with my appreciation of his expertise in English).
The happiest outcome for me would be if Tom decided to recuse himself (both directly and by proxy of direct requests to other mods) from questions which touched on pejorative language. But I am principally concerned with open discussion of the situation which concerns me, and if there is some other happy resolution, that will be fine by me too.
13 hours later…
14:28
If a mod was reopening or undeleting their own questions or answers that others in the community had voted to close/delete, or consistently flagged/closed/deleted particular individuals, that would be a sign of bad mod activity.
But the situation you're describing is a well-understood phenomenon that we all have agreed needs addressing (questions/answers about sex/pejoratives are often poor but get lots of traffic).
And one mod takes interest in using the (very) fair functionality implemented to reduce the problems with such things.
3 hours later…
17:32
What I have in mind for this chatroom is to expose barriers to consistent and systematic enforcement. There is already a comment thread about the other issue, I have also recommended that it be escalated to the community managers, and anyone could also open a meta question on it. My request is that this room not become another forum to discuss the same issue.
@DanBron I also appreciate your wanting to reset the tone of that discussion. One of the things about SE that I most value is the emphasis it puts on being respectful and patient, and assuming good intentions.
@SvenYargs I got to see your deleted comment, and I hope you'll repost it. It's exactly the kind of thing I want to review here: any element of the site which is a barrier to consistent and systematic enforcement, whether that barrier is in the site design, or in our community standards, close reasons, or any other kind of rule or guideline.
17:53
However, in determining whether something is a barrier, one must also determine what it is a barrier to. I commented yesterday...
Pre-emptive protection is not censorship. It is protecting the site from low-quality drive-by answers. If someone is prevented from answering by the threshold, then they have only to use their talents to get 10 points on a different question, and then come back and answer. It doesn't prevent them from answering; it merely places an "established members only" cordon around the question. — Andrew Leach ♦ yesterday
18:09
@AndrewLeach So we have this community guideline, saying we can pre-emptively protect questions. It has the express purpose of letting experienced users prevent a flood of drive-by answer posts which are non-answers: guesses, copypasta, and so on. It's a barrier to entry. But suppose it also has the tacit purpose, or just a de-facto effect, of letting experienced users target pet peeves? Then you could say it a barrier to fair enforcement.
4 hours later…
« first day next day → last day (44 days later) »
Transcript for
Jan23
Jan '1824
Jan25
Barriers to consistent and systematic…
Continuation of discussion from comment thread here: english.m...