Re: [mediacapture-region] Should we support strings in addition or in lieu of opaque identifiers? (#46)

> look at how likely the risk is to occur.

Video conferencing is big in our world, but it's not so big that Wikipedia and other non-video-conferencing sites would worry that they must comply with arbitrary demands for fear of tab-sharing not working too well. 

Let's run a thought experiment. You and I together quit our current jobs and start a new video-conferencing application. We're tremendously successful and gain 125% of the market - we're just that good. Now we write an email to Wikipedia and explain to them that, unless they start sending us CropTargets whenever they do any page-load, we will penalize them! They write back - "penlize how?" To which we respond - "we will annoy our OWN users with anti-Wikipedia messages whenever they try to tab-share Wikipedia pages!! (Not if they share a windows or the entire screen, though. We have technical limitations and decided not to use watermarking to circumvent them; we'll only harm your tab-sharing game.)"

What do you think happens next? I think we might give someone in Wikipedia the laugh of their life. But I don't think they'll bother emailing us back. After all - why should they care? What percentage of Wikipedia page loads culminate to a user trying to tab-share that page?

Also - how long will our users stick with us if we do follow-through on our threat?

To summarize - I don't think this is a real risk.

> Can you outline a scenario where lack of transmissibility would prevent cooperation between cross-origin services in the same user agent session ?

I can outline a scenario and simultaneously give a shoutout to the greatest musical genius of our generation.

<img width="1687" alt="image" src="https://user-images.githubusercontent.com/22117736/176559649-3a4d08df-1475-4dc0-8719-194ec260df1c.png">

Meet captures YouTube running in another tab. YouTube wants to send over a CropTarget focusing on the video and cropping away the list of suggested next videos. Meet could then show the user controls to crop to the video or share the entire tab. [*] The **benefit** here is that the user could easily hide their playlist, which they might find embarrassing. But how can youtube.com send a message to meet.google.com? Enter shared cloud infrastructure...

--
[*] Jan-Ivar has previously [asked](https://github.com/w3c/mediacapture-region/issues/63#issuecomment-1170488308) about Meet's **plans** for user-facing crop-controls. To clarify, this is a hypothetical scenario I have concocted in the last minute. It's not an announcement of future plans.

-- 
GitHub Notification of comment by eladalon1983
Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/46#issuecomment-1170580022 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 23:10:55 UTC