dirkf

The extractor has two IEs but none of the existing test URLs succeed. If the URL pattern for `RuvSpilaIE` is tweaked, I can watch the very scenic movie from the...

If the answers to my questions are as expected, that seems to have been replaced by spilari.nyr.ruv.

So for (b) the answer is as follows? * Those URLs are still valid and #8925 provides an example for testing. * Like everything with 'new' in the name, the...

Apparently the programme page for the problem video is https://www.ruv.is/sjonvarp/spila/svar-vid-brefi-helgu-with-english-subtitles/35763/al201h but any JS requests invoked when playing the video are to spilari.nyr.ruv.is.

In the problem page there is a ld+json block containing an `AudioObject` with `'contentUrl': 'https://produktwerker.podigee.io/204-neue-episode'`. To extract this audio URL, append to this URL like so `https://produktwerker.podigee.io/204-neue-episode/embed?context=external` to get (maybe...

Part of the resolution of the issue would be to "support" produktwerker.podigee.io either as part of the Heise extractor or perhaps through a separate extractor for podigee.io, which appears to...

This issue is about a page that needs Podigee. Someone may care enough to fix that problem (not looking likely so far), ideally without breaking any other still relevant extraction...

This seems like a case where the non-fatal error shouldn't have been, but you'd have to provide more details, as in the bug report template(s).

The ITV extractor probably fails anyway, and the default `errnote` didn't need to be re-specified. You would have to maintain a list of (host, port) that had experienced 429. A...

AHA, sorry. In this case, the YT webpage failed with 429 but yt-dl was able to fetch the JSON which is supposed to be enough to get the video, though...