Comment by jauntywundrkind

The extra irony here is that Netflix kind of lead the charge in this domain, worked with YouTube to build the DIAL protocol (Discovery and Launch, 2010). Which strongly resembles what emerged latter, Chromecast. From the DIAL protocol:

> For consumers, DIAL removes the pain of having to launch the required app on the first-screen [eg: tv] before interacting with it from their second-screen [eg: phone].

https://www.dial-multiscreen.org/

Growing up in the 90's, I was obsessed with ubiquitous computing, with an idea that there would be computers everywhere & we were going to need "the network is the computer" type thinking to let us make use of ambient screens, speakers, cameras, lights, etc. with Casting being ascendant and ragingly excellent, and Matter finally bringing some reason to IoT (but computer to computer notably weak) it's amazing to see some of that world.

I cannot for the life of me imagine why Netflix would be trying to stuff the genie back in the bottle now. We're ina user I would be pissed. I almost never touch my TV remote, and turning back the

I also want to mention that there is an open standard at the w3c, Open Screen Protocol, that's built by the Second Screen Working Group, to handle these flows in an open specified way. Matter has a Cast spec as well, but seems to only work with native apps that are already installed on devices, where-as DIAL (in many cases), Chromecast, and Open Screen Protocol all have modes where the target TV or speaker or whatnot open a given URL, so they can work with any* app without the 1st screen/tv needing explicit support. https://github.com/w3c/openscreenprotocol