> The only workaround is to login with a browser and copy the cookies from it to youtube-dl.

That's really easy to do with postman.

"Postman" seems like a pretty generic name.

Looking quickly online, maybe you're meaning this one?

https://www.postman.com

I'm pretty sure that is what they mean, yes. It is a nice tool. Lets you write HTTP(S) templates with parameters and whatnot, save them in groups, send them, handle the response, etc.

Funny. I initially read that as “The Postman” - kind of like “The Batman.”

And your response is regarding whether it should be referred to in the definite article.

>postman

It just works. Every time. It’s gotta be one of the most unappreciated tools out there right now.

Why not simply create a youtube-login command that does nothing but launch an electron instance that lets you login into youtube and then returns the cookie?

youtube-dl could then call that command to obtain the cookie.

There’s a good chance that behavior would result in a CAPTCHA.

The idea, I think, is that it literally launches a browser to let a human do the whole thing.

You can automate fetching Chrome’s cookies. This is generally very useful for scraping.

https://github.com/blackjack4494/yt-dlc is maintained by someone who responds to issues.