3

Are there specific guidelines for when it is appropriate to flag a question vs. voting to close?

Increasingly, voting to close a clearly off-topic or otherwise unworthy question and posting it in the "Vote to Close" chat room yields insufficient votes to finish it off, unless a moderator happens to be watching the VTC chat.

I find myself extremely hesitant to flag such questions unless there are special circumstances (e.g. belongs on a site with no migration path), because I presume that the very existence of the "vote to close" chat room is to discourage flagging of questions that can be voted closed.

This leads to cycles of voting to close a question, posting it to VTC, waiting at least 8 hours, and then flagging it with a note that I tried the other route first. This strikes me as a highly inefficient way to engage in crowdsourced moderation.

  • Is the vote-to-close chat room working better (or equally poorly) for others?
  • Is there a better way for me to approach questions that deserve to be closed?
| |
5

For what it's worth, people seem to flag old questions, and VTC newish questions.

Not saying that's right, but that's what seems to happen.

| |
  • Makes sense. VTC seems to work well when a question is new enough to get a lot of attention, and poorly otherwise. – Skyhawk Jan 23 '12 at 9:05
  • 1
    @Miles, of course if someone goes on an unrestrained editing spree new questions get pushed down to the point where they don't get the needed attention. – John Gardeniers Jan 23 '12 at 11:24
  • @JohnGardeniers Touché. – Skyhawk Jan 23 '12 at 12:14
2

I think it's ok to cast your own vote and then flag for a moderator.

I don't know why the VtC room was created, I assumed it was because it's considered better to have 5 normal users cast votes than for one moderator to hammer it. But if it's something that you (or anyone else) think is clearly in need of closing, then there's no reason not to ask a mod to close it right away. Worst case, whatever mod sees the flag disagrees and ignores it.

| |
  • 2
    I created VTC for the purpose of increasing the visibility of questions that need attention. Today there are still only 217 people with the relevant privilege of them 50 used it in the last week and <20 used it regularly. – user9517 Jan 23 '12 at 11:02
2

As a mod, I try and let the community close questions where possible, particularly if they are border line, using the Mod Hammer is really something I want to reserve for questions that are blatantly off topic and need to go, spam etc. That said, if there's a question sat with 4 close votes I often will cast the last one.

So, in my opinion, if the question is so bad it needs to go immediately, or as Mark said, it's an old question, then flag away, but If there is a possibility the community will get to it then I would leave it for them. Obviously if you don't have close rights, and don't feel it will get the communitys attention enough to close it, then it may be worth a flag.

| |
1

I think it depends on the age of a question. If you see a bad one which is old and you think Serverfault would definitely be a better place having that question closed, flag it. If we agree we, will happily close it.

If it is a new question on the first pages I would rather wait for the community's decision. I guess many 10k users watch the close-vote list in the tools section of the site. So, there's a pretty good chance that the question will be closed if there are enough people who agree with you.

| |

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .
https://meta.serverfault.com/questions/2723/vote-to-close-vs-flagging
meta.serverfault.com
crawl=CC-MAIN-2020-29
139638
application/http; msgtype=response
sha1:ANQDJQ6VBWRHN5Z3BWGGGCROQSQKYCUY
<urn:uuid:8e4c3d65-4bab-4adc-b2eb-2384a7e8158b>
2020-07-06T13:29:24Z
151.101.193.69
text/html
sha1:JQBCT6KQJZRXFXZRTHJMJ3DS7AWRFTLF
<urn:uuid:50a072f1-270f-49c1-98a1-62317625c4f3>
https://meta.serverfault.com/questions/2723/vote-to-close-vs-flagging
response
<urn:uuid:14b7757a-3cb7-4971-99b4-7732a3ee3fb3>
isPartOf: CC-MAIN-2020-29
publisher: Common Crawl
description: Wide crawl of the web for July 2020
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-83.ec2.internal
software: Apache Nutch 1.17 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.2-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/