The "too localized" close reason currently reads:
This question is unlikely to ever help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet.
But it's prone to misinterpretation, as Joel lamented a year ago:
There seems to be some knee-jerk closing of questions as "too localized" throughout Stack Exchange simply because they mention a time span or because they mention a geography. There are many questions which are limited in time or which are limited in geography, which, nevertheless, must not be closed as "too localized."
After discussing another potentially incorrect "too localized" closure in Gaming.SE's chat room, it appears part of the confusion stems from the close reason itself, particularly the "this question is unlikely to ever help any future visitors" and "worldwide audience of the internet" clauses and the amount of wiggle room they afford to closers.
To provide just a few examples of the "too localized" confusion (excuse my Gaming.SE bias, but it's my most active site)...
- The example above — incorrect presumption that questions that don't help a lot of people are too localized
- Is it possible to beat Google's zerg rush easter egg game? — closed as too localized, reasons given at the time were that it was too stupid a game and not something people will care about in the future; reopened.
- How can I craft the Golden Wrench in TF2? — closed as too localized, reason given was that it's because you can't craft it anymore; reopened.
- How should we use the Beta tag? — Two answers (one, two (deleted)) suggest closing beta questions as too localized due to misinterpretation of the "specific moment in time" and "unlikely to help future visitors" clauses
- How should we handle non-beta pre-release questions? — two answers (one, two) incorrectly suggest the too localized close reason is for questions that don't have an answer yet.
- Are questions about patch notes too localized? — suggests incorrectly that asking about a change in a new version of a game is too localized
- Do we need a “General Reference” close reason? — answer incorrectly suggests a question that's Googleable is too localized
- Are Fantasy Sports considered inside of our scope? — answer incorrectly suggests that, because a game runs in seasons, any question would be too localized
- How to handle early Diablo 3 questions? — Another example of incorrectly suggesting any question asking about a game in beta is too localized
- Incorrect belief that a question whose answer will constantly change is too localized
- How to get a diablo 3 beta key? — Immediately closed as too localized because it'd only be applicable for a month.
- Similarly, How can I play Dota 2 Beta? closed as too localized; game has been in private beta for months and currently still is in private beta.
- What are the various promotional versions of Mass Effect 3 (i.e., Gamestop, Best Buy, etc.)? — Incorrectly closed as too localized because the promotions would not stay constant.
- Similarly, What in-game retailer bonuses are available for Final Fantasy XIII-2? received close votes for the same reason
- How up to date is the Android version of Tiny Tower, compared to the iOS version? — General question about platform differences closed as too localized for no given reason (perhaps due to the very localized answer given?)
- Why is LeBlanc forgotten amongst the pros? — closed as too localized because it requires pros to answer. Probably NC, but wanting to get an answer from "pros" or equivalent is the whole point of Stack Exchange.
- What role can Malzahar take in high ELO games? — closed as too localized because the answers could change; reopened after copyediting changes
... on Programmers.SE:
- Too localized: by population size instead of geographical area — whole mess of bad assumptions and suggestions; incurred the wrath of Joel
- Is there a way to phrase a localized question that works for the site? — Otherwise NC question incorrectly closed as too localized because it referred to a programming niche.
...on Meta Stack Overflow:
- time to get rid of too localized? — answer correctly suggests the current wording would technically bar any language not helpful to the worldwide audience of the internet, suggests reworking
- Similarly, another invocation of Joel's ire due to the "worldwide audience of the internet" clause.
- What exactly makes this Python question “Too Localized”? — answer suggests this question (now reopened) was too localized because it's a troubleshooting question (aren't they all?)
- Shouldn't the tumbleweed badge, not be a badge? — Another example of the incorrect suggestion that "too obscure" means "too localized".
Can this close reason be clarified so that it more accurately captures the intent of closing a question as too localized, which is to shut down questions only the asker could answer or care about?