Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
@BonGart If someone finds an OSX-related question that needs to be closed, I would never read that question on my own, because I know nothing about OSX and rarly read questions in that tag. But if someone else reads it and determines it needs to be closed, I can judge if it should be closed as well. So if the other vote draws my attention to that OSX question, so that I can close it, that's a good thing. Closing questions is a team effort. We work on closing questions. We track them down, we discuss them in chat, and we close them - together, as a team. Showing the vote count helps.
@BonGart: What you call "pack mentality", I call "teamwork". Falsely closing a questions sucks, but not closing a question that needs to be closed sucks even more. We want perls, not sand. And closing questions is a big part of that.
I don't care why a question was closed as long as it was the right decision. If it wasn't then I would complain and try to reopen. But that has never happened. In general, I almost never see a question that was closed even though it shouldn't have. So where exactly is the problem? Does it bug you that people are doing the right thing but possibly for the wrong reason? That might be sad, but the end justifies the means. Why people put in their close vote is not relevant, as long as the decision is right. We try to keep a clean ship here, what you're proposing will not further that goal.
