- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Fri, 18 Feb 2022 13:26:41 +0000
- To: public-device-apis-log@w3.org
(Piggypacking [no pun intended] on this PR for context.) @sandandsnow, I'd like share with you an update on our continued work to improve privacy of APIs in scope of Devices and Sensor WG. Feel free to share this news with PING as appropriate: Following https://w3ctag.github.io/design-principles/#secure-context we limited the Battery Status API to secure contexts. This ensures end-to-end integrity and confidentiality of battery status information and protects users' privacy. As you can see from the initial PR comment, the reason this change took rather long to bake into the spec was to ensure we don't break a large number of websites that rely on this API. We also wanted to coordinate this spec change with the required implementation updates that were approved recently and are now rolling out in phases. This is also a heads up that in the near future we will reach out to PING to do another review of this API. Before requesting your review, we'll first do some informative updates such as refresh on the questionnaire, improve documentation of use cases https://github.com/w3c/battery/issues/25 and possibly also note in the spec a high-level API opportunity https://github.com/w3c/battery/issues/52 that'd further improve privacy (the last one would be a long-term effort). I'll get in touch with you when the specification is ready for PING to take another look. Thanks for working with us. -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/battery/pull/51#issuecomment-1044526452 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 18 February 2022 13:26:44 UTC