Re: [webrtc-stats] The HW exposure check does not solve Cloud Gaming use cases (#730)

@xingri Im not familiar enough with this part of the code to know what all of those enum options mean, but if this means that `decoderFallback` would only depend on things that happened on the current site (such as the decoder failing previously during the session) then I think thats a fine, A+ approach.

If though the `decoderFallback` value is shared across sites or, or across browser sessions, then i think the fingerprinting risk is possibly still here.

If its the second case, then i'll have to read up more on the kinds of things that could cause `decoderFallback` to be `true` and get back to you (which i could do by Monday at the latest)

-- 
GitHub Notification of comment by pes10k
Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/730#issuecomment-1463119620 using your GitHub account


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

Received on Friday, 10 March 2023 02:18:43 UTC