Closed wieluk closed 1 month ago
I dont get it. What problem are you trying to solve please?
I am sorting private torrents into different categories.
Sure but what do you win by doing so?
Not having hundreds of unsorted torrents in one category?
What is your goal? You want to differentiate between private tracker torrents and non-private tracker ones? That would be a feature request to qbit that you can filter in their UI (by isPrivate attribute; no need to add that to category)
No I just want to have them in their own categories to have a oversight but it doesn't seem like this is something you want so I a will just let my script run.
I simply don‘t understand the benefit you are aiming for. If it‘s about the ability that you can differentiate in qbit between private and public trackers, I still think categories are the wrong approach; use the isPrivate attribute instead. It‘s not shown on the UI currently, but you may request that from qbit or even do a PR yourself.
In addition, if you split the sonarr category into sonarr-public and sonarr-private, I am not sure how that would not break sonarr, since in the torrent client settings sonarr to my knowledge can only look for one category to know which torrents are relevant to sonarr.
No I am sorting each private tracker into into its own category. There is one category per private tracker.
Let‘s say you have done that, and now you have several categories. How do you link sonarr/radarr to these categories? They only support one category (eg „radarr-category“, „sonarr“ or whatever you have defined in these apps) but not multiple ones
This is done post import so I do not need to link it
I have something like this (really quick and dirty):
running in the background. Do you think it could be a good addition? Not exactly like this but more polished and with automatically creating the categories before?