- From: Mikhail Pozdnyakov via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Apr 2017 10:26:52 +0000
- To: public-device-apis-log@w3.org
We (me and @alexshalamov) have a concern that introducing of low(high)-resolution mode will be quite confusing for web developers who will not know exactly which permission token is required for the functionality they intend to provide. Moreover, definition of high / low thresholds by the UA, would lead to fragmentation between browsers. Also for motion sensor we can hardly find a ‘safe’ zone for both frequency or accuracy (https://github.com/w3c/sensors/issues/98#issuecomment-281339687 ), search papers [ [ALS](https://arxiv.org/pdf/1405.3760.pdf), [Motion sensors](https://pdfs.semanticscholar.org/3673/2ae9fbf61f84eab43e60bc2bcb0a48d05b67.pdf), [Gyro](https://crypto.stanford.edu/gyrophone/files/gyromic.pdf) ] tell that there can be vulnerabilities even at low frequencies. For ALS we do not really have the use cases requiring accurate readings (@tobie do we?), even rough data (10 - 100 lux accuracy) shall be enough for example for updating a web page style based on the surrounding illumination. We believe that for any sensor type the returned data can be rounded to the values which are good enough to implement the use cases, if it improves user’s security/privacy (this UA can decide), but there is no actual need for introducing any extra modes and permission tokens. -- GitHub Notification of comment by pozdnyakov Please view or discuss this issue at https://github.com/w3c/sensors/issues/183#issuecomment-297341213 using your GitHub account
Received on Wednesday, 26 April 2017 10:26:59 UTC