On the backend glow sees location data like Country:State/Region:City:Latitude:Longitude. We're not keeping lat/long in our region totals on the frontend since it's not useful to us. And specific region data is buried in a huge JSON dump for the whole world, so our current data sources won't be useful here. A better API would take the user's lat/long and return specific numbers for their continent, country, region, city. The client can then decide what it wants to show. How is the geolocation going to happen? Will it be based on IP or will it use navigator.geolocation?
(In reply to comment #1) > On the backend glow sees location data like > Country:State/Region:City:Latitude:Longitude. We're not keeping lat/long in > our region totals on the frontend since it's not useful to us. And specific > region data is buried in a huge JSON dump for the whole world, so our > current data sources won't be useful here. > > A better API would take the user's lat/long and return specific numbers for > their continent, country, region, city. The client can then decide what it > wants to show. > > How is the geolocation going to happen? Will it be based on IP or will it > use navigator.geolocation? Over to you James/Steven, can you reply back to Jeff?
Assignee: nobody → jlong
The whole point of the Geolocation API is to let the user choose to be located or not. So I think we should use this. It will only be available on recent browsers and only IE9+ though. But it might also be less effective in terms of convertions than IP detection because it won't display the results right away but after a user interaction. Some users might also decide to leave the website because they are afraid by us asking geoloc information. But we'll see when testing.
(In reply to comment #3) > The whole point of the Geolocation API is to let the user choose to be > located or not. So I think we should use this. It will only be available on > recent browsers and only IE9+ though. What is the normal browser+version spread for this page? > But it might also be less effective in terms of convertions than IP > detection because it won't display the results right away but after a user > interaction. Some users might also decide to leave the website because they > are afraid by us asking geoloc information. But we'll see when testing. I'd expect IP detection to be more effective since they don't have to interact with the page before we hit them with impressive data.
I'm copying Alex and Doug Turner because they know more about geolocation privacy issues than I do, but I'm uncomfortable with the idea of identifying where a website visitor is coming from and displaying that without their prior consent.
(In reply to comment #5) > I'm copying Alex and Doug Turner because they know more about geolocation > privacy issues than I do, but I'm uncomfortable with the idea of identifying > where a website visitor is coming from and displaying that without their > prior consent. Sorry I'm late to the game. I was initially thinking this could show some stats on their country based on locale. More general information that doesn't feel as intrusive. But I'd love to hear more from folks who specialize in privacy. Technically, a lot is feasible hear so it just depends on what we feel is appropriate.
Hey Liz! Thanks for adding Alex, I've actually had a separate bug open under legal for him to address this more privately for a few weeks now: Bug 652900 I will set up a meeting, but we would like to proceed in a very general way and with a very targeted and limited testing audience (e.g. starting with the continent or just picking 7 major cities like New York, Columbia, London, etc.). I think there is an elegant and friendly way to do this to test the idea out and if it does increase conversion and create a highly positive experience, we could then figure out how or if to scale. Something to also consider is how Firefox is very clear on privacy and location-aware browsing: http://www.mozilla.com/en-US/firefox/geolocation/ Unlike a lot of companies and browsers we aren't using or selling the user's data and in fact, any website on the web is able to detect where a user is coming from, it's the challenge of being transparent about it and doing something useful with the information. Meeting invites incoming!
Thanks Chrissie, I'd forgotten about the other bug.
Assigning to nobody until we figure out how we're actually going to do this.
Assignee: jlong → nobody
Closing this bug, we'll revisit geolocation outside of Glow at a later time. Thank you all!
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WORKSFORME
Component: www.mozilla.org/firefox → www.mozilla.org
Product: Websites → Websites
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.