16

This question already has an answer here:

So we got all new and shiny close reasons and a little bit reworked dialog which works very well and is very nice and handy. But there is one question left, as what do we close too localized questions now?

It actually helps to read the documentation, "too localized" was removed because it was misused most of the time:

5(A). "Too Localized" is no longer necessary since the specific off-topic reasons now address its main use case. (new)

Too Localized was, by far, the most misused close reason in our surveys, with both Community Managers and Moderators deeming over 50% of randomly sampled TL closures to not have merited closure (including on SO).

Today, TL is used helpfully on code dump questions on SO, but the new OT reasons are where this is now correctly addressed. SO can use "Large blocks of code with requests for debugging without meaningful supporting info" as a specific OT reason.

But the new dialog leaves us with only four options:

  • Programming questions are off-topic on Meta Stack Overflow.

  • This question does not appear to seek input and discussion from the community. If you have encountered a problem on one of our sites, please describe it in detail.

  • Changes to the system or to the circumstances affecting the asker have rendered it obsolete. If you encounter a similar problem, please post a new question.

  • Other (add a comment explaining what is wrong)

Only the "other" reason does very well fit on "too localized" questions now, doe we close it with that?

marked as duplicate by Josh Caswell, Danny Beckett, ɥʇǝS, Lucifer, hims056 Jun 29 '13 at 3:46

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • 4
    You've listed the meta sub-reasons. Is this question specific to meta? Most "too localized" questions on meta would go with the third sub-reason. If this isn't about meta; then the main site will have an entirely different set of sub reasons. – Servy Jun 14 '13 at 13:58
  • funniest example of "Too Localized" I ever seen - the question has about 200 upvotes, 27K views and about 80 linked questions. If that's TL then I don't know what isn't – gnat Jun 14 '13 at 15:50
  • 1
    @gnat "This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time". Accept rate is no longer around, so... yeah. ;) – J. Steen Jun 14 '13 at 17:28
  • @J.Steen that "specific moment in time" is several years of SE history. You know, in theory I can understand how this can be formally squeezed into TL, but 200 upvotes, 27K views and about 80 linked questions make this look very silly anyway – gnat Jun 14 '13 at 17:30
  • @gnat It looks silly, I agree, but the close reason is valid. What's more ironic is that the close reason could itself become too localised if we ever return accept rate. ^^ – J. Steen Jun 14 '13 at 17:31
  • @J.Steen that made my day, thanks! – gnat Jun 14 '13 at 17:32
  • Can we/you pick a better example, or example_s_? This is a serious issue with the new close reasons that I want to air. – Josh Caswell Jun 14 '13 at 18:44
1

From the post you link to:

5(A). "Too Localized" is no longer necessary since the specific off-topic reasons now address its main use case. (new)

Too Localized was, by far, the most misused close reason in our surveys, with both Community Managers and Moderators deeming over 50% of randomly sampled TL closures to not have merited closure (including on SO).

Today, TL is used helpfully on code dump questions on SO, but the new OT reasons are where this is now correctly addressed. SO can use "Large blocks of code with requests for debugging without meaningful supporting info" as a specific OT reason.

You close them as Off Topic, and you pick a reason that fits the question. There is no one OT reason that fits all valid Too Localized questions.

If you cannot fit it in a OT category, perhaps the question was not Too Localized in the first place?

For the specific question that triggered this post in the first place, I do not think would warrant closing that one as Too Localized. It is a genuine support request, it is on topic, and can bite others. You may feel the issue is trivial, but it is not localized to one person or small geographical area. It should not be closed in the first place.

  • 2
    I just saw that, yes...but with what sub-reason? – Time Traveling Bobby Jun 14 '13 at 13:55
  • 1
    @M.NightDemonbobby There won't be just one. It will depend on the site that you're on, the specifics of the question, as well as what new sub-reasons end up being added (so far they're not finalized, and are of course subject to change over time). – Servy Jun 14 '13 at 13:56
  • 1
    Sub-reason: "Typo questions are off-topic on Meta. Ask it on the main site to get downvoted to oblivion." – Antony Jun 14 '13 at 13:57
  • 3
    @Servy: I'm not sure what you want to say, but my main point of view is that there is no option anymore to close really too localized questions (like mishaps during entering a date, see my example). – Time Traveling Bobby Jun 14 '13 at 13:58
  • @M.NightDemonbobby And my point is that there will be a new sub-reason for "offtopic" added to address that specific case. It just doesn't exist on meta because that close reason doesn't apply to meta. This isn't rolled out to SO yet. – Servy Jun 14 '13 at 13:59
  • @M.NightDemonbobby: I am not certain that that question is too localized. That was the point of removing that closing reason. – Martijn Pieters Jun 14 '13 at 14:00
  • "...perhaps the question was not Too Localized in the first place?" Oh, that's an idea...I have to think about that. – Time Traveling Bobby Jun 14 '13 at 14:00
  • @M.NightDemonbobby As per the quote; 50% of TL questions weren't really TL, so a lot of questions previously closed shouldn't have been closed as TL to begin with. Some just shouldn't have been closed, some should have been NARQ. – Servy Jun 14 '13 at 14:01
  • 1
    I agree that it's not too localized. It's been asked at least twice. It's clearly something affecting multiple users (probably even more who just haven't noticed). – yoozer8 Jun 14 '13 at 15:16

Not the answer you're looking for? Browse other questions tagged .