- From: pes10k via GitHub <sysbot+gh@w3.org>
- Date: Fri, 05 May 2023 15:34:37 +0000
- To: public-webrtc-logs@w3.org
> It would seem highly unlikely that this issue is resolved independently from MC when MC is the discoverability API that this API depends on Understood, 100%. I only mean that if proposals / specs are revealing fingerprint-relevant inputs through MC, and MC is in a state that it doesn't prevent user-harming code from accessing MC-controlled data, then those proposals / specs are in practice revealing fingerprint-bits. That its going through the MC machinery doesn't change this specs contribution to the privacy risk. I see @samuelweiler opened https://github.com/w3c/media-capabilities/issues/176 a couple years ago. Would this be a good place to continue from, or do you think it'd be better to create a new issue? -- GitHub Notification of comment by pes10k Please view or discuss this issue at https://github.com/w3c/webrtc-svc/issues/92#issuecomment-1536434051 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 5 May 2023 15:34:38 UTC