Linked by Thom Holwerda on Mon 26th Aug 2013 16:24 UTC

Update: the functionality used by the application was reverse engineered and Google stated that it may change. Google has released a statement which acknowledges that playing local content will come back to ChromeCast once the API has stabilised. Storm in a teacup, apparently.

Heads up. Google's latest Chromecast update intentionally breaks AllCast. They disabled 'video_playback' support from the ChromeCast application.

Given that this is the second time they've purposefully removed/disabled[1] the ability to play media from external sources, it confirms some of my suspicions that I have had about the Chromecast developer program: the policy seems to be a heavy handed approach, where only approved content will be played through the device.

A company intentionally disabling cool stuff? Surely you jest.

Thread beginning with comment 570697
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

THANK YOU! I logged in just to make this exact comment.

There is zero evidence google did anything intentional here. The guy reverse engineered an internal API and then his app broke on a subsequent update. OMG, boo f-ing hoo! People angry about this obviously know nothing about what valid expectations are for the stability of an internal API you figure out on your own. As a developer I will say this: Get over it, you don't understand the situation.

90% chance they are still iterating on the API and that part just isn't ready yet (and therefore it evolved and broke dude's app..)

Having said all that, we have no idea what google is doing. Maybe it *was* intentional. Even so, they might be contractually obligated to prevent access to such APIs because of contracts they've entered into with TV manufacturers, content providers, etc.

I think part of what people are freaking out over is the definition of what this device *is*. Right now it is a device for streaming youtube and chrome tabs. We all know it will be much more but what? If it is google's plan for it to be an open streaming device, then that API will emerge when it is ready and all this boo-hoo-ing will stop. But understand that will imply limitations on what sort of content they will be able to provide via partnerships because some content partners won't like it.

However if it is their plan to make it replace your cable TV box, then there will lots of cool integrations with big name content partners but they will almost certainly lock out some 3rd party stuff that gives users too much freedom.

Either way, that is fine. It is just a product so get over it.

Reply Parent Score: 3

Bill Shooter of Bul Member since:

Would it be too much to ask Google to define what it was before I bought it?

I was planning on buying it based off of what devs were saying was possible with the SDK. But it now looks like it would be a better idea to wait until the SDK is released before jumping the gun.

Reply Parent Score: 2

Vanders Member since:

Would it be too much to ask Google to define what it was before I bought it?

If you asked and they said "No, we're not ready yet" but you still went ahead and bought one anyway, who's fault would that be?

This isn't another PS3 "Other OS" moment no matter how much some people want it to be.

Reply Parent Score: 2