@jippie The term Public Service Announcement comes from radio broadcast industry. It's a message broadcasted free-of-charge to raise awareness of some issue.
@Vi. No what happens is it takes a lot of time reading the question, then trying to make sense out of a potentially nonsense answer (you don't know beforehand) and consider whether it deserves closing or not and for what reason.
Then I see how much of my time I've lost trying to understand stuff that just isn't meant for understanding and I conclude I can use my time better. Especially since it is an awful amount of posts every day.
@jippie You are right about the review queues. We have only 5 to 7 people reviewing (that includes Nick with the +5 hammer). WhyTF has everyone neglected community modding?
Since our review queue is so long, newly flagged questions take a long time to close. They remain unclosed long enough for rep whores to get to them.
To compensate for all this I have to be fairly aggressive with hammering questions (wherever I find them: in the review queue or elsewhere), and make lots of judgement calls. That increases the amount of flak that I get. Funny thing is, flak comes from members who have enough reputation to do community modding, but don't bother to do it. ( @EMFields , I'm looking at you.)
@NickAlexeev I don't know if you ever visit the Arduino SE, but Nick Gammon seems to be the loneliest moderator. However, he is doing a great job there. (Don't know when he finds time to work)
@Marla Modding is more about common sense than hard skills like software. Look at this freshly minted Arduino.SE pro tem mod. When he got the modship he had 150 rep there (and not much more on other stacks). Modships are pretty much laying on the ground on Arduino.SE .
@NickAlexeev, If modding is less about hard skills, why there's no inter-site elected mods? Or modding situation is pitiable globally (on most SE sites) and it's not reasonable to redistribute workforce to this site?
@Vi. There is no negative feedback. Lower quality will not result in fewer visitors. Lower quality will result in losing core members (probably for good).
What if some questions come "pre-closed" (invisible from first page and search unless approved by some queue)? Can it serve as milder barrier of entry compared to just blocking asking until queue cleared?
@Marla, It should not appear as "blocked" or "closed" or "suspended". It may be termed like "waiting for review" or "waiting for pre-moderation". The feature may be active only if there are queue problems and the site can work normally when queues are OK.
@Vi. I did experience something like that on a "comment" section of a financial web site I frequent. Must admit I did stick around there until my comments were accepted without delay.
@Marla You would come back eventually. It's like yeast excretions. They don't taste all that nice the first time one tries it. But eventually one drinks it by a liter. It's called beer.
Also maybe questions from users that have big problems with English (even if they have some background topic knowledge) may appear nonsensial at first and second glance, and only on third reading one understands that the question (after massive editing) has it's place. "Agressive" moderation may spill it away with the rest of water.
@Vi. ... or reduce the number of close-votes required to close a question. Under-moderation can be detected by the average time that a question stays in the review queue.
I'm sure you remember this experiment, which changed the required number of close/reopen votes from 5 to 3. Before getting to the meat of the analysis, I should point out that the change worked almost exactly as intended. Close votes clustered around 3 and the median time to close dropped noticab...
For editing queue there is nice workaround (I call it "strong approve" or "strong reject"): go to the question and manually edit it again (if not approved) or revert (if not rejected).
There is probably no such workaround for close queue...
@Vi. Some other things that can be done: special powers for certain classes of questions given certain conditions. For example: duplicate can be insta-closed by a member who has a gold tag-badge for one of the dupe's tags (this is already in place at least on SO).
(Previously I though that "Programmers" is just a trash can of "Stack Overflow" to detour semi-offtopic subjective content there and closing questions on "Programmers" is not appropriate)
Update: this is now enabled everywhere!
The rules are:
You can instantly close as a duplicate any question that was originally asked with a tag you have a gold badge for.
You can instantly reopen any question closed as a duplicate that was originally asked with a tag you have a gold badge for....
@NickAlexeev, Swift close-as-duplicate should be accompanied by reopen-as-not-really-duplicate (AFAIR something like that is indeed implemented: I saw some special button).
@NickAlexeev [fun] Then rename it to QueueOverflow? [/fun]
Are there any scientifically modeled findings of what number of votes should be to do X, how much rep should be to do Y and so on and in general how community-supporting system should behave (given some mathematical model of a community)?
@NickAlexeev I don't understand what you're saying, since if a question is closed down before anyone even gets a chance to answer it because a moderator misinterprets it and closes it immediately, that makes it doubly or triply hard to bring back to life since all that's available is comments and editing which is still at the mercy of the moderator.
@Mast Glanved over the post, but don't understand why is it called "failed" there. What constitutes a failure? People whining and wanting to go back? Some numbers? Just a management decision to roll back?
@NickAlexeev I thought I was... I edit others' posts, vote to open and close posts, ask for moderators' actions to be reversed on occason, comment on spelling and grammar, etc. What more is there?
@EMFields I'm looking at the logs for the close and reopen review queues for the last 30 days (that's as far back as it goes). Your name isn't there to be found.