3 ms·
I think the sensible solution (and this goes for anything where there's security or privacy concern like WebGL) is to block it by default however to prompt the
by SG- 11y ago
I think the sensible solution (and this goes for anything where there's security or privacy concern like WebGL) is to block it by default however to prompt the user that the website wants to use WebRTC.
The user can then choose to allow it for one time or to whitelist or blacklist the site.
- the8472 11y ago> and this goes for anything where there's security or privacy concern It would force web developers to think much harder about feature detection and being non-intrusive about their usage. If someone gets nagged to enable webrtc just to read some news article it might actually cause some head scratching. cross domain cookies, local storage, video/audio playback (at least in background tabs), ... You could even make an argument for cross-domain javascript. Sometimes it's insane what crap shows up in µMatrix. More requests going to 3rd party sites than the actual content that I want to look at.
- rumdz 11y agoI really hope someone from Mozilla reads your comment. That sounds like a good solution to me too.