Reading your post, I am thinking about agreeing with you. It also will eat up tokens very fast. I withdraw my request. LOL
I proposed in another thread, piggybacking on someone else's proposal, of a a settable configuration textbox around 'delay' between queued downloads. From a code perspective, pretty easy to do; if you wanted to get fancy, you could even 'delay' from the start of the download time - to accommodate slower downloads.
This would essentially allow you to queue up 100 episodes of a show, but download one every 35 mins or so .. and keep you token 'neutral'. Truthfully, there is no reason I should need to sit NEXT to my computer, hitting a button every 2-3 minutes, for hours. The computer can do that (better than I can). I would rather queue up stuff at night, and let it run while I'm asleep.
This came out of me downloading the full series of Arrow, and then Amazon severing ties with one of their providers that had thousands of 'old' movies with only 1-2 days notice. {so I was token empty, and then only had like 36 hours to grab some films before they went away.]
Would you be willing to pay an additional fee for support of additional providers?
Maybe? I forked over for a lifetime subscription for a reason, and it was a chunk of change. I rolled the dice that you guys will stick around, and not get blocked etc. and paid a chunk up front for a chance to 'save' over the long run as the software matured.
I'm not sure how many folks took that risk, and I very much understand that adding a 4th provider to maintain is increasing your technical debt/responsibility that you have to work with.
That being said, Hulu is owned by Disney, and is a massive library with some exclusive content deals (which is why DIsney bought them) Disney will only increase that a they seperate family content from Touchstone/adult content.
Depending on the provider, I would be willing to fork over some more $$ to get them implemented and supported in a way that makes sense. Dev hours don't come from a vacuum. If you guys are running at 95% capacity, then you will need more help to implement more - I get that. There is a sweet spot on that however, and you run the risk of really alienating a customer who chunks down 20 euro for a year of service, which then get's shut down. Regardless of 'knowing the risk' up front - it will still cause PR issues.
Then it is a matter of the Devs focusing on services that have a wide audience (Hulu, HBO Max, etc) so they can swing any additional compensation etc.