Well, whatever it is, it can certainly be avoided by planning ahead.
If they made it per provider, we would have all kinds of complaints from the other end of the spectrum - why give me 40 per provider (and less when they add providers) when I only use one or two? And just what the heck is "the purpose for which AnyStream is sold"? It's purpose it to let you download up to 280 videos per week. It was sold that way, and all your grousing about it is unlikely to change it.
I agree with you that a pool of generic tokens was probably easier and safer to implement.
And, since certain folks have a tendency to reply to threads without actually bothering to read them, or read them in the context of the thread, I should also point out the following :
I HAVE ZERO ISSUES WITH THE WAY THE CURRENT TOKEN QUEUING SYSTEM WORKS.
(caps for emphasis).
That being said, I do have to point out the flaw in the often parroted line that limiting tokens is in place to 'protect us'.
First, the obvious : They aren't in place to protect the users. They are in place to protect RedFox's revenue stream.
I am 100% ok with this too, because indirectly this protects my investment (a lifetime investment, with a soon to be upgraded license) in the software.
Initially, during the first trial, they were supposedly put in place to prevent banning of accounts. The 100 limit was enacted for the first provider to keep people from hammering them too hard.
We will ignore that Netflix has over 200m subscribers, so this was probably STILL aggressive because the ( generously ) 1000's of users that use AnyStream aren't even a 10th of a percent of Netflix's HOURLY traffic.
Again, I'm fine with a super-safe precautionary move on RedFox's part. I'm ok with safe and under the radar, as it lengthens the life expectancy of my investment.
What is my point with all this?
Once you have multiple providers in the mix, the 'we are just out to protect your accounts' argument starts to unravel.
If a 100 token pool (280 max downloads a week) is 'safe' for Netflix, then one assumes it would also be a respectable limit for Amazon, or Hulu, or Disney.
Clearly the devs think so, as they haven't adjusted the count lower.
No one knows where or how you spend those download tokens.
But to the point others have made : What happens when you split those tokens across multiple providers? (which people often say is exactly what they do.)
Amazon isn't going to ban you because of how many downloads you've pulled from Hulu or Netflix.
Netflix doesn't care what you do on HBO Max.
Aside from Disney and Hulu, the other providers are pretty unlikely to share data between themselves, especially not about potential leaks and or abuses of their systems.
So when someone defends the fact that we don't have seperate provider token pools with 'it is to protect you', they are using a dishonest (some might say FanBoi) argument, and are essentially gaslighting you.
If we had 280 max downloads for EACH PROVIDER, The upward limits of weekly downloads per provider would STILL be 280 max downloads.
So the theoretical idea is sound. We could have more tokens, split out among the separate providers, without additional risk of 'detection'.
If someone INSISTS that giving people more downloads is super risky for the user .. ask them what is preventing ANYONE from buying multiple licences to Anystream?
Because truthfully, if you need more downloads, that is TOTALLY an option
But back to the idea of separating tokens per provider as a practical idea?
No need to fix something that isn't broken when there is loads of broken stuff to fix.
Redeveloping the whole token system probably has a much lower ROI than adding new providers.