- From: machenmusik via GitHub <sysbot+gh@w3.org>
- Date: Fri, 08 Feb 2019 23:28:28 +0000
- To: public-geolocation@w3.org
In reply to: ``` The entire concept of spatial computing on the web is at stake (i.e. motion as a basic input driver to rival mouse, keyboard and touch input drivers). Basic input drivers should not be subject to permission-based access controls (by all means, all other sensor APIs belong behind permissions but absolutely not coarse-grained motion and orientation sensor access). ``` My view is that the reason why we are looking for a different solution than default-enabled exposure is precisely because, for the browsers in question like Mobile Safari, the spatial computing aspect is not likely to be a primary function, and therefore this data is not likely to be a primary input source. As an example, if Avaer were to decide that ExoKit is intended to be an immersive browser with spatial computing as a primary function, then ExoKit could decide to default to enabled for https sites or localhost (or perhaps to any site displayed in immersive mode, if that were too restrictive). My intuition is that obfuscation of the data is at this moment an uncertain solution, and that a more intentional permission model will be needed, with browsers ideally remembering site permissions where appropriate to reduce user friction. -- GitHub Notification of comment by machenmusik Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/57#issuecomment-461982077 using your GitHub account
Received on Friday, 8 February 2019 23:28:30 UTC