73

I thought the real good use of Too Localized was for typographic errors and small, silly mistakes. It doesn't make sense to call most of these off-topic because the user usually isn't thinking he has a typo, he doesn't know what the problem is. Therefore he is giving legitimate code, and then it's discovered that it's just a typo; so it won't really help ...


56

Questions where the problem was fixed, but no one knows how (and no one is interested, usually really narrow situations) For example: OP posts a comment: Nevermind, I have fixed the problem OP never comes back to answer how. No one else really cares.. (like I said, it's usually a simple problem..). This certainly doesn't fit under off-topic, ...


44

I have just been reminded of something that happens a LOT on travel. A person asks a question with a short shelf life that's perfect for the site when it's asked, but won't be in a few weeks or months. This can include updates on a natural disaster, or a significant closure like a major museum being closed for repairs or other indefinitely-long things. It ...


36

I completely agree with and understand all the problems with "Too Localized", and I wholeheartedly agree with the decision to remove it. And I do think it makes sense to replace "Too Localized"'s previous legitimate uses with site-specific close reasons. But I do not think the right solution is to lump these site-specific close reasons in with the "Off ...


25

Syntax errors mysql_* expects x y give Undefined offset Blank page of death Convert my code in language X to language Y The 100000th question about how to access an array value Trying to access a GET variable on a POST request Are just some I can think of. I'm pretty sure when I open the main frontpage I can think of some more. Note this is only from the ...


20

I've been thinking about this for the last week or so, and I feel like the problems with the wording come down to Dennis's last three points: Distracting focus on geography. Unclear period of time. Hand-wavy reference to the global Internet audience. Really, what matters most here is that first bit - "unlikely to ever help future visitors". Everything is ...


19

You shall not muzzle the ox when it treads out the grain.                                                                     --Deut. 25:4 For all the high-minded language we throw around ...


19

The essence of a typo question to my mind is one like this: I have application hosted on CloudFoundry... I have a download controller to download an APK file that I have on Web Application/Apps folder.. but, I have an error 404. Please help me. class DownloadController { def android() { def webRootDir = servletContext.getRealPath("/") ...


16

From what I could gather the problem was due to a typo as evidenced in this deleted answer and the comment attached: ..and OP also added the following to the question: Updated: Typo error require changed to required. [ My mistake ] This suggested that the cause of his difficulties was in fact the "typo" and it wasn't made abundantly clear ...


16

I feel this solution is a regression. Under the new system, a "Too localized" would be Off-Topic > Other However while the comment box is available, it is not required so all the question-asker sees is off-topic instead of unlikely to help any future visitors... or an extraordinarily narrow situation not generally applicable to the worldwide audience ...


15

Ideally, write a generic guide to “how do I access common nested data structures in X”, in the form of a question with an answer that covers 90% of the cases. Close 90% of the incoming questions as duplicates of that canonical question. Answer the remaining 10%, which are advanced enough to be interesting. “Using References” in the old Perl documentation is ...


15

Your Google searches reflect the bias of someone who knows the answer. Someone to whom the words "max" and "range" occur in formulating the question will be well served by anything at all they find, including but not limited to SO questions. But people don't all know those words or think that way. They will search using non jargon words like "largest" and "...


14

Pros of answering obviously problematic questions: You helped the OP solve their problem. Cons of answering obviously problematic questions: Closed questions are on a path to deletion, and your answer will go down with it if the question is eventually removed. OP got what they were looking for without much effort, and may not realize that they need to put ...


14

Because we don't think it will be helpful to anyone else. It could be a misspelled function name or a missing semicolon. What are the odds that anyone else would come looking for exactly the same problem? And we definitely don't need anymore answers pointing out the obvious. The next step is to consider if it should be deleted as well.


14

At Android Stack Exchange, we currently see another example for "too localized (in time)", which one could call "obsolete" or "no longer relevant": We've got a tag for Google Reader, and have corresponding questions. However, Google Reader closed its doors, and will no longer be available. Similarly, no new OTA updates are coming out for Android 2.x and 3.x;...


13

...the asker just could have tried the actual code You have to be really careful making that assumption about programming questions, particularly in languages like C and C++ where you can have undefined behavior. In other words, just because a particular piece of code appears to run and work on your system's implementation of C does not mean that it is ...


12

Whenever I encounter a question where the OP's "solution" invalidates the premise of the question, I do two things: I vote to close the question as "too localized". The question is pointless after all. No future answer will be of value since the whole premise of the question was flawed. I flag for moderator attention. I usually leave a custom message ...


12

There was no "Too Localized" option. Only "very low quality" or "other". I selected "other" with the extra comment: "Too localized. The problem was a syntax error of misplacing a quote." In such cases, at least on high-traffic sites like Stack Overflow and Super User, please use canned flags. Canned flags send the post to a queue where it can be reviewed ...


11

Sorry? You want to encourage people to post trivial stuff they can't be arsed to work on so that our contributing users can put time and energy into stuff which--by design--won't make the site better in the future? Really?


11

It could also be considered "not a real question", but I can understand why it was closed as "too localized". Consider the definition of NARQ: not a real question It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help ...


11

First, we have to decide what we mean by typo questions. Some have suggested that syntax error questions count as typo questions, while others believe it's really for questions where the OP forgot how to spell their own name. Syntax errors as "typo questions" Syntax error questions historically happen because the user did something wrong. This is often ...


10

I disagree. "Too localized" is the best close reason for quite a range of questions. In particular (in my opinion) those following the pattern: Huge walls of code (of varying quality) with a couple of lines of text that boils down to: Please debug this for me. Typo questions My code doesn't compile! whiel (foo) { bar; } These questions aren't ...


10

Code Review is for reviewing working code, most questions on SO are about code that doesn't work yet. A very large number of "too localized" questions on SO would be off-topic code review. In general I also don't think that misusing a regular close reason as a migration tool would be a good idea. Migration should be a deliberate action, not a side-effect.


10

I will briefly summarize the case I made at greater length in the closing overhaul discussion. Declaring a question "off-topic" implies it will be "on-topic" somewhere else That is both the commonplace experience of the use of off-topic and pretty much the historical use on SE. Ask a question about Linux software on Ask Different and you will be told it'...


9

I think this is a judgment call that smart people need to make in individual cases. You can find a handy population of those smart people by looking at everyone with 3k+ reputation—in particular, those users with close vote privileges. If 5 people agree that the question is not useful and should be closed as "too localized", they will "vote their conscience"...


9

Roll it back, or, if you don't have the sufficient privileges to roll back revisions, leave a comment asking the OP to restore the content, and flag it for moderator attention. In this case I've rolled back the vandalism for you; and you're right, it's also too localized, so I've closed it accordingly as well.


9

I think we should keep such questions opened if the syntax error is common and can't be caught before the execution of the module/method/script/whatever. Your MySQL example just fits that description, whereas a Java type (like a missing ;) does not. In your example, I would bet that many developpers have such syntax problems, and spend hours wondering why ...


Only top voted, non community-wiki answers of a minimum length are eligible