In the absence of a statement from Google that the ChromeCast by design doesn't support the functionality used by this or other video streaming apps, I'd consider it premature to assume intentional breakage.
If you think about why did google enable local content streaming(but with bad/no sound - how hard is for google to get the bloody sound working before an important launch?) and whitelisting and used hdcp(secure content) on this device , google's strategy becomes clear:
They want to frighten content owners into submission. Let the content owners know that if they won't support chromecast , google will open it, and content companies will suffer.
On the other hand ,if content owners play ball, google will provide highly secure platform(and i wouldn't be surprised if tab casting will turned off - it's currently labeled experimental). This is the preferred road for Google, since there's more money that way.
In light of this potential strategy , there's probably malice in the last changes.
When Google's next hardware product comes out, can we stop thanking them and instead point out how they have a history of releasing products that give users no control over what runs on them?
Google has far more technical expertise than any ISP, so it stands to reason that they'll be using that to push down on users more than any other ISP has in the past. We may yet regret clamoring for Google Fiber to be everywhere.
The Nexus phones and tablets officially support flashing of custom ROMs.[1,2]
The Moto X will have an unlockable bootloader on carriers that allow it.[3]
Google gave a tutorial on how to root Glass (see the I/O talk "Voiding Your Warranty: Hacking Glass" [4]).
All Chromebooks have a developer mode that can be accessed using a hardware switch or key combination. See e.g. [5,6] for the Samsung ARM and Pixel Chromebooks.
Google even provides instructions for disassembling the Chromebooks ([5,6], at the bottom).
I don't think it's wise to ignore Google's history and extrapolate the future based exclusively on an SDK preview.
[EDIT: Downvoters, I would be curious to know your motivations.]
[1] http://en.wikipedia.org/wiki/Android_rooting
[2] http://android-developers.blogspot.ch/2010/12/its-not-rootin...
[3] https://plus.google.com/+PunitSoni/posts/e6oQdFnLGiv
[4] https://developers.google.com/events/io/sessions/332704837
[5] http://www.chromium.org/chromium-os/developer-information-fo...
[6] http://www.chromium.org/chromium-os/developer-information-fo...
> When Google's next hardware product comes out, can we
> stop thanking them and instead point out how they have a
> history of releasing products that give users no control
> over what runs on them?
Consumer hardware devices that Google has released so far are: Nexus {One,S,Galaxy,4,7,10,Q}, Glass, Chromebook Pixel, Chromecast.All of the Nexus devices (except for the abandoned-before-launch Q) have official support for flashing custom firmware. The Chromebook Pixel comes with "developer mode", which turns it into a standard unverified laptop. Glass can be unlocked, and Google employees demonstrated how to install Ubuntu on it at Google IO.
Other than the Chromecast, which devices do you feel restrict the user from controlling which code they run?
I'm just trying to encourage some honesty from an intellectual perspective -- why confuse ourselves when the outcome will be no different than the last? Why do we willfully continue to lock ourselves into an ecosystem, be it Google, Facebook, or Apple?
I don't understand this animosity towards Google, it's like every little change to the status quo triggers a hate-fest here on HN accompanied with wild accusations (only to be debunked soon after). They pushed a system update that broke undocumented APIs, they could be patching a security vulnerability for all you know, there is no need to commence spreading FUD about some other unrelated initiative.
Itβs not just Google, we like drama around here.
Personally I feel no such animosity towards Google, however any perceived hostility towards Google is purely coincidental -- my hatred is towards bait&switch and other parasitic corporate practices.
[1]http://en.wikipedia.org/wiki/Hanlon's_razorThe larger implication (not withstanding using documented or undocumented API) is violation of general assumption that Chromecast will be open and idie friendly than the Apple TV.
Even if the OP had used a documented API, the developer warning is clear that any and all API can be changed.
I thought Google made it clear from the beginning that this was intended to be a beta release until testing was done. Looking at Reddit I was shocked to see the number of people who think Google is trying to force them into buying from the Play Store.
The author posted code that suggests that the ability to stream arbitrary content has been intentionally disabled.
https://plus.google.com/110558071969009568835/posts/HbrpBbVG...
> Warning: The current Google Cast SDK is a preview SDK intended for development and testing purposes only, not for production apps. Google may change this SDK significantly prior to the official release of the Google Cast SDK. We strongly recommend that you do not publicly distribute any application using this preview SDK, as this preview SDK will no longer be supported after the official SDK is released (which will cause applications based only on the preview SDK to break).