- From: Rich Tibbett via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Jan 2019 14:34:18 +0000
- To: public-geolocation@w3.org
> For us, it is either this or disabling the API by default until we can make it safe. All content relying on the API will break overnight. No replacement sensor access is provided on WebKit (Generic Sensors API). No alternative browser engines are allowed on iOS so there is no way to keep any applications relying on those APIs running. No deprecation strategy is planned warning developers of disruption or revocation of sensor data before they land in Safari. A cliff-edge fall-off of usage is the correct way to modify an extensively used 8+ year old web platform API. Browser-based content and embedded web view content in native applications will cease operation in all of the following use cases: * Games and gaming * Navigation * Virtual Reality * Augmented Reality * 360 viewers (videos, panoramas) * 3D scanning * Gesture recognition * Step counters * Physical activity monitoring * Sleep monitors Multiple proposals exist to make the emitted motion sensor data both a.) still useful for legitimate use cases and b.) resistant to raised security and privacy concerns by refining/limiting the data emitted in different ways. Those solutions will not considered further because the effectiveness of those solutions needs further investigation/research even though they are cited as potentially resolving all current security and privacy concerns by the original investigators. Instead we will modify the API invocation to require permissions/user-gesture or just remove the whole API because it is easier, less implementation work and resolves all security and privacy concerns because then there are no use cases or usage anymore. Now contrast this to [the alternative approach/summary I posted above](https://github.com/w3c/deviceorientation/issues/57#issuecomment-448533631). -- GitHub Notification of comment by richtr Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/57#issuecomment-452717086 using your GitHub account
Received on Wednesday, 9 January 2019 14:34:19 UTC