You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
its come to my attention that some indexers temporarily suspend your API key if redirect is not being used instead of "Proxy NZB's"
What do you want to happen?
allow the ability to choose "NZB access type" per indexer on the indexer's config page rather than restricting it to a global option where you are forced to use one or the other for all indexers.
If not clear, why do you want it?
so I can continue to proxify NZB's for "Fallback for failed downloads" to work with all my other indexers except for those who impose restrictions.
Do you think it's something only you need or something that might be popular?
if more indexers follow suit or start imposing ridiculous restrictions then yes it may become an needed feature..
If not clear, explain the use case.
not sure how much clearer I can get.
The text was updated successfully, but these errors were encountered:
I'll look into it. I think I'd rather keep a list of the indexers in the code and always use certain settings for them in order to keep the configuration from getting even more complicated.
its come to my attention that some indexers temporarily suspend your API key if redirect is not being used instead of "Proxy NZB's"
What do you want to happen?
allow the ability to choose "NZB access type" per indexer on the indexer's config page rather than restricting it to a global option where you are forced to use one or the other for all indexers.
If not clear, why do you want it?
so I can continue to proxify NZB's for "Fallback for failed downloads" to work with all my other indexers except for those who impose restrictions.
Do you think it's something only you need or something that might be popular?
if more indexers follow suit or start imposing ridiculous restrictions then yes it may become an needed feature..
If not clear, explain the use case.
not sure how much clearer I can get.
The text was updated successfully, but these errors were encountered: