- From: pes10k via GitHub <sysbot+gh@w3.org>
- Date: Sun, 26 Feb 2023 23:26:56 +0000
- To: public-webrtc-logs@w3.org
@henbos i take your point and agree, it would be good to have a similar, common, shared algorithm different-but-similar specs to hook into, to make sure there is a common gate for exposing FP-related information. I think, though, that it'd be a serious privacy loss/harm to remove the mostly well defined (*) algoritm thats in place, and instead point to a currently undefined algorithm, and hope that the pointed-to-algorithm becomes stronger. Could we invert things, and keep the getStats algo as is, and work with the folks defining `MediaCapabilitiesInfo.powerEfficient` to have it point to the `getStats` algo, and unify things that way? Or, if better, spin up a third/distinct doc that defines the "when and what can the page learn about user hardware at different states of user interaction" algorithm(s) and have getStats, MediaCapabilitiesInfo, and anyone else point to that? --- * I just said "mostly" bc I re-read the text and it wasn't 100% unambiguous that the exist getStat's algo would require the clarification you provided in https://github.com/w3c/webrtc-stats/pull/732#issuecomment-1426657623 (though I appreciate that could easily be ignorance on my end) -- GitHub Notification of comment by pes10k Please view or discuss this issue at https://github.com/w3c/webrtc-stats/pull/732#issuecomment-1445498413 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 26 February 2023 23:26:58 UTC