- From: Fuqiao Xue <notifications@github.com>
- Date: Tue, 29 May 2018 06:03:39 -0700
- To: w3c/screen-orientation <screen-orientation@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/screen-orientation/pull/116/review/123980722@github.com>
xfq commented on this pull request. > <p> - This specification does not allow an origin access to sensors on a user’s device directly, but information exposed by sensors (e.g., the screen orientation angle) can be accessed indirectly. - </p> - </section> - - <section> - <h2>Access to aspects of a user’s local computing environment</h2> - <p> - The screen orientation type and angle of the device can be accessed with the API specified in this document, and can be a potential fingerprinting vector. + The screen orientation type and angle of the device can be accessed with the API specified in this document, + and can be a potential fingerprinting vector. However using this information is very difficult compared to other fingerprinting information. + Aggregating information derived from this API is not very helpful in fingerprinting. + In particular the Device Orientation API provides a far more detailed version of the same information. By "Device Orientation API", do you mean the [DeviceOrientation Event Specification](https://w3c.github.io/deviceorientation/spec-source-orientation.html), or the [motion sensor specs](https://w3c.github.io/motion-sensors/)? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/screen-orientation/pull/116#pullrequestreview-123980722
Received on Tuesday, 29 May 2018 13:04:06 UTC