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

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 570666
To view parent comment, click here.
To read all comments associated with this story, please click here.
acobar
Member since:
2005-11-15

Private API justifications are only made for Google when Microsoft is on the receiving end.


We all know you love Microsoft but why should you use every opportunity to try to make it look good?

Did you read the article? Who said was anything private involved? Please, go back and read it again. The API is not ready and prone to be modified and there was a warning about it, not less, not more.

Perhaps, you have some information that you could share with us, in which case I am all ears.

Reply Parent Score: 2

Nelson Member since:
2005-11-29

So they're not private, they're just ...not public? I see.

The sad thing is that this is how you actually rationalize.

Reply Parent Score: 3

acobar Member since:
2005-11-15

The sad thing is that you say that you are a developer, because if you were you really would know what is the difference between a proper published SDK and one with "don't count on it to be stable" warning strings attached.

Reply Parent Score: 4

WorknMan Member since:
2005-11-13

Did you read the article? Who said was anything private involved? Please, go back and read it again. The API is not ready and prone to be modified and there was a warning about it, not less, not more.


It doesn't sound like they MODIFIED anything, in which case devs could just update their apps to compensate for the changes. Instead, it sounds to me like they REMOVED the functionality completely.

This reminds me of when Microsoft put HDCP into Windows Vista so it could play blu-rays; geeks around the world threw a shit fit, claiming that Microsoft should've stood up for rights of consumers and fought the content industry. And now that Google appears to be catering to their whims as well, suddenly it's okay? Although we don't have absolute proof that this is what is happening, it wouldn't surprise me in the least. Google is a publicly traded corporation, and doesn't give any more of a shit about you than MS or Apple do.

Personally, I feel now as I did then... if you want to blame someone for this kind of thing, then make sure it is aimed where it actually belongs - at the feet of the content industry.

Reply Parent Score: 3

Soulbender Member since:
2005-08-18

It doesn't sound like they MODIFIED anything, in which case devs could just update their apps to compensate for the changes. Instead, it sounds to me like they REMOVED the functionality completely.


Who cares? It was an unstable API and devs warned to use it at their own risk. The guy used something that he very well knew could break at any moment.
Cry me a river or better yet STFU.

Reply Parent Score: 3