iPhone 3.0: Safari Geo-Location Not Just for Google's Latitude

iPhone 3.0 - Safari Geolocation

Last week we posted on Google's Latitude service coming to the iPhone by way of Safari. Of course, as Computerworld (via MacRumors) points out, for the location-tracking buddy service to work in the browser, the browser must support geo-location, and not just for Google.

According to BrowserSphere developers were told back in March that Safari would support the Geolocation JavaScript classes, which "work with the onboard location services to retrieve the current location of the device."

So we guess IP addresses won't be the only way for annoying web ads to try and localize us any more?

Have something to say about this story? Share your comments below! Need help with something else? Submit your question!

Rene Ritchie

Editor-in-Chief of iMore, co-host of Iterate, Debug, Review, Vector, and MacBreak Weekly podcasts. Cook, grappler, photon wrangler. Follow him on Twitter and Google+.

More Posts

 

0
loading...
0
loading...
0
loading...
0
loading...

← Previously

1Password touch 2.0 Now Available

Next up →

iPhone Jailbreak 101: What Are Those Swirly Black Badges on Mail, Phone, iPod?

Reader comments

iPhone 3.0: Safari Geo-Location Not Just for Google's Latitude

14 Comments

Writers pro tip: It's never "try and." Use "try to" instead.
I really wish Safari would ask permission for location information for each site. At this point it's not clear whether this will be the case. If it's just a one-time permission for any and all websites to access my location, I'll be choosing "Don't Allow."

Just release the damn thing already Apple. I swear you guys have the longest Beta's ever. Well not longer than Google but still damn.

@truth I feel your pain but in some ways apple are good. Google takes ages winmo rarely gets updates and even rarer that carriers release them quickly if at all (unless you install 3rd party cooked Roms)
Agree with muero about the location request prompt

This would have been a great article for me about a week ago. I have an app that uses WebKit that was just rejected because it did not work with these APIs properly in 3.0. The problem is I can't find any documentation, or even an example website where I can go to reproduce the problem and catch the error. If anybody knows the full URL for the website in the screenshot, please post it.

Personally, I'm not all that enthused about my browser knowing my exact location.
If I want to search for something near me, adding a city name to the search string is easy enough.
I can't imagine willingly allowing anyone I know to stalk me, and I'm certain I don't want unknown web sites to do so either.
So the question for those enthusiastic about this feature, I have One Question: What would you see this offering you in exchange for surrendering your privacy?

This computerworld article linked by MacRumors suggests domain-by-domain restrictions, though of course the screen shots could be faked.
But even if they are by domain and have a same-origin restriction like XHR (e.g. so that when you are visiting TIPB, theiphoneblog.com could ask for your location, but not smartphoneexperts.com, google-analytics.com, or theblackhelicoptersarecomingtogetme.com), I cannot yet imagine any feature out there compelling enough to make me click "OK" on this.

The paranoia in me has me nervous about this. I'm with Muero and icebike on this topic. I do not see myself tapping "Allow."

@develeper, on your computer, just drag and drop the image into the URL bar and it will take you to it's excact URL that the picture was taken from. This works in firefox for windows.

Thank you for this helpful article. I have been reading your blog for the past couple of weeks, and I have been enjoying ever second of it There are so many blogs out there, its nice to find a good one!. I write for a blog that is a lot like yours, would you be interested write a guest post on it? Please email me if you are interested