Live data from Hacker News

Yt-dlp: External JavaScript runtime now required for full YouTube support

github.com

591–600 of 646 posts

Re: Yt-dlp: External JavaScript runtime now required for full YouTube support

#591
post #421

Earlier quoted context omitted.

I use Firefox with uBlock and besides a couple of times where video start was delayed by a few seconds it has been working as well as before.

Google does A/B testing for anti ad blockers. Not only do I get slowdowns and some videos don't load at all at times, but I also get a notification that explains that the reason is using adblockers.

Here I am, totally given up on adblockers, and no way I’m paying for premium, but jesus christ the amount of ads I get, sometimes seems to be one every minute, making most videos unwatchable.

Though it’s mostly good for my addiction since it makes me use youtube less.

Re: Yt-dlp: External JavaScript runtime now required for full YouTube support

#593
post #478
post #421

Earlier quoted context omitted.

I use Firefox with uBlock and besides a couple of times where video start was delayed by a few seconds it has been working as well as before.

For the last two days I haven't been able to watch youtube videos on Firefox without disabling uBlock.

I disable youtube instead when this happens.

Re: Yt-dlp: External JavaScript runtime now required for full YouTube support

#594

Earlier quoted context omitted.

long press -> save image/video is perfectly supported on a phone, it's just content diffusion platform that arbitrarily restrict it.

No, it's also iOS that's arbitrarily restricting it. I opened a bare .webm directly in Safari and got nothing on long press and nothing in any of the control widgets to save it.

Likely not really what you want but you can make a shortcut that saves the file to Photos.

- Get URLs from (shortcut input) - Get contents from (URLs from previous step) - Save (contents of URL) to Photos

Set to accept URLs and appear in share sheet.

Re: Yt-dlp: External JavaScript runtime now required for full YouTube support

#595

From https://github.com/yt-dlp/yt-dlp/wiki/EJS it looks like deno is recommended for these reasons: > Notes > * Code is run with restricted permissions (e.g, no file system or network access) > * Supports downloading EJS script dependencies from npm (--remote-components ejs:npm).

For a long time, yt-dlp worked completely with Python. They implemented a lightweight JavaScript interpreter that could run basic scripts. But as the runtime requirements became more sophisticated it struggled to scale

As they put it, it was less of an interpreter, and more like 3 regexes in a trench coat.

Re: Yt-dlp: External JavaScript runtime now required for full YouTube support

#596

Earlier quoted context omitted.

Quick, everyone start sending unwanted junk mail to this guy's house, he'll pay you to stop!

Heaven forbid someone pay for an online service they use and enjoy.

I do, but not for services that treat their users (and content creators!) like YT does.

Re: Yt-dlp: External JavaScript runtime now required for full YouTube support

#597
post #186

Earlier quoted context omitted.

Glad to hear it’s faster now! YouTube barely works in a full-on browser these days, props to the team that keeps it accessible via a Python script!

I use YouTube in a browser (Brave) almost everyday. Works great for me.

Brave is a series scam company.

Re: Yt-dlp: External JavaScript runtime now required for full YouTube support

#598

Earlier quoted context omitted.

long press -> save image/video is perfectly supported on a phone, it's just content diffusion platform that arbitrarily restrict it.

You can't even make a screenshot if the app doesn't allow it. Phones are broken. (well, the OS on them is).

There's a double edged sword here. Not even talking about DRM.

I would love to be able, myself, decide if it's fine to capture a screen for an application but I'd also would love to protect me or my non-tech-savvy relatives from accidentally share sensitive info (e.g. banking) when screen casting.

In my opinion there should be a waiver buried deep in the settings that allows me to disable such protections with a grace period of a week or so. Grace period is crucial because scammers are able to make people do virtually anything under stress and hurrying.

Re: Yt-dlp: External JavaScript runtime now required for full YouTube support

#599
post #403

Earlier quoted context omitted.

> What environment are you using that: - Has access to Youtube - Can run Python code - Can’t run JS code They didn't say “can't run JS code”, but that from that location the solver could not be downloaded currently. It could be that it is an IPv6-only environment (IIRC youtube supports IPv6 but github does not), or just that all external sites must be assessed before whitelisted (I'm not sure why youtube would be but…

I've just hit the IPv6 problem. I routinely use yt-dlp -6 to cycle through my (basically infinite) set of IPv6 addresses. However when you do this, it tries the github EJS download over IPv6, which fails as github doesn't support IPv6 (because it's still the year 2000 over there). Actually I think this is kind of a yt-dlp bug, since it doesn't need to use IPv6 for the github download.

You can set up a 'socat' process to listen on a certain IPv6 address and relay traffic to GitHub, and add it to your hosts file, and you don't even need to break TLS since it's forwarding traffic unchanged

Re: Yt-dlp: External JavaScript runtime now required for full YouTube support

#600
post #164

Earlier quoted context omitted.

Back then, the focus was on optimising for the user. Now, however, companies prioritise their own interests over the user.

Indeed, the good old days when "optimizing for the user" got us... Windows 3.1 (release date April 6, 1992 , ref https://en.wikipedia.org/wiki/List_of_Microsoft_Windows_vers... ) or the first version of Linux - which I did not have the honor to use but I can imagine how user friendly it was considering what I ended up using couple of years later ( https://en.wikipedia.org/wiki/History_of_Linux ) /s

> first version of Linux - which I did not have the honor to use but I can imagine how user friendly it was

My first accounts were on Linux 1.x. It was glorious. Simple, sensible, and with manuals one command away. And it allowed you to just get things done. And there were tools. So many tools. 80's home computers and DOS crap and Macs that couldn't even open a file if it hadn't been tagged as the property of some application... Hells I would never have to be a part of any more. Except for work and school. But for personal computing, a brighter future was coming. In 30+ years since I've never had to step away.

Post reply on HN