- From: Ami Fischman <fischman@chromium.org>
- Date: Mon, 7 Apr 2014 08:53:27 -0700
- To: Ian Hickson <ian@hixie.ch>
- Cc: WHATWG <whatwg@whatwg.org>, Philip Jägenstedt <philipj@opera.com>
Thanks Ian. I pinged public-media-capture about this and https://www.w3.org/Bugs/Public/show_bug.cgi?id=25245 is now tracking making that spec better specified. On Wed, Apr 2, 2014 at 10:52 AM, Ian Hickson <ian@hixie.ch> wrote: > On Mon, 3 Mar 2014, Ami Fischman wrote: > > > > Looks like we're back in business: > > > > Latest editor's draft: > > http://dev.w3.org/2011/webrtc/editor/getusermedia.html > > Thanks. > > As a user, this scares me a lot. Why isn't it up to me to control this? I > don't understand the security model here at all. I don't want random Web > pages to know that they can pipe audio to the remote speakers in my > bedroom from my laptop, but if we just expose all the audio output > devices, that's exactly what will be possible. > > Without a much clearer security model, I don't think it's a good idea to > add any APIs. > > -- > Ian Hickson U+1047E )\._.,--....,'``. fL > http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. > Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.' >
Received on Monday, 7 April 2014 16:09:34 UTC