Slashdot Mirror


Google Claims ChromeCast Local Streaming Only Broken Because of SDK Changes

sfcrazy writes "You may be familiar with the story that a ChromeCast update disabled the playback of local content, but Google has confirmed that it will allow every kind of content. Google Statement: 'We're excited to bring more content to Chromecast and would like to support all types of apps, including those for local content. It's still early days for the Google Cast SDK, which we just released in developer preview for early development and testing only. We expect that the SDK will continue to change before we launch out of developer preview, and want to provide a great experience for users and developers before making the SDK and additional apps more broadly available.' So no need to fear!"

15 of 82 comments (clear)

  1. Most unsurprising explanation is the most likely by jareth-0205 · · Score: 5, Insightful

    Much as everyone on here loved to crow about how Google were being evil and locking the device down, isn't this the far more likely reason? An undocumented API has changed. Now can we stop overreacting? Locking down this device isn't really their style.

  2. Lies, Lies, Lies. by Anonymous Coward · · Score: 4, Funny

    Google bad. Microsoft good. Get it right people!

  3. Re: Most unsurprising explanation is the most like by Anonymous Coward · · Score: 2, Insightful

    I suspected it was some mistake, but I still think they're evil.

  4. Re: Most unsurprising explanation is the most like by Anonymous Coward · · Score: 2, Informative

    I suspected it was some mistake, but I still think they're evil.

    Well, Edward Snowden pretty much confirmed that.

  5. We have always been at war with Google by Overzeetop · · Score: 5, Funny

    Microsoft has always been our ally.

    In other news, the chocolate rations will be increased this week, and there's been another winner in the lottery!

    --
    Is it just my observation, or are there way too many stupid people in the world?
  6. Re:Most unsurprising explanation is the most likel by wbr1 · · Score: 5, Insightful

    Much as everyone on here loved to crow about how Google were being evil and locking the device down, isn't this the far more likely reason? An undocumented API has changed. Now can we stop overreacting? Locking down this device isn't really their style.

    No, their style will be to cancel the device/services with some warning and litle explanation.

    --
    Silence is a state of mime.
  7. No shit by readingaccount · · Score: 5, Insightful

    Yeah, people fucking pointed this multiple times (here and elsewhere), but this rather important tidbit was lost among the noise that is misguided Internet rage.

    The Internet is extremely good at pushing things out of context or missing that little bit of info that completely changes the meaning of something. Like that image of Will Smith's family looking shocked over Miley Cyrus' act at the VMAs even though the picture-in-picture clearly showed it was Lady Gaga's act. But hey, people love to not pay attention to the details. It's faster that way.

  8. Re:Correction: It's all the same shit. by VortexCortex · · Score: 2

    The Internet is extremely good at pushing things out of context or missing that little bit of info that completely changes the meaning of something.

    You mistake strength for weakness. Imagine such levels of hue and cry and demanding of accountability in the mainstream populous -- Such is missing even over things that actually really matter.

    'Tis better to Sense Emphatically and waste a few cycles for self correction than Decide to dismiss threats by default and Act far too late. For the first time in your planet's history businesses can respond nearly instantly to customer demands. Just look at the Xbone, for a recent example. The point is that if Google had removed such feature they'd know it was a bad move, and going forward they know for sure not to strip that feature.

    Tell me, do you curse yourself for your immediately incorrect first impression before you've even considered a second look to discover something a bit closer to truth? Your indignation would be warranted if despite widespread evidence of the falsehood everyone still believed the initially perceived deceptions. Let they who hath never done the double take pass the first judgment.

    The Internet is not unlike your brain, except that you can see every part of this seething Cybernetic system as it fills with speculation prior to arriving at better understanding over time. Like humans the Internet reacts the most to what is perceived most threatening. What is most notable is not the time frames of the responses but the relative time frames of each cybernetic phase: Rapid repeated Sensing and even duplication of thoughts bubble up here in Slashdot's corner of the global mind; At a slower pace do the Decisions percolate as information is gathered; Yet more energy still is required to activate that synapse of the collective's Actions.

    As a cyberneticist I agree that you should have the sense to decide before you act; However, do not mistake Sensation for Decision or Action. The Internet isn't perfect, but I couldn't have designed it better myself.

  9. Re:Most unsurprising explanation is the most likel by DragonTHC · · Score: 4, Insightful

    But it is the style of those content providers whose apps leave messages like, "This content is not available on mobile"
    and "You cannot play content while a second display is enabled"

    And if you could cast any media class, then all of a sudden, those messages just wouldn't matter.
    And content providers would pull their apps claiming they no longer have control over where it's displayed.

    --
    They're using their grammar skills there.
  10. Re:Most unsurprising explanation is the most likel by swillden · · Score: 4, Informative

    Much as everyone on here loved to crow about how Google were being evil and locking the device down, isn't this the far more likely reason? An undocumented API has changed. Now can we stop overreacting? Locking down this device isn't really their style.

    No, their style will be to cancel the device/services with some warning and litle explanation.

    Cancel the system that's bringing YouTube (and its ads) into the living room? Seems very unlikely. In general, Google only discontinues services that aren't very successful (no, Reader wasn't very widely used, in spite of the heat generated by its fans). Successful services that are generating revenue are expanded. Successful services that aren't generating revenue are monetized. Unsuccessful services are discontinued if it looks like they're not going to become successful.

    The Chromecast seems to be very successful, and to have an obvious and successful revenue model in place (YouTube). I don't think it's going anywhere.

    (Disclaimer: I work for Google, but don't speak for Google.)

    --
    Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  11. The tech press by Simulant · · Score: 4, Insightful


    Unfortunately much of the tech press content consists of (paid?) product announcements, unsubstantiated rumour, and reviews of dubious quality.

    Google was up front about there being no Chromecast apps until the SDK was released, at the very beginning. This was never a story.

    1. Re:The tech press by RandomFactor · · Score: 2

      Unfortunately much of the tech press content consists of (paid?) product announcements, unsubstantiated rumour, and reviews of dubious quality.

      RODQs?

      I don't think they really exist.

      --
      --- Mercutio was right.
  12. Re:Most unsurprising explanation is the most likel by CastrTroy · · Score: 3, Interesting

    I'm still perplexed by the fact that they cancelled Reader. It had been around for 8 years. I'm sure it wasn't their most popular service, but then again, there probably didn't cost them much to run. The code didn't really need updating as nothing has changed in RSS in the past 5 years, and less users just means fewer server resources to handle the traffic. After they announced they were closing, 3 million people joined Feedly. That's not a very small number of people by any means. Personally, I went to Tiny-Tiny RSS, which I host on my own (shared host) server. That way I'm not reliant on some company deciding to shut down service.

    --

    Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
  13. Re:A distinction without a difference by Andy+Dodd · · Score: 4, Informative

    Except when your SDK is in beta and explicitly states that apps are not to be distributed without your approval until the SDK comes out of beta.

    In this case, I'm not sure if it's even an SDK change - it's a removal of an exploit that was used to allow a non-whitelisted unofficial app to behave like a whitelisted one.

    --
    retrorocket.o not found, launch anyway?
  14. Re:A distinction without a difference by squiggleslash · · Score: 2

    This is a preview SDK. They're not obliged at this point to retain compatability or to avoid breaking anything. In fact, they can quite legitimately throw the entire API out and replace it with something else.

    Anyone developing for Chromecast right now knows this, which meant the original article was dubious, if not intentionally deceptive. The author's program would have broken whether they'd written the app to stream from local hard drives or from Hulu.com.

    Ultimately anyone who wants to write their own streaming servers, be they for commercial services or for home hacking, continues to be able to do so, and in a few months they'll have a stable API to code against. Local streaming was never broken.

    --
    You are not alone. This is not normal. None of this is normal.