Kethsar

Nope, since the actual function that tries checks how long it has been since it last grabbed them.

Nothing. It's just a debug message that fires whenever it thinks it should try, before it calls the actual function that tries. That's why it appears, even if it doesn't...

I knew this would start eventually. I don't have the drive the yt-dlp people do to fight it much either. I might try updating which clients are used for requests,...

I've added support for the po token in commit 99a510d10c093f766315af5b7df9bc077070e526 It will require grabbing the token as outlined at https://github.com/yt-dlp/yt-dlp/wiki/Extractors#po-token-guide It's been working for me. I only just started getting...

>even after you interruptted and exited Hmm, is that doing a hard-interrupt without letting it exit gracefully? Disabling quick-edit mode was a "feature" someone else asked I put in because...

Personally I use a 3 minute retry and monitor 4 channels at a time (formerly 6), all from my main PC

Both, the potoken is required. I don't have a slew of different API clients set up like yt-dlp does, and the method yta uses currently requires a potoken.

Maybe without cookies, I don't know. With cookies my potoken seems to just last. I don't recall being forced to refresh it since it became a requirement.

I have multiple based on what I plan to watch, but the one I use is the only one I have memberships on, so is the only one where I...

I actually have something in place to do this automatically already. Did you see this message in your download? If so, can you post what it truncated to and what...