Seems its already in Arch's repositories, and seems to work, just add another flag to the invocation: yt-dlp --cookies-from-browser firefox --remote-components ejs:github -f "bestvideo[ext=mp4]+bestaudio[ext=m4a]/best[ext=mp4]/best" 'https://www.youtube.com/watch?v=XXX' It is downloading a solver at runtime, took maybe half a second in total, downloads are starting way faster than before it seems to me. [youtube] [js…
What environment are you using that: - Has access to Youtube - Can run Python code - Can’t run JS code If the concern is security, it sounds like the team went to great lengths to ensure the JS was sandboxed (as long as you’re using Deno). If you’re using some sort of weird OS or architecture that Deno/Node doesn’t support, you might consider QuickJS, which is written in pure C and should work on anything. (Although…
Yt-dlp: External JavaScript runtime now required for full YouTube support
601–610 of 646 posts
Re: Yt-dlp: External JavaScript runtime now required for full YouTube support
#602I remember when QuickTime came out in 1991 and it was obvious to everyone that video should be copied, pasted and saved like any arbitrary data. It's absolutely insane to me how bad the user experience is with video nowadays, even video that's not encumbered by DRM or complex JavaScript clients.
Experience with video is excellent for most people. All the complexity is hidden from the end user, unless you are trying to hack something. In the 1990s, streaming effectively didn't exist because people didn't have enough bandwidth (it was mostly dial-up), and there was very little legal offering, and the little that existed was terrible. Home video was limited too, as few people knew how to make video files suitab…
Re: Yt-dlp: External JavaScript runtime now required for full YouTube support
#603Earlier quoted context omitted.
It is likely you use Chrome or a browser that uses Blink for its engine and the OP uses a non-blink browser like Firefox. I use Firefox and I can cofirm since the last few months Youtube usability borders on usable
They've also started to be really aggressive against VPNs. I've tried Private Internet Access, Mulvad and AirVPN and often I have to cycle through 5-15(!) servers before YouTube stops saying "sign in to confirm you're not a bot". Discord has started to become absurdly aggressive with it too, to the point that they don't even let you load messages whilst logged in if you're on a VPN. It really makes me feel like there…
Re: Yt-dlp: External JavaScript runtime now required for full YouTube support
#604Re: Yt-dlp: External JavaScript runtime now required for full YouTube support
#605Earlier quoted context omitted.
They've also started to be really aggressive against VPNs. I've tried Private Internet Access, Mulvad and AirVPN and often I have to cycle through 5-15(!) servers before YouTube stops saying "sign in to confirm you're not a bot". Discord has started to become absurdly aggressive with it too, to the point that they don't even let you load messages whilst logged in if you're on a VPN. It really makes me feel like there…
What's so clean about YouTube, Discord, X etc? It's full of low quality content, scams, malware, influencers, advertisers and other scum and villainy.
There are allegations going around that e.g. some platforms are lax on child protection because some high up executives are pedophiles. But I'd still place those platforms in the "heavily sanitised" bucket if they're heavily restricting everything else. Those platforms just have a slightly different definition of "clean" than most of us.
Re: Yt-dlp: External JavaScript runtime now required for full YouTube support
#606Earlier quoted context omitted.
It's fine for this project since google is probably not in the business of triggering exploits in yt-dlp users but please do not use deno sandboxing as a your main security measure to execute untrusted code . Runtime-level sandboxing is always very weak. Relying on OS-level sandboxing or VMs (firecracker & co) is the right way for this.
> It's fine for this project since google is probably not in the business of triggering exploits in yt-dlp yt-dlp supports a huge list of websites other than youtube
From the September announcement:
> The JavaScript runtime requirement will only apply to downloading from YouTube. yt-dlp can still be used without it on the other ~thousand sites it supports
Re: Yt-dlp: External JavaScript runtime now required for full YouTube support
#607Earlier quoted context omitted.
It's fine for this project since google is probably not in the business of triggering exploits in yt-dlp users but please do not use deno sandboxing as a your main security measure to execute untrusted code . Runtime-level sandboxing is always very weak. Relying on OS-level sandboxing or VMs (firecracker & co) is the right way for this.
> Runtime-level sandboxing is always very weak. Relying on OS-level sandboxing or VMs (firecracker & co) is the right way for this. ... Isn't the web browser's sandboxing runtime-level?
Re: Yt-dlp: External JavaScript runtime now required for full YouTube support
#608Earlier quoted context omitted.
From the preservation point of view yes. But realistically, it's been the norm throughout human history that irrelevant culture simply gets removed.
So is much of relevant culture, it's not like there is a magic preservation wand that sorts by relevance before removal
Re: Yt-dlp: External JavaScript runtime now required for full YouTube support
#609Earlier quoted context omitted.
100%. Web Credentials + Digital ID + age verification will all be handled with Secure Attestation backing it. Cloudflare will have a checkbox for site admins... [X] Require Age Verification... and that's it. Boom. Your site is "safe" from accidentally allowing kids in. ...of course, free speech and anonymity die with this, but why would that be a problem? You don't want to say anything the current or potential future…
Free speech doesn't die with this. Host your own site.
Re: Yt-dlp: External JavaScript runtime now required for full YouTube support
#610Earlier quoted context omitted.
Damn that's crazy, nothing a simple static redirector in a single js line can't fix. Overall cost to implement this shit : likely thousands hundred k Bypass cost : literally 0 It really is just a way for them to say "we can fuck with you as much as we want and you won't do shit cause what you gonna do ? go somewhere else ?"
In killing the cable company, YouTube has become the cable company themselves.