W3C home > Mailing lists > Public > public-device-apis@w3.org > May 2012

Re: Device light and proximity sensor

From: Doug Turner <dougt@mozilla.com>
Date: Wed, 9 May 2012 11:16:09 -0700
Cc: public-device-apis@w3.org
Message-Id: <F91D26FA-A20D-44A2-A4C6-CFA03D76A1AC@mozilla.com>
To: Dave Raggett <dsr@w3.org>

There are a couple things here, so I'ld just address inline.

> The simplest answer is to avoid passing back the additional data.

Obvious and true!

> We
> also need to worry about the default behavior if the device doesn't have
> a sensor or it is switched off and for an external reason can't be
> automatically switched back on.

I am not sure we need to build something to support that.  

> The min, max and default values are all
> potentially useful for finger printing.

So is everything else we add.  I am sure you're not suggesting that we give up adding device apis because fingerprinting is too big of a worry.


> Users may be more concerned about the performance of an application,

Sure.

> which may depend on the application being able to tune the sensor events
> appropriately,

Not sure that is true.  Do you have an example of where someone needs to tune sensor events so that their application can perform better?


> This plays into the larger discussion of the future of
> online privacy and what will follow on after Do Not Track.


Okay.  Sounds out of scope.  What will follow on after DNT?  I am not sure I read anything about that yet.

Thanks!
Doug
Received on Wednesday, 9 May 2012 18:16:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 18:16:41 GMT