3 ms·

Seems smart to me: https://www.recode.net/2017/10/12/16464132/google-target-retailers-amazon-walmart-assistant-alexa-home-echo-augmented-reality https://www.re

by geocar 9y ago

Seems smart to me: https://www.recode.net/2017/10/12/16464132/google-target-retailers-amazon-walmart-assistant-alexa-home-echo-augmented-reality https://www.recode.net/2017/10/12/16464132/google-target-ret... https://www.pcworld.com/article/2975731/software-games/youtube-gaming-launches-today-to-challenge-twitchs-livestreaming-dominance.html https://www.pcworld.com/article/2975731/software-games/youtu... https://www.theverge.com/2017/9/26/16371292/google-youtube-amazon-echo-show https://www.theverge.com/2017/9/26/16371292/google-youtube-a...

NicoJuicy 9y ago
Amazon was first to pull Google products. History here: https://www.androidpolice.com/2018/03/02/amazon-still-isnt-selling-chromecast-nearly-three-months-initial-announcement/ https://www.androidpolice.com/2018/03/02/amazon-still-isnt-s...
- kuschku 9y ago
  And Google was the first to modify the Chromecast protocol to prevent Amazon (and open source projects) from using it. This is why all the pi-cast projects died down, after all. Google constantly eradicating third-party implementations to hurt Amazon. That’s what started this fight. 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.
  - NicoJuicy 9y ago
    ? I still use CastNow https://github.com/xat/castnow https://github.com/xat/castnow It's core is chromecast-player https://github.com/thibauts/node-castv2-client https://github.com/thibauts/node-castv2-client V2 suggests there was 1 revision over time... The FAQ mentioned issues with Chromecast ultra and it seemed to be ipv6. Your reasoning ( Google changes a protocol to block Amazon), seems to be quite extreme.
    - kuschku 9y ago
      That's for casting to a chromecast — not receiving a chromecast.
      - NicoJuicy 9y ago
        It's protocol isn't opensource also. Yes, Google does opensource a lot. But that doesn't mean they should open source one of their "few" hardware projects.
        kuschku 9y ago
        No, but Google intentionally obfuscating their protocol when at that time several apps supported casting from the Kindle devices, and people worked on receiving streams, was annoying. And continuing to repeatedly change the receiving protocol until everyone stopped trying to reverse it was very anticompetitive. Amazon has spent years to get binary compatibility with almost every Google SDK and API, and Google has responded by continuing to obfuscating these even further, and preventing them entirely. And that's in addition to Google's illegal threats (EU antitrust case is almost over) to OEMs to prevent them from building Kindle devices. Amazon cloned an open source operating system, and used it. And attempted to achieve binary compatibility with Google's version. Google did all they could to prevent that from succeeding. It's a very twisted view to see Amazon as having started that fight. Personally, I dislike Google's proprietary Android versions as much as Amazon's, but it's been Google that's been fighting third party implementations all along the way here, and not Amazon. It was Google spending lots of effort to destroy open source implementations utterly and entirely.
        NicoJuicy 9y ago
        They didn't tried to fk with open-source, they where avoiding Amazon's "1-up". Amazon also didn't release their binary drivers and they weren't even successfull/popular They couldn't know that Amazon would fail miserably.. If I look at business tactics, that was a very mean move from Amazon and they earn everything that's coming ( the url's that were posted to "defend" them). PS. I suppose you have Prime?

by geocar 9y ago

NicoJuicy 9y ago

Amazon was first to pull Google products. History here: https://www.androidpolice.com/2018/03/02/amazon-still-isnt-selling-chromecast-nearly-three-months-initial-announcement/ https://www.androidpolice.com/2018/03/02/amazon-still-isnt-s...

kuschku 9y ago
And Google was the first to modify the Chromecast protocol to prevent Amazon (and open source projects) from using it. This is why all the pi-cast projects died down, after all. Google constantly eradicating third-party implementations to hurt Amazon. That’s what started this fight. 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.
- NicoJuicy 9y ago
  ? I still use CastNow https://github.com/xat/castnow https://github.com/xat/castnow It's core is chromecast-player https://github.com/thibauts/node-castv2-client https://github.com/thibauts/node-castv2-client V2 suggests there was 1 revision over time... The FAQ mentioned issues with Chromecast ultra and it seemed to be ipv6. Your reasoning ( Google changes a protocol to block Amazon), seems to be quite extreme.
  - kuschku 9y ago
    That's for casting to a chromecast — not receiving a chromecast.
    - NicoJuicy 9y ago
      It's protocol isn't opensource also. Yes, Google does opensource a lot. But that doesn't mean they should open source one of their "few" hardware projects.
      - kuschku 9y ago
        No, but Google intentionally obfuscating their protocol when at that time several apps supported casting from the Kindle devices, and people worked on receiving streams, was annoying. And continuing to repeatedly change the receiving protocol until everyone stopped trying to reverse it was very anticompetitive. Amazon has spent years to get binary compatibility with almost every Google SDK and API, and Google has responded by continuing to obfuscating these even further, and preventing them entirely. And that's in addition to Google's illegal threats (EU antitrust case is almost over) to OEMs to prevent them from building Kindle devices. Amazon cloned an open source operating system, and used it. And attempted to achieve binary compatibility with Google's version. Google did all they could to prevent that from succeeding. It's a very twisted view to see Amazon as having started that fight. Personally, I dislike Google's proprietary Android versions as much as Amazon's, but it's been Google that's been fighting third party implementations all along the way here, and not Amazon. It was Google spending lots of effort to destroy open source implementations utterly and entirely.
        NicoJuicy 9y ago
        They didn't tried to fk with open-source, they where avoiding Amazon's "1-up". Amazon also didn't release their binary drivers and they weren't even successfull/popular They couldn't know that Amazon would fail miserably.. If I look at business tactics, that was a very mean move from Amazon and they earn everything that's coming ( the url's that were posted to "defend" them). PS. I suppose you have Prime?