> There is one thing that developers like more than building things — and that is breaking things built by other people. Haha. This is not as universal as the author thinks. Every time I need to reverse-engineer something obscured on purpose, I wish we could just get along. Every time I have to reverse-engineer something obscured by accident, I call it debugging. But even if I solve the puzzle, it's like solving cros…
Reverse-Engineering YouTube: Revisited
11–20 of 43 posts
Re: Reverse-Engineering YouTube: Revisited
#12Re: Reverse-Engineering YouTube: Revisited
#13Its too bad such an important resource (youtube) has a secret API - that changes all the time.
Why? YouTube has a proper public API, that doesn't change all the time.
Re: Reverse-Engineering YouTube: Revisited
#14I don’t particularly have anything to add about the article. But I do enjoy using your desktop youtube downloader , as well as couple of your .net libraries. Especially CliWrap. Amazing work. Just wanted to say thanks!
Re: Reverse-Engineering YouTube: Revisited
#15Does anyone know if YouTube runs Ffmpeg internally?
These days they use special hardware accelerators: https://gwern.net/doc/cs/hardware/2021-ranganathan.pdf
Re: Reverse-Engineering YouTube: Revisited
#16Unfortunately mpv and ffmpeg do not currently have mature DASH support and cannot benefit from fast seeks: https://github.com/mpv-player/mpv/issues/7033 (didn't look deeply)
Re: Reverse-Engineering YouTube: Revisited
#17Ive said it before on GitHub, I dont think `TVHTML5_SIMPLY_EMBEDDED_PLAYER` is the great solution everyone thinks it is. Yeah, you can get the age-restricted videos anonymously. However you can also get those videos by logging in, which the author doesn't mention: POST /youtubei/v1/player HTTP/1.1 Host: www.youtube.com Authorization: Bearer ya29.a0AVvZVsqRwNWFI3R0MSxnugyNlxbqIOXcwXkeA6NMOcpv_... { "contentCheckOk": t…
> 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?
Re: Reverse-Engineering YouTube: Revisited
#18Ive said it before on GitHub, I dont think `TVHTML5_SIMPLY_EMBEDDED_PLAYER` is the great solution everyone thinks it is. Yeah, you can get the age-restricted videos anonymously. However you can also get those videos by logging in, which the author doesn't mention: POST /youtubei/v1/player HTTP/1.1 Host: www.youtube.com Authorization: Bearer ya29.a0AVvZVsqRwNWFI3R0MSxnugyNlxbqIOXcwXkeA6NMOcpv_... { "contentCheckOk": t…
Re: Reverse-Engineering YouTube: Revisited
#19Re: Reverse-Engineering YouTube: Revisited
#20> There is one thing that developers like more than building things — and that is breaking things built by other people. Haha. This is not as universal as the author thinks. Every time I need to reverse-engineer something obscured on purpose, I wish we could just get along. Every time I have to reverse-engineer something obscured by accident, I call it debugging. But even if I solve the puzzle, it's like solving cros…
You wouldn't need to tear down barriers if the people that built them thought the same in the first place. Nonetheless, keep up that attitude.