Hi,
The consensus opinion at WebRTC and MediaCapture seemed to be that
the ability to let an app say which of these 5 microphones do you
want? is more amenable to creating good apps than leaving this UI to
the browser chrome.
Seems to me that the privacy aspects (the fingerprinting
On Fri, Apr 11, 2014 at 6:23 PM, Edward O'Connor eocon...@apple.com wrote:
The consensus opinion at WebRTC and MediaCapture seemed to be that
the ability to let an app say which of these 5 microphones do you
want? is more amenable to creating good apps than leaving this UI to
the browser
On 04/02/2014 07:52 PM, Ian Hickson 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
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 i...@hixie.ch wrote:
On Mon, 3 Mar 2014, Ami Fischman wrote:
Looks like we're back
On Mon, 7 Apr 2014, Harald Alvestrand wrote:
On 04/02/2014 07:52 PM, Ian Hickson 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
As a user, this scares me a lot.
On 04/07/2014 06:20 PM, Ian Hickson wrote:
On Mon, 7 Apr 2014, Harald Alvestrand wrote:
On 04/02/2014 07:52 PM, Ian Hickson 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
As a
On Mon, 7 Apr 2014, Harald Alvestrand wrote:
The consensus opinion at WebRTC and MediaCapture seemed to be that the
ability to let an app say which of these 5 microphones do you want? is
more amenable to creating good apps than leaving this UI to the browser
chrome.
Seems to me that the
On Mon, Apr 07, 2014 at 07:28:45PM +0200, Harald Alvestrand wrote:
On 04/07/2014 06:20 PM, Ian Hickson wrote:
When I was first desigining the API for WebRTC (years ago, before it got
rather unceremoniously forked by the W3C), the security design I had come
up with was basically that the UA
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
Ian,
On Fri, Feb 7, 2014 at 4:55 PM, Ian Hickson i...@hixie.ch wrote:
Can you let us know when there's a URL that will permanently hold the
latest (including day-to-day updates) spec?
Looks like we're back in business:
Latest editor's draft:
On Wed, 18 Dec 2013, Ami Fischman wrote:
On Wed, Dec 18, 2013 at 8:38 PM, Ian Hickson i...@hixie.ch wrote:
On Tue, 17 Dec 2013, Ami Fischman wrote:
Recently https://www.w3.org/Bugs/Public/show_bug.cgi?id=23263
Navigator acquired the ability to enumerate media output devices (in
Ian,
The link you're looking at is currently being used to focus the WG's
attention on the Constrainable business, which is why everything else has
disappeared. This is temporary :)
See http://lists.w3.org/Archives/Public/public-webrtc/2014Feb/.html for
the haps, and the previous editor's
On Fri, 7 Feb 2014, Ami Fischman wrote:
The link you're looking at is currently being used to focus the WG's
attention on the Constrainable business, which is why everything else has
disappeared. This is temporary :)
See http://lists.w3.org/Archives/Public/public-webrtc/2014Feb/.html for
On Sun, Jan 12, 2014 at 8:47 PM, Philip Jägenstedt phil...@opera.comwrote:
[...]
Do you mean to make this per-origin as well? (It will require storing
that information per-origin forever, or until some invisible timeout.)
That seems about as restrictive as one could make it, but is the API
On Tue, Jan 14, 2014 at 5:51 AM, Ami Fischman fisch...@chromium.org wrote:
On Sun, Jan 12, 2014 at 8:47 PM, Philip Jägenstedt phil...@opera.com
wrote:
[...]
Do you mean to make this per-origin as well? (It will require storing
that information per-origin forever, or until some invisible
Hmm; I wasn't thinking in terms of per-device, only per-origin and
per-browser/machine.
Seems like a conversation for public-media-capture?
On Mon, Jan 13, 2014 at 3:30 PM, Philip Jägenstedt phil...@opera.comwrote:
On Tue, Jan 14, 2014 at 5:51 AM, Ami Fischman fisch...@chromium.org
wrote:
Perhaps :) I'm not on that list, but am fine leaving this to people
who have stronger opinions than me on the issue.
On Tue, Jan 14, 2014 at 6:36 AM, Ami Fischman fisch...@chromium.org wrote:
Hmm; I wasn't thinking in terms of per-device, only per-origin and
per-browser/machine.
Seems like a
On Thu, Dec 19, 2013 at 2:45 PM, Ami Fischman fisch...@chromium.org wrote:
On Wed, Dec 18, 2013 at 8:38 PM, Ian Hickson i...@hixie.ch wrote:
On Tue, 17 Dec 2013, Ami Fischman wrote:
Recently https://www.w3.org/Bugs/Public/show_bug.cgi?id=23263
Navigator acquired the ability to enumerate
On Tue, 17 Dec 2013, Ami Fischman wrote:
Recently https://www.w3.org/Bugs/Public/show_bug.cgi?id=23263
Navigator acquired the ability to enumerate media output devices (in
addition to input devices):
http://dev.w3.org/2011/webrtc/editor/getusermedia.html#enumerating-devices
What's the
19 matches
Mail list logo