4 ms·
After working with WebRTC and realizing its potential I immediately disabled it in my webbrowser. One fear was to become a peer in a (copyright infringing) p2p
by jackewiehose 7y ago
After working with WebRTC and realizing its potential I immediately disabled it in my webbrowser.
One fear was to become a peer in a (copyright infringing) p2p-network, unknowingly just by visiting a random website.
WebRTC can be very useful but I think browsers should ask for special permissions like they do for camera access etc.
- dmos62 7y agoThat's a good idea. Already many privacy protecting extensions disable it, because it can leak private information [0]. [0] https://github.com/gorhill/uBlock/wiki/Prevent-WebRTC-from-leaking-local-IP-address https://github.com/gorhill/uBlock/wiki/Prevent-WebRTC-from-l...
- jackewiehose 7y agoIf you downvote this it would be nice to know where I am wrong.
- cerberusss 7y agoIt's ridiculous that this isn't turned off by default. Here's a Firefox extension which does exactly that: https://addons.mozilla.org/en-US/firefox/addon/happy-bonobo-disable-webrtc/ https://addons.mozilla.org/en-US/firefox/addon/happy-bonobo-...
- miles 7y agoWhy risk installing an add-on when you can achieve the same end just by using about:config to set media.peerconnection.enabled to false?
- nerdponx 7y agoWhy hide basic configuration in an under-documented use-at-your-own-risk settings editor?
- cerberusss 7y agoMy thought was, that the extension is very easy to switch on/off. However since installing, I have never wanted WebRTC to be on...