I agree with your concern — we should engage with people more before closing things — but I think put in the position to close this question, I might followed suit and might have pulled the trigger without explanation.
While it may sound snobby, my only excuse is I expect a certain level of English and technical understanding here. If you can't explain even ...
Absolutely. The age of a question is completely irrelevant when choosing duplicates. What we want is the best, most comprehensive and inclusive answer. If a question asked today has better answers than one asked four years ago, we should close the old one in favor of the new.
People often think that the age of the question should somehow be a factor when ...
Yes. "Mint," "Debian," "Kali," etc., don't mean "stop paying attention."
You're right that it's bad to robo-close questions based on the presence of specific keyword or tags, and that this is something that sometimes happens on our site, that it happened in this particular case, and that it needs to stop happening. The question formerly titled Bring Back ...
After a review of your close habits, the volume of stuff that comes to the site, and how it all crashes into this sort of flaming wreckage, there really is a need for increased.
We've thus raised the amount of close votes on Ask Ubuntu to match Stack Overflow, at 50 votes.
You can't retract flags.
A moderator will see it and likely disagree with it. Assuming that happens that will count against your helpful flag totals but that's rather the point: don't flag things willy-nilly.
I should point out that having declined flags is not the end of the world. Everybody who gets involved in flagging has a few so don't take it as a ...
Vote to close as many questions as you legitimately think need closing - no more, no less.
If you're going organically, it's fine to use no close votes a day. Similarly, it's fine to use all fifty in a single day, as long as they're all warranted.
The reasoning for this is discussed here by Jeff Atwood himself (well, for specifically the suggested edit ...
At present when we decide to "Do not close" a question this is relevant to our own review queue only. It will not (and should not) neutralize close votes cast by others. But it is not displayed anywhere.
We need to comment our disagreement (or vote on a disagreeing comment if there) in the hope people read it before casting their votes.
It would be a nice ...
People get closed posts wrong.
Closing a posts means that either there is no quality in it enough to meet the site's standards, or simply its a useless question (either a dupe, or really not a post per se).
That is an opportunity to actually improve the post, should be taken as one and its meant to be taken as such.
No comments? What do you mean? There is ...
I am another of the original close-voters. My thinking was similar to Tom Brossman's. While I didn't think the question's subject matter was necessarily too broad, I thought there were several different, related things the OP could have been asking.
Furthermore, it seemed that the question might have been intended as a feature request. Since ...
Jorge Castro has commented with an answer that I think applies to the specific case in this question:
Feel free to post it as an answer then we can retitle it as a canonical 404 question for wubi!
I plan to do that. Assuming everybody's OK with that resolution, this question no longer needs to be answered for that specific example.
I'm posting this as ...
I've been playing janitor on close votes ever since I broke 3k. Even attacking the close queue every day I can't make a dent. Perhaps boosting the number that can be reviewed in a day would help? During the past week I've seen the number climb from the high nine's to the current 1k+. Due in part to the large number of flagged poor questions the heap is huge. ...
Your points here ignore the simple fact that not all questions about EOL releases are automatically off-topic so any system that attempts to look at tags needs to be intelligent enough to work out what's actually being asked.
That —err— automatically rules out anything fully-automated.
The review queue idea isn't necessarily bad. I doubt SE would want to ...
It means the question you were trying to close it against was already closed as a duplicate of this question. Hence a circle ;)
Please don't close questions against questions already closed as a duplicate. Follow the chain to the origin!
In my capacity of supporting the other three members of the community, I was content that this was not a borderline case and that it was a potential better fit with Unix & Linux.
If the OP flagged for the migration I would have approached the mods there to migrate.
In this case, a junior member of the community dropped an "off-topic" comment.
If both questions have good content, they should be Merged rather than closed.
Otherwise, you should vote to close the one that's worse. Which can be defined in a few different ways. I'll try to put them in ascending order of importance (this is my opinion, nothing more):
Has poor quality answers (one clinches the deal, as far as I'm concerned)
Is less ...
I can't find the MSO Q&A on this, but I'm 99% sure that this is status-bydesign.
The system is designed for Stack Overflow, and they design it so that if you're out of the "lay man" votes, you need to just let it be. This is a problem on small-medium sites like ours.
Anyway, just flag it using this "It needs moderator attention > Other", and explain. ...
Not a real question
It is a real and valid question, but just one or more vital piece(s)
of information isn't provided, such as a specific hardware
The definition for NARQ is:
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably ...
Luis Alvarado is our resident vacuum cleaner.
Upvote if you agree or are Luis Alvarado, downvote if you do not agree :)
I'll will max my reviewing for today soon
Related: How can we encourage 3k+ users to review more Close Votes
When the OP of the question agrees that their post is a duplicate, a binding vote by the Community user is cast and closed.
See this MSE post for more details: New UI encourages askers to confirm or dispute duplicate votes
As always, it depends
Looking at a question like:
PLZ HELP ME ASAP
error: some-error another error -> some totally unclear error
I'd say Shoot on sight!. In such a post is no effort whatsoever to even write down a decent question. It shouts DO MY JOB!
On the other hand, we've got plenty of unclear ...
Closing questions is well, even when it is too fast. But it would be preferable to leave a comment explaining what they can do to improve it.
Let's take an example here:
Environment still acting up
I tried running some code to reset my proxy, and it messed with my desktop environment. I had to put the permissions back, but even after that, my ...
Answers to unclear questions rely on guesswork. This can lead to answerers barking up the wrong tree, bad answers, good answers to the wrong question, and a host of confusion. It's best that unclear questions are closed immediately, until they can be clarified. Once they're clarified, they should be reopened, also as fast as possible.
Closing unclear ...
Questions that are not clear enough to plausibly be answered should be closed. And there is no reason to wait to close them. After all, closed questions that are edited are automatically added to the reopen queue, and these days the system even allows us to take back our close votes.
So the core thesis behind this proposal is a good one. It is simply that ...
Instead of just trusting flags and closing random stuff up we as moderators need to have a look at the information on the posts before making up your minds. There are many possible actions to be taken and not all posts deserve to be "just closed".
For abandoned questions and linked posts on the regulators room I tend to follow these guide lines:
Check if ...
There's no retracting a close vote.
However, it will expire in its own time (48 hours? can't remember exactly). If you think your vote will wrongly encourage people to vote against something, leave a comment explaining why you think it should stay open (eg, why it isn't a dupe).
But either way, people shouldn't be blindly voting to close things. If a ...
In this case (between these two questions) I'd be inclined to leave both as they are. One is dealing with two distinct applications (a browser and not a browser) and the other is dealing with two browsers. There are several technique of doing what they're asking the if it's the same protocol, that cuts off some options and opens up others.
It's a pretty ...
Old questions with good answers should remain open. Just remove any references to the version in the question itself.
Why remove version information? If a question has an answer and the release is since EOL'd just leave it alone.
Old questions that have no good answer...
This seems highly subjective. If the question has an answer leave it be.