Live data from Hacker News

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

github.com

121–130 of 646 posts

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

#121

Earlier quoted context omitted.

>outright blocking adblockers, which has no bearing on youtube's service The scale of data storage, transcoding compute, and bandwidth to run YouTube is staggering. I'm open to the idea that adblocking doesn't have much effect on a server just providing HTML and a few images, but YouTube's operating costs are (presumably, I haven't looked into it) staggering and absolutely incompatible with adblocking.

That’s fine, but YouTube has an obligation to make sure the ads they serve aren’t scams. They are falling short of that obligation.

Could you elaborate on why? It seems to me that YouTube's implicit contract with the user is "these people paid us to show you this advert", not "we vouch for the integrity and veracity of this advert". I obviously agree that it'd be nice if YouTube would put more effort into screening adverts, but I don't see why they're _obligated_ to. I'm happy to be corrected, though.

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

#122
post #34

Earlier quoted context omitted.

This is obviously not plausible. They're never going to shut off browser access on people's laptops. Watching YT at work is a major thing. I have to assume you're joking, but I honestly can't figure out what point you're even trying to make. Do it think it's surprising that an ad-supported site has anti-scraping/anti-downloading mechanisms? YouTube isn't a charity, it's not Wikipedia.

>Watching YT at work is a major thing. Where are these jobs where I can get paid to watch YouTube?

In small shops youtube is quite a handy source of information. I have to prototype and 3D print lots of stuff.

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

#123
post #36

I use yt-dlp (and back then youtube-dl) all the time to archive my liked videos. Started back in around 2010, now I have tens of thousands of videos saved. Storage is cheap and a huge percent of them are not available anymore on the site. I also save temporary videos removed after a time for example NHK honbasho sumo highlights which are only available for a month or so then they permanently remove them.

I was just lamenting last night that we can't watch some of Terutsuyoshi's amazing makuuchi bouts from about three(?) years ago. I wish I'd archived them.

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

#124

Earlier quoted context omitted.

Same here and my motivation was that some of my liked videos were randomly removed and it's pretty cool music I wanted to keep forever. I made another script that adds the video thumbnail as album art and somehow tries to put the proper ID3 tags, it works like 90% of the time which is good enough for me. Then I made another script that syncs it to my phone when I connect it. So now I have unlimited music in my phone…

> And yet, none of Google's 900k TOC genius engineers have thought of this as a feature ... Isn’t that the YouTube Music app?

No.

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

#125
post #84

Earlier quoted context omitted.

Do you ever go back and actually watch those videos? Whenever I start to journal, track, or just document something, after some time I notice again and again that most of the value has already been created the moment I finish working on a specific entry. Even with something seemingly very important like medical records. Maybe one exception I can think of are recordings of memories involving people close to you

I actually do! I have a perpetual VLC playlist which plays those videos randomly if I need some background noise.

I also have a ton of music videos from Youtube. Many of them are fan-made, many already unavailable I sometimes play them on a projector when I'm throwing a party.

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

#126
post #96

Earlier quoted context omitted.

Popular self-hosted solution: https://github.com/tubearchivist/tubearchivist

You people always make everything more complicated than necessary. yt-dlp -o '%(uploader)s/%(upload_date)s - %(title)s [%(id)s].%(ext)s' --cookies-from-browser chrome https://www.youtube.com/playlist?list=LL

That does none of the things tubearchivist does, among them:

- Subscribe to your favorite YouTube channels - Index and make videos searchable - Play videos - Keep track of viewed and unviewed videos

Not to mention having to ssh and copy paste URLs around, instead of visiting a page in my browser.

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

#127
post #36

I use yt-dlp (and back then youtube-dl) all the time to archive my liked videos. Started back in around 2010, now I have tens of thousands of videos saved. Storage is cheap and a huge percent of them are not available anymore on the site. I also save temporary videos removed after a time for example NHK honbasho sumo highlights which are only available for a month or so then they permanently remove them.

Do you ever go back and actually watch those videos? Whenever I start to journal, track, or just document something, after some time I notice again and again that most of the value has already been created the moment I finish working on a specific entry. Even with something seemingly very important like medical records. Maybe one exception I can think of are recordings of memories involving people close to you

I don’t think journaling is the same thing though as hoarding pics/videos. Even if you never go back and read through old hand written journals, just the physical process of writing has mental effects that pics/videos do not. There’s also a bit of therapeutic results from slowing down and putting thought to paper. So to me the only similarity is that you might not ever look at it again, that does not make them the same at all

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

#128
post #96

Earlier quoted context omitted.

Popular self-hosted solution: https://github.com/tubearchivist/tubearchivist

You people always make everything more complicated than necessary. yt-dlp -o '%(uploader)s/%(upload_date)s - %(title)s [%(id)s].%(ext)s' --cookies-from-browser chrome https://www.youtube.com/playlist?list=LL

> Once your YouTube video collection grows, it becomes hard to search and find a specific video. That's where Tube Archivist comes in: By indexing your video collection with metadata from YouTube, you can organize, search and enjoy your archived YouTube videos without hassle offline through a convenient web interface.

If you don't want the indexing and the pretty frontend that's fine, but there's a reason software like Plex is popular.

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

#129
Just one question. I see all these 3rd party clients solving the problem separately. Isn't it easier for everyone to build a unified decoder backend that exposes a stable and consistent interface for all the frontends? That way, it will get more attention and each modification will have to be done only once.

Since JS is the big issue here, the backend itself could be written in JS, TS or something else that compiles to WASM. That way, the decoder doesn't have to be split between two separate codebase. Deno also allows the bundle to be optionally compiled into a native executable that can run without having to install Deno separately.

Post reply on HN