Re:Chromecast update breaks AllCast
by hershel on Monday August 26, 2013 @01:43PM
(#6278581)
>> I think we're a long way from malice here
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.
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.