Re:Reverse-Engineering YouTube: Revisited
by philipphutterer on Saturday February 04, 2023 @12:47PM
(#34656374)
> However you can also get those videos by logging in, which the author doesn't mention.
> Also not mentioned in the article is that you can actually take the throttled URLs as is, and download pieces concurrently for a pretty good result.
The author mentioned both, the login option as well as the chunking mechanism. Sorry, but did you actually read the blog post?
they mention cookies. that not the correct method for authenticating to the API, OAuth is.
Re:Reverse-Engineering YouTube: Revisited
by tyrrrz on Saturday February 04, 2023 @12:49PM
(#34656396)
If you can afford to always be logged in, then sure, but it's not always an option. Especially if you need a general solution.
who said anything about always? you log in as needed. most videos are open.
Re:Reverse-Engineering YouTube: Revisited
by tyrrrz on Sunday February 05, 2023 @01:23AM
(#34662489)
I mean, if you're not the sole user of the tool, you can't guarantee that everyone can log in (or would want to)
I doubt anyone WANTS to log in. 90% of videos are open. Yes, logging in is a burden, but coding wise its literally one extra line in the HTTP request. I think thats a fair tradeoff compared to parsing arbitrary JavaScript.
each person can weigh the pros and cons and make their own decision, but I dont think its as black and white that TVHTML5_SIMPLY_EMBEDDED_PLAYER is the best option, and the article doesn't even discuss OAuth, so I dont think its presenting a balanced take on the different approaches.
http://2a.pages.dev/mech