- From: Tim Volodine via GitHub <sysbot+gh@w3.org>
- Date: Fri, 17 Mar 2017 20:36:33 +0000
- To: public-device-apis-log@w3.org
To chime in here, I remember two issues regarding increased frequency: - battery drain (which I guess is inevitable for VR and depends on hardware) - malicious 'attacks' e.g. fingerprinting or even 'eavesdropping' IIRC in crbug.com/421691 one of the papers talks about audio attacks and increasing the sampling rate naturally increases the risk and accuracy of such attacks.. As was already mentioned it's not exactly clear what the reasonable threshold is though and the actual impact of marginal increase. To reduce potential risks we can restrict the usage e.g. to top main frame only, and/or by requiring a user gesture. Additionally we could make the usage opt-in e.g. <iframe allow=sensors_hifrequency>, which would provide extra validation. It seems natural to also disable the sensors after some inactivity and of course when page is not visible or running in background.. I guess this would factor in the 'design-level' security approach mentioned by maryammjd@. -- GitHub Notification of comment by timvolodine Please view or discuss this issue at https://github.com/w3c/sensors/issues/98#issuecomment-287464491 using your GitHub account
Received on Friday, 17 March 2017 20:36:39 UTC