360
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/piracy@lemmy.dbzer0.com
67 comments fedilink hide all child comments
 

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
[–] 1 point 1 year ago (1 child)

IDK really.

I don't dislike it in a "this is terrible technology and no one should be doing it" kind of a way. Just in a "I feel a bit icky about this" kind of way.

There must be privacy considerations right? Do I really want everyone to know what videos I'm watching?

Also, do I really want my client to be providing n upstream connections grinding away at my battery?

They've probably long since solved this I guess but in the early days firefox wasn't supported ?

I just... don't feel like this is the solution to the cost of delivering content.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 1 year ago

    I was incorrect, it uses HLS with P2P support:

    At the beginning of PeerTube, we only supported Web Video (previously known as "WebTorrent") streaming. Due to several limitations of the Web Video system, we had to add HLS with P2P support.

  • permalink
  • fedilink
  • source
  • parent