Yingwu

In summary, YouTube is A/B testing a change where specific clients receive only DRM-locked video streams. This is notable because yt-dlp impersonates those clients during normal operation. Since yt-dlp won't support decrypting DRM-locked videos, this change breaks yt-dlp's ability to download any videos.

To respond to your specific questions:

• innertube is the name for private YouTube APIs. (Here's a library that talks to innertube https://github.com/tombulled/innertube/, although yt-dlp has its own separate client code.) These APIs are intended for consumption by the various types of YouTube client software.

• The "tv" client is one of the types of client (see other examples here: https://github.com/tombulled/innertube/blob/main/innertube/c...)

• TVHTML5 is the specific client (as opposed to e.g. TVLITE or TVANDROID)... presumably different TVs run different specific TV clients, with consumption of different specific TV APIs.

• When yt-dlp downloads a video, it roughly performs this sequence of steps: pretend to be one of the types of clients supported by innertube; download the top-level video object; parse out the list of possible formats. These formats are like "MP4, 1080p, with AAC audio" or "Ogg, audio only". (The original issue report shows a better example in the verbose output dump.) By default, yt-dlp just grabs the best quality audio and best quality video stream, downloads them, and muxes them together into a single file, but you can configure this behavior. DRM formats are formats that are protected by (presumably) Widevine: https://en.wikipedia.org/wiki/Widevine, the decryption of which yt-dlp has stated will not be supported.

• Available means they're an option for our yt-dlp client to download. Videos don't necessarily have all formats for all clients; for instance, a video might not have a 4K option, because it was never uploaded in 4K. Or it might have a 4K upload, but YouTube won't show 4K options to a client that doesn't support 4K decoding.

• In this case, it means this specific internal client type can't download the video, because when yt-dlp reaches out, it gets ONLY formats that are DRM-locked. This is of note, I think, because the TV client is a way to get high-quality video from the YouTube API without having to pass it a valid YouTube login token (further down the issue, the reporter says providing a token allows the "web" innertube client to work).

Thank you for this. I posted another guide to my new community [email protected], but I'll post yours too on there.

Check out my newly created community [email protected]. Have you tried the guide that I posted regarding Kindles and Amazon removing Download & Transfer? https://lemmy.dbzer0.com/post/40761027

Check out my newly created community [email protected]. Have you tried the guide that I posted regarding Kindles and Amazon removing Download & Transfer? https://lemmy.dbzer0.com/post/40761027

I've been enjoying my time on here for some time now :)

It's a space for all discussions. Personally I'm against but the comm is open for all kinds of views.

I'd like to clarify that removing DRM does lie in a grey zone in many countries, including in the US due to some court rulings. In some countries the right to make a backup of your e-book might have priority over copyright law for example.

Language of Climate Politics sounds very interesting.

It's super frustrating how everyone's excited for the next centralized thing that'll just start anew on the road to eventual enshittification.

Hmm, sounds complicated to check out each publisher. Especially if I'm reading fan translations 🤔 Thanks though!

Interesting to see arrests still happening towards private trackers. I wonder how the Nordics fares nowadays when it comes to being the Mecca of filesharing, feels like the golden days have passed since long ago.