- From: Rob Manson <roBman@mob-labs.com>
- Date: Tue, 16 Aug 2011 23:16:07 +1000
- To: Adam Bergkvist <adam.bergkvist@ericsson.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
- Cc: Rich Tibbett <richt@opera.com>
Hi Adam, > I think it will be tricky to have a MediaStream that's restricted to > local usage only, and still be useful. It wouldn't be sufficient to > prevent the stream from being added to a PeerConnection. E.g. we would > have to disable the MediaStreamRecorder as well as ability to render > the video in a canvas because once recorded clips or video frames have > been extracted from the stream it's quite hard to prevent them from > being transmitted somewhere. I.e. once the application can access the > data there's no reasonable way to guarantee local usage only. Then > there wouldn't be too many interesting usecases left. Yes...that is a very good point. I'll blame my flawed thinking on enthusiasm and a long day 8) Transparency around which streams a browser is currently sending could definitely help with this and could provide an advantage over native apps. For the AR use case this is a serious privacy issue. You're right we can't stop this issue...but I'd be interested in your thoughts on making it visible to the user. roBman
Received on Tuesday, 16 August 2011 13:16:36 UTC