dirkf

This test URL https://www.bilibili.com/video/BV1jL41167ZG/ from the yt-dlp extractor is described as "supporter-only" but not detected as such, by either the original extractor or my back-port. Is the short looping video...

Is this a standard video (that might be identified by its size, say)? Otherwise, as I commented, it's not obvious how to detect "supporter-only" videos, which would be useful to...

This is just one of many test URLs. The point of tests is to use examples that cover all the various cases that users may encounter. Perhaps this metadata item...

Indeed that is the only test video that has `is_upower_exclusive_: true`, so I'm assuming that it means "supporter-only". A WIP extractor based on yt-dlp's (with the new PR https://github.com/yt-dlp/yt-dlp/pull/9117) looks...

The issue is twofold: * `_call_api()` has `_download_json(..., fatal=False, ...)`, which can cause `_download_webpage_handle()` to return `False` instead of raising * the specialisation of `_download_webpage_handle()` doesn't take account of that,...

The result is only a tuple if the webpage was fetched. When `fatal` is falsy, `False` can be returned if the request failed. If it was only intended to affect...

Not all true at the time That's equivalent to the patch that I posted, given that `res` (called `webpage` in the original code) is guaranteed to be either `False` or...

Oh sure, edited. Current _yt-dlp_ would do that because the network rework now indexes the content after the "petty" test, while formerly and upstream the content is destructured, which would...

The same considerations apply as in #8952 and linked upstream issue ytdl-org/youtube-dl#31426 for Invidious.

But now that the generic webpage extraction has been in place for some time, the said list could (should?) be replaced by code that detects all piped and Invidious pages.