Re: [mediacapture-record] Improvements to Privacy & Security Considerations (#196)

Am not gathering a security issue in the audio output example. The user or site can just attach the stream to an `HTMLMediaElement` or use Web Audio API to output the audio.

`WebRTC` exposes local IP addresses anyway https://www.ovpn.com/en/blog/webrtc-might-expose-your-ip-address-despite-vpn/, correct?

Input and output could be clarified tremendously. It is ironic that Chromium does not support capture of `Monitor of <device>` under the auspices that Media Capture and Streams specification only describes microphone input yet `setSinkId()` only works at Chrome, Chromium, which is using `getUserMedia()` to get permissions to output to speakers.

> The getUserMedia() spec does not mandate capturing audio output or showing a UI prompt as part of the device selection procedure.

https://bugs.chromium.org/p/chromium/issues/detail?id=1013881#c9, https://bugs.chromium.org/p/chromium/issues/detail?id=1032815.

So, we have Chromium stating essentially `getUserMedia()` is only for microphone input yet implementing output to speakers via `getUserMedia()`.

There appears to be a contradiction.

Either `getUserMedia()` needs to take the time to extending the scope of the specification - in clear language - or create a specification just to deal with selection of existing default or virtual devices - not just the _default_ microphone or camera that was the origin of the specification - which `getUserMedia()` has clearly "outgrown", however, is simultaneously attempting and does massage all sorts of extensions into `getUserMedia()` vicariously; perhaps in an attempt to remain within narrow confines of original charter yet still extend beyond the charter using the original charter as a reference?

-- 
GitHub Notification of comment by guest271314
Please view or discuss this issue at https://github.com/w3c/mediacapture-record/issues/196#issuecomment-653035130 using your GitHub account

Received on Thursday, 2 July 2020 14:21:41 UTC