- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Sep 2022 10:14:24 +0000
- To: public-webrtc-logs@w3.org
This particular vagueness was phrased by @youennf. Youenn what if we add a hardware mitigation algorithm section that we refer to, and for now we make it explicitly that you MUST have "context capture state = true". While this does not have any vagueness, we would have a go-to place in the spec if we want to add other steps in the future where it should also be allowed to expose a metric. It would be nice if we could be in a state where we're over-protective instead of under-protective allowing more discussion when the time comes that we want to expose the metrics to more use cases. I feel like we get stuck on trying to have something be perfect and then we don't progress. Better to be over-protective and revisit, I say, so we can unblock the PR. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/675#issuecomment-1256030677 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 23 September 2022 10:14:26 UTC