this post was submitted on 26 Dec 2023
136 points (83.0% liked)

Videos

14278 readers
201 users here now

For sharing interesting videos from around the Web!

Rules

  1. Videos only
  2. Follow the global Mastodon.World rules and the Lemmy.World TOS while posting and commenting.
  3. Don't be a jerk
  4. No advertising
  5. No political videos, post those to !politicalvideos@lemmy.world instead.
  6. Avoid clickbait titles. (Tip: Use dearrow)
  7. Link directly to the video source and not for example an embedded video in an article or tracked sharing link.
  8. Duplicate posts may be removed

Note: bans may apply to both !videos@lemmy.world and !politicalvideos@lemmy.world

founded 1 year ago
MODERATORS
Flutter@lemmy.world
Ghostalmedia@lemmy.world
can@sh.itjust.works
qaz@lemmy.world
qaz@lemmy.blahaj.zone
136
Tesla removes Disney+ after cursing out Disney CEO: why automakers removing carplay matters (www.youtube.com)
submitted 10 months ago by jimmydoreisalefty@lemmy.world to c/videos@lemmy.world
21 comments fedilink hide all child comments
 

cross-posted from: https://lemmy.dbzer0.com/post/10927107

Imagine a world where billionaires having petty arguments result in functionality being remotely removed from your $40,000 device...

TL;DW: Disney decided to cease advertising on X (formerly Twitter) and not long after, the Disney+ app was removed from many owners' Tesla vehicles. Users who have already used the app shouldn't be affected by this, however those who haven't will no longer have access to this functionality.

This video follows on the heels of GM announcing removal of CarPlay and Android Auto from their future vehicles, indirectly reducing the freedom granted to vehicle owners of what they can run on their infotainment system. Running apps that provide traffic warnings and additional functionality will be no more, likely paving the way for more unnecessary subscription addons - and even situations like this where functionality can just be taken away without warning

you are viewing a single comment's thread
view the rest of the comments
[–] BlueLineBae@midwest.social 9 points 10 months ago (1 children)

I just found out yesterday that you can't cast from a pixel to a fire stick. It was the first time I tried and I thought it was broken. Nope, just Google being petty.

[–] Sprucie@feddit.uk 11 points 10 months ago (2 children)

Genuine question, is it Google being petty or Amazon not supporting the protocol?

[–] ByteWelder@lemmy.ml 7 points 10 months ago (1 children)

It’s likely mostly Google and a bit of Amazon: Casting support requires Google Play Services installed on the device. Google Play Services is only allowed to be used (as in: allowed by Google) if the Android device also comes with many other Google apps. Amazon probably doesn’t want their device to become a Google-centric device. That’s likely the reason.

[–] DoomBot5@lemmy.world 2 points 10 months ago

Yeah, that's 100% on Amazon not wanting Google services on their devices.

[–] Tanoh@lemm.ee 1 points 10 months ago

The chromecast protocol is not open, it is just built into android so available to all apps (for now....) And only chrome on PC supports it (surprise!)