- From: Mészáros Mihály via GitHub <sysbot+gh@w3.org>
- Date: Sun, 04 Nov 2018 19:10:02 +0000
- To: public-webrtc-logs@w3.org
FF implemented the variable, so in my understanding it partially implemented. See in FF `about:config` `media.peerconnection.default_iceservers`: [] I use it with in pair with `media.peerconnection.use_document_iceservers`: false to enforce to use my pre-configured trusted TURN servers instead of to use any application configured stun/turn servers/services, (that have unknown, random quality) Please consider that there are many uncertainty, with application configured TURN! - Such TURN servers are maybe (or maybe not) not fully trusted.. - my TURN server is not only trusted more, but it has an SLA, comparing to any unknown App service and or backend TURN relationship. It is also a benefit. - probably such TURN server has much higher latency, because it does not know my location, and it is no close enough to my location. - etc. So I think if someone is taking care about trusted TURN servers, privacy and about the TURN server selection control, then there are still reasons to have such browser side trusted default TURN Server. -- GitHub Notification of comment by misi Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2023#issuecomment-435696785 using your GitHub account
Received on Sunday, 4 November 2018 19:10:03 UTC