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
[–] 3 points 1 year ago* (5 children)

ATSC 3 ? Never heard of that, but I'm curious.

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

    New broadcast standard which if implemented as intended, will use Widevine DRM to encrypt/decrypt streams, and require a web connection to view previously free OTA broadcasts, also that DRM will limit what you can do with it, as Rossmann puts it early on in his 'this is why I show these things in my vids' vid. https://peertube.gravitywell.xyz/videos/watch/61332f1b-9a15-46b6-8a97-c4e378fbce72

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •