3 ms·
> My point is that trying to get this information by default is a bad sign. Suppose we want to create a search site that can use location info (for some entire
by kazinator 5y ago
> My point is that trying to get this information by default is a bad sign.
Suppose we want to create a search site that can use location info (for some entirely legit purpose), but we don't ask by default. That implies it must be an opt-in user preference.
To maintain a user preference, we have to create a tracking profile for the user. That's "evil" too, oops, and there will be a cookie pop-up.
Say we are already doing that; we have various preferences. Why would we complicate them by adding a location preference, if that preference is already handled in the user's browser? Firefox indicates right in the address bar that you denied location access to the site.
I always click deny on these requests, but if I had to code it, I probably wouldn't do it differently.
- Nextgrid 5y agoYou can store the preference in a “location_optin” cookie which can only be false or true and ask the browser for location only if it’s set to True. This is not tracking and would not even require a consent prompt for GDPR purposes.
- ASalazarMX 5y agoIt shouldn't ask for location by default, but offer a toggle in the UI to enable local searches, which when enabled would ask for it. This way, it won't annoy the user for their location every time they search in a private window.