The W3C Gelocation API doesn't specify or get involved in the underlying technology to locate the user. Instead it leaves that up to the device itself and then exposes a single API for retrieving that information off of the device, regardless of how it was determined. In the end the developer and the user know nothing about how it was determined, just how accurate the result is.

Let me know if that makes sense.

Ben,

The best place to find updates for things like that is the Twitter Development Talk mailing list. We recently announced a Developer Preview of the Retweet API so that developer would have advance access before we launch a new feature. You can find the list here: http://groups.google.com/group/twitter-developmen...