- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Feb 2023 13:15:32 +0000
- To: public-webrtc-logs@w3.org
See https://w3c.github.io/webrtc-nv-use-cases/#game-streaming for the description of the use-case. Note that attacks requiring a live connection like heuristics about decode time can be used as Diego pointed out. So far, we haven't seen such attacks though so I do not think we are gaining much by gating decoderFallback. For cloud gaming the gamepad API could be taken into account as well but I assume this is the same single-digit percentage solution as microphone. We should still take fullscreen (removed in #712) into account since it will prevent some fingerprint but maybe need different levels of granularity? Moving forward I'd rather go the opposite direction and have more information in encoderImplementation/decoderImplementation if getUserMedia et al give a strong signal. -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/730#issuecomment-1413730322 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 2 February 2023 13:15:33 UTC