- From: Ian Hickson <ian@hixie.ch>
- Date: Mon, 4 Jan 2010 22:48:49 +0000 (UTC)
- To: David Rogers <david.rogers@omtp.org>
- Cc: "Tran, Dzung D" <dzung.d.tran@intel.com>, public-device-apis@w3.org
On Mon, 4 Jan 2010, David Rogers wrote: > > Apologies for not responding to this earlier, but I was away. Just a > comment on Ian's point about privacy. It depends on the application of > the technology as to whether it is privacy sensitive, as a basis abuse > case - if proximity is used in my house then there are privacy issues - > i.e. I don't want to be burgled. We may be talking about different kinds of proximity sensors. I was referring to the kind of sensor found in, e.g., the iPhone, to detect when the phone is being held up to the user's ear. I don't see a privacy problem with exposing that data. > There are a number of other use cases that could be applied - e.g. if I > am using web apps to measure control data in a large plant this could be > subject to attack (for various reasons). I agree that external sensors shouldn't be exposed without user-controlled explicit per-origin opt-in. > The potential future applications for device APIs are quite exciting but > as I've said before we are connecting the physical world to the internet > world and we have to be really careful about how we go about it. Agreed. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 4 January 2010 22:49:19 UTC