- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Jun 2022 14:38:46 +0000
- To: public-webrtc-logs@w3.org
Why is it impossible for both ends to collaborate to get the 'censor' effect? The end-user is the one browsing the web in a browser, and there's precedent for "undesired behaviors" not aligning between them and sites. E.g. popups and autoplay. Maybe an example would help: 1. A video conferencing site uses [Capture Handle Identity](https://w3c.github.io/mediacapture-handle/identity/index.html) to implement a communication channel and documents how to use it on the open web for any site to use (or a select few partners, or for a fee, doesn't matter). 2. This communication channel accepts any [CropTarget](https://w3c.github.io/mediacapture-region/#dom-croptarget). 3. All bank/credit card/shopping sites, say, quickly use this to defeat capture of any page with account or transaction information (makes perfect sense to them). 4. A user is in a one-to-one video call with their accountant/financial advisor/spouse whatever, attempting to go over expenses, and screen-sharing isn't working or they're told they're not allowed to share those pages. I purposely picked an example with some merit on the side of censoring being desirable to protect users from themselves and scammers. But we also know restraints can get in the way of user choice, which is why most browsers offer choices around popups and autoplay. That's what we're asking for here. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/63#issuecomment-1170067856 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 29 June 2022 14:38:48 UTC