3 ms·

Assuming they drop support for the Chromecast add-on, doesn't this effectively eliminate the ability for other browsers that can use chrome extensions to cast t

Assuming they drop support for the Chromecast add-on, doesn't this effectively eliminate the ability for other browsers that can use chrome extensions to cast to a Chromecast? (e.g., Opera, Vivaldi, maybe Chromium)?

pavanky 10y ago
That is only going to be a problem if they do not upstream the changes to Chromium.
- andybak 10y ago
  That's actually a very important question. Is Google opening up casting in the widest sense to 3rd party clients? I know there was some push in this direction when it was launched ( https://en.wikipedia.org/wiki/Discovery_and_Launch https://en.wikipedia.org/wiki/Discovery_and_Launch ) but I seem to recall hearing that there is now more to Google Cast than DIAL. Does anyone know how interoperable this all is?
  - vbernat 10y ago
    DIAL/SSDP is not used anymore (except for legacy apps, like the Youtube one). Now, this is mDNS (good) and proprietary protobuf protocol. There is no documentation for this but several people have reversed-engineered the stuff from the source code of Chromium and the extension to get third-party client (third-party Chromecast is not possible since there is a signature mechanism for clients to check). I have done such an implementation here: https://github.com/vincentbernat/nodecastor https://github.com/vincentbernat/nodecastor (but not really maintained).
    - andybak 10y ago
      That's troubling. Has anyone got any sense about whether interoperability is merely neglected or whether there's strategic reasons for its abandonment (either from Google itself or via pressure from partners with 'premium content')
    - voltagex_ 10y ago
      Shit, I was going to write a DIAL receiver for Windows so I could "share" a YouTube video from my phone and have it start playing immediately. Hopefully youtube.com/tv still works.

3 ms·

Assuming they drop support for the Chromecast add-on, doesn't this effectively eliminate the ability for other browsers that can use chrome extensions to cast t

by joemccall86 10y ago

pavanky 10y ago
That is only going to be a problem if they do not upstream the changes to Chromium.
- andybak 10y ago
  That's actually a very important question. Is Google opening up casting in the widest sense to 3rd party clients? I know there was some push in this direction when it was launched ( https://en.wikipedia.org/wiki/Discovery_and_Launch https://en.wikipedia.org/wiki/Discovery_and_Launch ) but I seem to recall hearing that there is now more to Google Cast than DIAL. Does anyone know how interoperable this all is?
  - vbernat 10y ago
    DIAL/SSDP is not used anymore (except for legacy apps, like the Youtube one). Now, this is mDNS (good) and proprietary protobuf protocol. There is no documentation for this but several people have reversed-engineered the stuff from the source code of Chromium and the extension to get third-party client (third-party Chromecast is not possible since there is a signature mechanism for clients to check). I have done such an implementation here: https://github.com/vincentbernat/nodecastor https://github.com/vincentbernat/nodecastor (but not really maintained).
    - andybak 10y ago
      That's troubling. Has anyone got any sense about whether interoperability is merely neglected or whether there's strategic reasons for its abandonment (either from Google itself or via pressure from partners with 'premium content')
    - voltagex_ 10y ago
      Shit, I was going to write a DIAL receiver for Windows so I could "share" a YouTube video from my phone and have it start playing immediately. Hopefully youtube.com/tv still works.