W3C home > Mailing lists > Public > public-geolocation@w3.org > January 2009

Re: real location vs. fake location

From: Doug Turner <doug.turner@gmail.com>
Date: Tue, 27 Jan 2009 10:25:11 -0800
Cc: "public-geolocation@w3.org" <public-geolocation@w3.org>
Message-Id: <AFB42293-2832-4416-A86F-A4295DD3C79D@gmail.com>
To: Erik Wilde <dret@berkeley.edu>

Hi Dret,

This is an implementation detail.  You could imagine a User Agent  
supporting "Lying" by allowing their user to define their location  
manually in some manner.


On Jan 27, 2009, at 10:20 AM, Erik Wilde wrote:

> hello everybody.
> "Any good social geoapp will let you type in a fake position  
> manually."
> http://www.wired.com/gadgets/wireless/magazine/17-02/lp_guineapig
> interesting article. we recently had this discussion about "just the  
> current position" vs. "any position", and i guess the underlying  
> question is, given the above statement, can i lie to my app, and/or  
> can i lie to my device? there's a trade-off; if i can lie to my app,  
> all my apps have to support lying, and i have to be consistent at  
> lying. if i can lie to my device, i only have to do it once, and  
> then all my apps will be fed the same lie. this in a way does not  
> affect the API design, but i think if the wording in the draft  
> implies (and i don't know that) that the position has to be the real  
> and true position of the device/user, then this could be changed to  
> saying something like "assumed position".
> cheers,
> dret.
Received on Tuesday, 27 January 2009 18:25:49 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:33:51 UTC