Live data from Hacker News

Chromium is no longer supported for Chromecast

productforums.google.com

31–36 of 36 posts

Re: Chromium is no longer supported for Chromecast

#31

Earlier quoted context omitted.

What is that speculation based on? Why wouldn't Google want more browsers to be able to Cast? My opinion: I feel like this is a pro-user move with an unfortunate side effect of breaking/unsupporting an extension. If I just want to cast to my TV why should I have to hunt for an extension. I'd rather it "just work" via a context menu in the browser.

> What is that speculation based on? Why wouldn't Google want more browsers to be able to Cast? You have to remember how Google's business works. Ads on search is a massive part (majority?) of their revenue. The main reason for Chrome existing is to direct people to Google search via the address bar.

Chrome now uploads all browsing history associated with a Google login too, so it's a lot of extra valuable information for ads.

Re: Chromium is no longer supported for Chromecast

#32
post #16

Earlier quoted context omitted.

I think she may be a Google employee. Google's product / support forums are always like this, it's terrible.

Pretty sure she's not. If you hover over the icon on her profile picture, it says "Expert - Google Products". I can't find an example, but as I recall they have something like "Google Employee" that leaves it in no doubt when it's an employee response.

I've never seen that, but maybe I've never seen an answer by an actual google employee. :/

Re: Chromium is no longer supported for Chromecast

#33
post #24
post #10

People really have any expectation from Google devices? Even android which whole marketing is that it is "more open" only receives self-serving features. Btw, the access to chrome-cast is baked in the playStore service. So your app has to be compiled with full google play store tracking library to use it. ...i used to help maintain a version of fenec (firefox for android) that was build without chromecast support jus…

I owned a Nexus One before it was stolen. I waited for an upgrade to Android 4.0 but it never materialized.

LOL. I still have mine. On the desktop dock used as a MP3 player dedicated for the living room receiver.

it still runs android 2.3 (custom rom, obviously), which is the latest one that google released the closed source hardware drivers for.

and people still insist android is open source.

Re: Chromium is no longer supported for Chromecast

#34
post #22
post #10

People really have any expectation from Google devices? Even android which whole marketing is that it is "more open" only receives self-serving features. Btw, the access to chrome-cast is baked in the playStore service. So your app has to be compiled with full google play store tracking library to use it. ...i used to help maintain a version of fenec (firefox for android) that was build without chromecast support jus…

This is more about Google's desktop software (removing stuff from Chromium) than about Google's devices.

i mention an example on exactly that too...

Re: Chromium is no longer supported for Chromecast

#35
post #15

Earlier quoted context omitted.

Just remove their commit rights or fork the project.

Google runs the chromium project.

Looks like various parties have forked the codebase already.

https://github.com/Eloston/ungoogled-chromium

Re: Chromium is no longer supported for Chromecast

#36
post #7

The new cast feature in recent builds of chromium is not working for me. It fails to find any devices. Looking at the debug output it says: "media router not defined." After a bit of googling I found you can revert back to using the old cast extension by following these instructions: https://support.google.com/chromecast/answer/6349849?hl=en

Thank you! I don't know if this was up the last time I looked. There are flags to gate the feature in the source-- looks like the iOS build excludes it. Going to leave a build running overnight and give it a look in the morning. If tearing it out works, I'll post a patch to the Debian bug report. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833477

Disabling media router from source is apparently more involved than I thought it would be. Could have changed the default setting in a new user profile, but disabling it with a command-line argument is probably more like what I'm looking for here.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833477#44

Post reply on HN