5 ms·

> it appears that amazon pulled both Apple TV and Chromecast because they didn't offer Amazon Prime. Amazon pulled Prime Video off of Chromecast themselves to

by foepys 9y ago

> it appears that amazon pulled both Apple TV and Chromecast because they didn't offer Amazon Prime. Amazon pulled Prime Video off of Chromecast themselves to sell the Fire TV (stick). Google did not remove Amazon's apps.

sashagim 9y ago
Google did pull YouTube app from Amazon devices. https://www.engadget.com/2017/12/05/google-blocking-youtube-on-amazon-echo-show-fire-tv/ https://www.engadget.com/2017/12/05/google-blocking-youtube-...
- Grazester 9y ago
  That was in retaliation to Amazon nonsense. Get your timelines straight.
  - yrro 9y ago
    rude
- deleted 9y ago
  [deleted]
kuschku 9y ago
Google first changed the Chromecast protocol a few times to prevent Amazon from using it. There’s a lot of fuckery there, and those of us that tried to build open source chromecast clones got fucked by Google as well. If you wish to argue against this, please offer me a way to implement the Chromecast protocol on a raspberry pi, reliably, without it constantly being broken by Google’s updates.
- foepys 9y ago
  > Google first changed the Chromecast protocol a few times to prevent Amazon from using it. How can they do that without also kicking out Netflix, Twitch, Hulu, etc.?
  - kuschku 9y ago
    Simply by the fact that none of these attempted to build a chromecast receiver? There were three groups working on such a receiver, Google with their Chromecast, Amazon wanted to support receiving chromecasts with the fire TV, and open source projects trying to receive chromecasts on the raspberry pi. Google changed that protocol a few times, only Google's products can receive chromecast streams today.
    - foepys 9y ago
      Oh, on the receiver side. So Amazon pulled Chromecast support from their apps because they couldn't get reliable Cast protocol support on their FireTV. Thank you for clarifying.
      - kuschku 9y ago
        Yes, that's basically it — they couldn't get reliable cast support to receive on the FireTV, and they couldn't reliably send from the Kindles due to Google's protocol changes. And that was already after Google's anticompetitive actions against the Kindle Fire devices.
- JshWright 9y ago
  I'd be interested to see a citation for your claim that Google intentionally changed the Cast protocol to prevent Amazon from using it. Your argument that Cast is hard on unsupported platforms is irrelevant. They are, by definition, unsupported, and Google is under no obligation to support them. Google provides an SDK that people are free to use on the platforms Google chooses to support. https://developers.google.com/cast/docs/developers https://developers.google.com/cast/docs/developers
  - kuschku 9y ago
    How do I receive a chromecast with that SDK, please? The point is not about sending, but about receiving, as was possible with miracast, and which would have made the fire stick a killer product (by having immediate compatibility with all Google apps' casting feature)
- mynameisvlad 9y ago
  Source? I couldn't find anything from a cursory search.
- infogulch 9y ago
  This is nonsense. You can cast with Plex from your home server of all things. I'm sure Amazon can figure out how to use an SDK.
  - kuschku 9y ago
    Plex can receice chromecasts, as Amazon was planning to with the Fire Stick, and as open source projects did?
- sshumaker 9y ago
  xoogler here, one of my teams implemented cast functionality in google photos. IIRC, this was definitely not the reason; the protocol was initially very limited and it was changed to make it more secure while also adding capabilities.
  - kuschku 9y ago
    That's the sending protocol (and I've seen those changes, I reversed that, too), but I meant the changes to the receiving protocol. There's a separate protocol app → Google and Google → Chromecast. Or at least, there was, after countless changes, I gave up attempting to build a raspberry pi with chromecast support. And of course, Chromecast replaced the dlna protocols and Miracast support in Android. I lost the ability to stream the screen on my nexus devices to open source receivers back then, because Google had to go proprietary.

by foepys 9y ago

sashagim 9y ago

Google did pull YouTube app from Amazon devices. https://www.engadget.com/2017/12/05/google-blocking-youtube-on-amazon-echo-show-fire-tv/ https://www.engadget.com/2017/12/05/google-blocking-youtube-...

Grazester 9y ago
That was in retaliation to Amazon nonsense. Get your timelines straight.
- yrro 9y ago
  rude
deleted 9y ago
[deleted]

kuschku 9y ago

Google first changed the Chromecast protocol a few times to prevent Amazon from using it. There’s a lot of fuckery there, and those of us that tried to build open source chromecast clones got fucked by Google as well. If you wish to argue against this, please offer me a way to implement the Chromecast protocol on a raspberry pi, reliably, without it constantly being broken by Google’s updates.

foepys 9y ago
> Google first changed the Chromecast protocol a few times to prevent Amazon from using it. How can they do that without also kicking out Netflix, Twitch, Hulu, etc.?
- kuschku 9y ago
  Simply by the fact that none of these attempted to build a chromecast receiver? There were three groups working on such a receiver, Google with their Chromecast, Amazon wanted to support receiving chromecasts with the fire TV, and open source projects trying to receive chromecasts on the raspberry pi. Google changed that protocol a few times, only Google's products can receive chromecast streams today.
  - foepys 9y ago
    Oh, on the receiver side. So Amazon pulled Chromecast support from their apps because they couldn't get reliable Cast protocol support on their FireTV. Thank you for clarifying.
    - kuschku 9y ago
      Yes, that's basically it — they couldn't get reliable cast support to receive on the FireTV, and they couldn't reliably send from the Kindles due to Google's protocol changes. And that was already after Google's anticompetitive actions against the Kindle Fire devices.
JshWright 9y ago
I'd be interested to see a citation for your claim that Google intentionally changed the Cast protocol to prevent Amazon from using it. Your argument that Cast is hard on unsupported platforms is irrelevant. They are, by definition, unsupported, and Google is under no obligation to support them. Google provides an SDK that people are free to use on the platforms Google chooses to support. https://developers.google.com/cast/docs/developers https://developers.google.com/cast/docs/developers
- kuschku 9y ago
  How do I receive a chromecast with that SDK, please? The point is not about sending, but about receiving, as was possible with miracast, and which would have made the fire stick a killer product (by having immediate compatibility with all Google apps' casting feature)
mynameisvlad 9y ago
Source? I couldn't find anything from a cursory search.
infogulch 9y ago
This is nonsense. You can cast with Plex from your home server of all things. I'm sure Amazon can figure out how to use an SDK.
- kuschku 9y ago
  Plex can receice chromecasts, as Amazon was planning to with the Fire Stick, and as open source projects did?
sshumaker 9y ago
xoogler here, one of my teams implemented cast functionality in google photos. IIRC, this was definitely not the reason; the protocol was initially very limited and it was changed to make it more secure while also adding capabilities.
- kuschku 9y ago
  That's the sending protocol (and I've seen those changes, I reversed that, too), but I meant the changes to the receiving protocol. There's a separate protocol app → Google and Google → Chromecast. Or at least, there was, after countless changes, I gave up attempting to build a raspberry pi with chromecast support. And of course, Chromecast replaced the dlna protocols and Miracast support in Android. I lost the ability to stream the screen on my nexus devices to open source receivers back then, because Google had to go proprietary.