W3C home > Mailing lists > Public > public-webrtc@w3.org > November 2013

Re: Why does screen sharing require a browser extension?

From: Martin Thomson <martin.thomson@gmail.com>
Date: Mon, 25 Nov 2013 12:10:44 -0800
Message-ID: <CABkgnnUoFJmNfnfnXTG0pqLzzUoZH5CbLqc8+Ss8=VWLm4u0bQ@mail.gmail.com>
To: cowwoc <cowwoc@bbs.darktech.org>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
On 25 November 2013 12:05, cowwoc <cowwoc@bbs.darktech.org> wrote:
> Please provide an example.


> [...] you can make this obvious by flashing
> the border of the area being captured. This is similar to webcams lighting
> up when they're on. There is no way a user would miss that visual queue.

That's what I thought, until I got some very clear information to the
contrary.  Skype places a red border around the screen when sharing. A
colorblind friend says to me: "so that's what that black border is".

> TLS alone would not, but TLS with Chrome App Store would. I'm saying that
> when a user hits a website that uses screen capturing, Chrome should check
> whether its TLS certificate has been approved in Chrome App store. If not,
> it should deny access. This gives you all the power of App Store (approval
> process, banning, etc) without the user needing to download an explicit
> plugin.

That model doesn't scale.
Received on Monday, 25 November 2013 20:11:13 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:36 UTC