- From: pes10k via GitHub <sysbot+gh@w3.org>
- Date: Fri, 10 Feb 2023 23:09:48 +0000
- To: public-webrtc-logs@w3.org
@alvestrand thank you for the ping. I apologize though, im finding this discussions very difficult to follow so bare with me. My understanding is: 1. Currently, a site can only access a device's `RTCInboundRtpStreamStats.powerEfficientDecoder` and `RTCInboundRtpStreamStats.powerEfficientEncoder` properties if _any_ `getUserMedia`-gated device is [currently playing](https://w3c.github.io/mediacapture-main/#context-capturing-state) 2. The change being discussed here would change things, so that the above two properties are also available anytime _any devices_ `MediaCapabilitiesInfo.powerEfficient` is available Is the above correct? If so, I have two questions: 1. I was surprised by the "any" bits in the above, but i don't see anything in the [exposing hardware check](https://w3c.github.io/webrtc-stats/#dfn-exposing-hardware-is-allowed) that ties the properties of the device being described with the device playing). Is this intentional? 2. I'm not able to find any algorithm or description of when `MediaCapabilitiesInfo.powerEfficient` is made available. Am I missing it? If so, can you kindly point me to it? If it doesn't exist, then the change in this PR is worrying, since it would change a useful, well defined privacy protection, into a privacy protection that was loosely or (un-)defined Apologies if I'm missing obvious things, just, a bit difficult to make sure i have the entire picture right, since it spans 2-3 specs/repos -- GitHub Notification of comment by pes10k Please view or discuss this issue at https://github.com/w3c/webrtc-stats/pull/732#issuecomment-1426475788 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 10 February 2023 23:09:50 UTC