3 ms·
Exactly. I think we're a long way from malice here, or even incompetence. That the ChromeCast has an SDK at all at this stage seems like a pleasant surprise;
by JoshTriplett 13y ago
Exactly. I think we're a long way from malice here, or even incompetence. That the ChromeCast has an SDK at all at this stage seems like a pleasant surprise; I feel certain the API will become more stable over time. If this were truly intended to be a closed device, unavailable for use except by specific media partners, why would there be a public SDK at all?
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.
- hershel 13y ago>> 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.