- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 Jul 2019 02:07:03 +0000
- To: public-webrtc-logs@w3.org
> That would further entice developers in calling getUserMedia when they do not have host candidates (for good or bad reasons) since this will be a one-time call. It's already a one-time-call in Chrome today, so I think they're sufficiently enticed. 😉 By exposing it, users can at least see what is happening, and even revoke it with the **X** > Ideally, we would be able to identify legit uses of RTCPeerConnection. Not possible I think. We'll just end up boosting our successful connection numbers. > Or we would identify cases where leaking the host candidate is not a privacy issue. That's `getUserMedia`. Once gUM is granted, its fingerprint surface dwarfs 192.168.1.x. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/pull/2175#issuecomment-509878332 using your GitHub account
Received on Wednesday, 10 July 2019 02:07:05 UTC