- From: Kenan Sulayman via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Dec 2018 22:23:58 +0000
- To: public-geolocation@w3.org
I would very much appreciate a more sober reflection on how this might possibly affect developers and users. The privacy concerns are perfectly valid. But removing the API, or locking it down, will wipe out a complete genre of interactive online games. Not only the ones on the web, but rather those distributed to mobile devices via Cordova (et al.). Additionally, how do you intend to communicate this permission request to the users? What's the difference between device acceleration and orientation data for the end-user? What if the user only permits either of them? Based on what rationale? What if the user does not understand the requested sensor function? Does requesting permissions protect users? Or does it simply limit the “tracking” to big platforms that provide so many features that there's at least one with a credible use case for one of these APIs, opening them for the whole rest of the platform? I'm unconvinced these questions have sufficiently been answered. -- GitHub Notification of comment by KenanSulayman Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/57#issuecomment-449513238 using your GitHub account
Received on Friday, 21 December 2018 22:24:00 UTC