[Announcement] Upcoming new requirements for YouTube downloads · Issue #14404 · yt-dlp/yt-dlp
github.com
Beginning very soon, you'll need to have Deno (or another supported JavaScript runtime) installed to keep YouTube downloads working as normal. Why? Up until now, yt-dlp has been able to use its bui...

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.

  • carrylex@lemmy.worldEnglish
    747·
    1 day ago

    This post’s title is just completely incorrect and it looks like 700+ people didn’t even read the comments or the actual issue for one minute.

    Good job guys!

    • Liam Mayfair@lemmy.sdf.orgEnglish
      811·
      1 day ago

      I mean sure, OP’s title is somewhat clickbaity but it’s kind of true though. YouTube have broken compatibility with all existing unofficial clients. It’s good that yt-dlp are managing to work around it. I expect many other clients will follow suit but some of them may be unable to install additional dependencies and remain broken.

      Ultimately, what is the last straw that will break the camel’s back? Every client/consumer will have their breaking point.

      • carrylex@lemmy.worldEnglish
        414·
        1 day ago

        I mean sure, OP’s title is somewhat clickbaity but it’s kind of true though.

        Somewhat? Did you read the issue? Here’s a recap: yt-dlp will introduce a proper JS runtime in the future to better cope with YT’s JS. That’s it… that’s the issue.

        YouTube have broken compatibility with all existing unofficial clients.

        • sugar_in_your_tea@sh.itjust.worksEnglish
          12·
          1 day ago

          Yup, Grayjay still worked for me as of this morning, and that’s on a build that’s a month old. So either I’m not impacted by the A/B test, or it’s actually not a big deal.