978
Google just broke all third-party YT clients, including yt-dlp; a full JS implementation is now required. (github.com)
submitted 1 year ago* (last edited 1 year ago) by to c/technology@lemmy.world
276 comments fedilink hide all child comments
 

cross-posted from: https://lemmy.org/post/1872634

So, starting now, Google started mandating full JS for YT, effectively breaking all third-party clients and locking the site to their official client.

This reeks of DRM.

UPDATE: Installing Deno and installing yt-dlp through PyPi fixes yt-dlp but the very idea that Google is mandating JS to lock down YT in an attempt at pseudo-DRM is still crappy.

UPDATE #2: inv.nadeko.net is working again for now.

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 34 points 1 year ago* (5 children)

At least you own your content on those platforms, PeerTube especially if self-hosted, and not Google. If you self-host a PeerTube instance using local hardware, for example, no one can take it down on a whim but you.

With YT, Google can and will nuke your channel for any reason they see fit.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 5 points 1 year ago (4 children)

    You got a source to google owning your content if you upload to YouTube?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 17 points 1 year ago

    I'm assuming they mean de facto, not de jure.

    In reality YT can do whatever the hell they want. You aren't going to win from their entire team of ivy leage lawyers unless you're independently wealthy yourself.

  • permalink
  • fedilink
  • source
  • parent
  • [–] [S] 5 points 1 year ago (2 children)

    Lessee, recent censorship issues, the fact that you can get demonetized or straight-up struck down if you say something Google don't like, the fact that your channel can and will get taken down if Google don't like you....

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 8 points 1 year ago (1 child)

    That isn't Google owning your content though, just Google deciding what you can do with your content on their service.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] -4 points 1 year ago

    It is for all functional purposes the same thing.

    If you don't own and control it and someone else does and you have no power or ability to stop them

    You don't own it

    To try to draw a line here is pointless in anything but a debate of technicalities and reality doesn't care about those.

  • permalink
  • fedilink
  • source
  • parent