- From: Doug Turner <doug.turner@gmail.com>
- Date: Fri, 11 May 2012 08:38:32 -0700
- To: Dave Raggett <dsr@w3.org>
- Cc: Marcos Caceres <w3c@marcosc.com>, Dzung D Tran <dzung.d.tran@intel.com>, Anssi Kostiainen <anssi.kostiainen@nokia.com>, "public-device-apis@w3.org public-device-apis@w3.org" <public-device-apis@w3.org>, Jonas Sicking <jonas@sicking.cc>
On May 11, 2012, at 8:29 AM, Dave Raggett wrote:
> On 11/05/12 16:13, Doug Turner wrote:
>> I love this kind of input. It is important to remember that
>> fingerprinting is a concern. However, I think that you might be
>> better off discussing fingerprinting at the w3 privacy wg.
>> Fingerprinting can be done on many APIs, not just these Device APIs.
>> Do you have a concrete proposal to address these concerns across the
>> main APIs, or are you just waving the fingerprinting flag as a
>> reminder to us all?
>
> We were discussing the pros and cons of {min, max, value} events versus
> near and far events for proximity. Finger printing is just one of the
> factors to take into account.
Yes, it is. Just like every API we expose.
> I would like to better understand the use cases. Is it mostly about
> sensing when a smart phone is against someone's ear? I don't really
> understand that for web apps though, unless you are using the web app as
> an audio player or a P2P voice call over Web RTC. Another use case is
> disabling the display or otherwise reducing battery demands when someone
> isn't near the device. In this case, we are presumably talking about
> sensing someone further away from the device. What am I missing about
> the use cases for proximity and web apps?
Games? Imagine you can use the proximity sensor to control some aspect of the game. Surely a binary attribute is probably not what you want.
Doug
Received on Friday, 11 May 2012 15:39:04 UTC