Re: [webrtc-pc] Should we remove getDefaultIceServers?

I suppose we could address fingerprinting somewhat the way Chrome does for `deviceInfo.getCapabilities()`, which is to return `{}` unless gUM permission has been granted. But as @misi points out, this seems futile if `onicecandidate` exposes the same info.

I'm not super opposed to removing it. Its absence wouldn't prevent UAs from implementing pre-provisioned ICE servers as I understand it, just remove a convenience method for JS to find out early if this special routing will happen?

I agree this is orthogonal to and separate from [[[Configuration]]](http://w3c.github.io/webrtc-pc/#dfn-configuration).

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2023#issuecomment-438387237 using your GitHub account

Received on Tuesday, 13 November 2018 18:38:11 UTC