dirkf

The site is a JS application with no meaningful data in the pages that yt-dl would see. An implementer will have to analyze the web traffic generated by the application...

Indeed, you've done the analysis that I mentioned and contrary to expectation this is rather straightforward. In case someone wants to do the rest of the job: linked JSON, pretty-printed...

Good luck!

See https://github.com/yt-dlp/yt-dlp/issues/1591.

The original PR, mentioned in the link, is apparently invalid, in that it no longer matches what the site does. It does contain a Blowfish crypto module that might still...

As above, the question is whether PR #22074 still works. Easiest is if you can get your repo unblocked (quote #27013), test the branch and commit any necessary changes to...

This patch back-ports the Android embed client work-around from yt-dlp to achieve the same result: ``` --- old/youtube-dl/youtube_dl/extractor/youtube.py +++ new/youtube-dl/youtube_dl/extractor/youtube.py @@ -283,15 +283,18 @@ _YT_INITIAL_PLAYER_RESPONSE_RE = r'ytInitialPlayerResponse\s*=\s*({.+?})\s*;' _YT_INITIAL_BOUNDARY_RE = r'(?:var\s+meta|

> That ID doesnt match that description. What happens when you try to remember what you did yesterday instead of looking it up!

Try the linked PR #31043 which worked when I last tested it. There is a separate issue #31164 with YT today but it doesn't affect this.

Well, check the dates for yourself (yes). The PR fixes the work-around as much as it can be. I am not a YT expert (indeed I rarely access YT content...