[webrtc-stats] The stats API allow hardware fingerprinting (encoder, powerEfficient) (#675)

henbos has just created a new issue for https://github.com/w3c/webrtc-stats:

== The stats API allow hardware fingerprinting (encoder, powerEfficient) ==
From #550:

> `decoderImplementation`, the `codec` data point, etc. reveal information about the underlying hardware beyond what's identified by `getUserMedia`

For the `codec` issue, I filed #674 as a separate issue due to the tie with webrtc-pc.
In the most recent TPAC (yesterday) we talked about fingerprinting in the context of adding `powerEfficientEncoder`.
@youennf added to #550 after the meeting:

> @henbos proposed during the meeting the possibility to only expose this kind of fingerprinting past some user validation (for instance if getUserMedia/getDisplayMedia was called successfully on the document).
> Maybe there is a way to phrase it in a generic way, something like:
> `As this field is a fingerprinting vector, it MUST only be exposed to contexts that the user interacted with in a deep manner, for instance if https://w3c.github.io/mediacapture-main/#context-capturing-state returns true.`

I like this way of phrasing it and think we should add this to `encoderImplementation` and `decoderImplementation`, as well as the recently proposed `powerEfficientEncoder` and `powerEfficientDecoder` (#666).

Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/675 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 13 September 2022 07:45:43 UTC