Re: What would you like to see in WebRTC next? A low-level API? from Stefan Håkansson LK on 2018-01-29 (public-webrtc@w3.org from January 2018)

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Mon, 29 Jan 2018 19:38:48 +0000
To: Cullen Jennings <fluffy@iii.ca>, Harald Alvestrand <harald@alvestrand.no>
CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <HE1PR07MB3418BD4820EC2C0C95A35105C9E50@HE1PR07MB3418.eurprd07.prod.outlook.com>

On 29/01/18 17:00, Cullen Jennings wrote:
> 3. The browser runs the codec in a context where it has no access to anything that would allow it to exfiltrate the raw data or do other bad things but the browser can call the API to encode and decode stuff

If I understand correctly, an AudioWorklet can already be used to access 
and process raw audio (and can take an audio track as input and generate 
an audio output track). I don't know if you can do bad things though ;)

And can't you do similar things for video with a video element, a canvas 
and "Capture from DOM elements"?

Received on Monday, 29 January 2018 19:39:24 UTC