qbit_manage
qbit_manage copied to clipboard
StuffAnThings
[FR]: Tag Torrents With Trackers That Don't Match Any Configured Trackers
Is your feature request related to a problem? Please elaborate.
It would be useful to be able to control public torrents and their ratio and seeding time via qbit-torrent.
Describe the solution you'd like
Add a "Public Tracker" or maybe "Other Tracker" tag with associated ratio and seeding time settings. Basically it would be a tag added to torrents that don't have a tracker that matches any other configured trackers. Assuming you configured all of the private trackers you use then this would tag public torrents which would allow setting the ratio and seeding time for public torrents via qbit-manage.
Does your solution involve any of the following?
- [X] New config option
- [ ] New command option
Describe alternatives you've considered
None yet
Who will this benefit?
Anyone who uses private and public torrents.
Additional Information
No response
Currently if a tracker isn't configured it will add the trackers that are missing in your config.yml file when trying to tag.
Currently if a tracker isn't configured it will add the trackers that are missing in your config.yml file when trying to tag.
That sounds like a good idea for private trackers but I can see this becoming difficult to manage for those that use public trackers since there are so many and they come and go over time. Ideally I think there should be an option to either keep the existing functionality (for those that use private trackers) and an option to simply tag torrents with trackers not found in the config as "Public Torrent" or "Other Tracker" and have a single ratio and time setting for those, instead of having to manage dozens upon dozens of public trackers individually and having to continually keep the config updated as those trackers come and go.
How would you identify the torrent is public or private?
If the tracker is in the configuration file it's save to assume it's a private tracker you configured. If the tracker isn't in the configuration file then assume it's public. Alternatively instead of calling the tag "Public Tracker" or "Public Torrent" play it safe and just call it "Other Tracker".
I don't think we can safely assume that if it's not in the configuration file then it's public.
I don't think we can safely assume that if it's not in the configuration file then it's public.
That's fair. The suggested feature would still be useful though. Just use the "Other Tracker" terminology instead of using the term "Public".
following this one, because most of public stuffs doesn't get processed unless it's coming from private tracker. Most of my *arr containers would add tags like "sonarr", "radarr", "readarr", and etc... would it be possible to process those tags instead of tracker?
you're right, that's what I meant by monitoring the categories type set by 3rd party applications.
I am also interested in a solution like this. Basically a way to configure a tag that acts as a catchall for anything that is not already configured. For example, I have my five configured trackers and then anything else gets tagged as "other". Then we can choose whether to add that specific tracker to the configuration file or not. My issue is that the script does not always add unconfigured trackers to the config and I end up with a lot of untagged torrents. If there was a fallback for anything that wasn't processed where generic settings could be applied that would be great.
How would you identify the torrent is public or private?
qB knows if they are private because of the private flag in the metainfo.
It's how qB and other clients know to disable DHT et al.
I also want this feature or at least a variant of it which allows me to tag "public" or "private" on all torrents based on tracker privacy (because qB WebUI annoyingly doesn't have a view for all private torrents). Further, it would let me drop https://github.com/Hundter/qBittorrent-Ratio-Manager which I use to set general ratio rules for private vs public trackers (it doesn't actually set them in qB, it just removes the torrents and data when the configured ratio cons.traints are met)
The latest develop branch adds support for this. In order to use it just update to develop and add the following other keyword under trackers config.
Example:
tracker:
other:
tag: public
max_ratio: 10.0
max_seeding_time: 120000
limit_upload_speed: 150