Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Dunno. How can you inadvertently request location info when you're implementing a keyboard for Android?


We check for last known location in order to provide regional dialects via Living Language.

I'm not saying it's legit or required, but that's their explanation from the link there.


Why don't they just use the current locale info ?

Why assume their keyboard is extra special when the user is happy with how the rest of the system is setup?


Looks like Living Language isn't just about figuring out the user's current locale. It's about learning local slang and dialects based on what Swype users are typing, in order to give users a dictionary that's much more specific than something generic like "en-US".

For something like that you'd legitimately want to know where someone is down to the city or even neighborhood. Though checking their location 4000 times/day still sounds egregious to me. And possibly misguided - the way I speak English isn't going to change just because I've gone to Petoskey for the weekend.


I think that the 'sloppy programming' comment was directed at the volume of requests. Maybe a poorly chosen location poll or polling interval. Whether or not a keyboard should be polling your location at all is another question.


Read the thread and specifically the answer from one administrator of the board.


I'm reasonably sure that the Google keyboard does. It's used for nearby-city autocomplete, which can be pretty handy.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: