The C̶a̶k̶e̶ User Location is a Lie!!!
The C̶a̶k̶e̶ User Location is a Lie!!!
A post discussing the nuances around location-based programming. Various ways to access user location, how they can fail, and what to do about it.
See also: How a remote Kansas location keeps getting visited by the FBI
Disclaimer - the above is an 8-year-old story. No idea if the three-letter agencies are still turning up there, but I wouldn't be surprised.
Regarding location for the purpose of determining what language to render the app or website in: the article skips over the fact that users can configure their preferred and fallback languages in the browser. It's perfectly possible to access that in JavaScript and render the app or website accordingly. You don't need location information for that. In fact, it totally ignores the fact that some people live (or are visiting) in a region but don't necessarily speak the language. I find it super annoying when google presents me with suggestions or ads for local businesses when I'm on vacation.
[ context for "Cake" here ]
... "The player-character, Chell, is challenged and taunted by an artificial intelligence named GLaDOS (Genetic Lifeform and Disk Operating System) to complete each puzzle in the Aperture Science Enrichment Center using the portal gun with the promise of receiving cake when all the puzzles are completed." ... https://en.m.wikipedia.org/wiki/Portal_(video_game)I want context for that funky C̶
Seems like a great place to hide if you're forced to wear a GPS bracelet. Everyone will just shrug it off.
You just need to able to get there instantly, and after that, the ability to tread water for a long, long time.
Especially when you're born on New Year's 1970
Good article, apart from talking so much about choosing a language for the user and ignoring the Accept-Language header, which exists solely for this reason.
Most websites seem to ignore this header and just show you whatever their geo-ip says.