Auto-restart seeding when Seeding Limit no longer met

[backpack5689]

Suggestion

I was setting up my seeding limits today, and started looking for if it was possible to auto-restart seeding if it dropped below that limit.

I was wondering if we could add this feature. I could see maybe another checkbox to say "when ratio drops below: {value}, restart seeding". So it would probably have to check the ratio (maybe daily or hourly (or make that configurable)). But it would just resume seeding the file.

Use case

This would be useful for those that torrent a mix of niche and mainstream items. With this feature, we could focus bandwidth on those items that are niche, and support the mainstream items when they drop to a certain level.

Extra info/examples/attachments

[glassez]

when ratio drops below: {value}

Under what circumstances do you expect the ratio could drop?

[backpack5689]

I apologize, I think I used the wrong term. I thought that Ratio was the same thing as Availability. Just realized that ratio was how much you've seeded/download.

What I was actually looking for was a way to stop and restart torrent seeding based on availability. So if the availability of a torrent dropped below say 3 or something, QBittorrent could re-start the seed.

[stalkerok]

Availability

Calculated only if you are connected to other peers.

[backpack5689]

Maybe we could add a setting to check with other peers every X amount of minutes/hours/days if it's been placed on hold for having too high an availability?

[stalkerok]

Perhaps you meant seeding limit based on the number of seeds, but there is an issue with this too, as qBittorrent (or libtorrent) takes information from the tracker as a basis, and if the tracker reports an incorrect number of seeds (or the torrent is trackerless), qBittorrent will not know the exact number of seeds on the torrent. It would be nice if the client itself could create more accurate lists of seeds when connecting to peers.
Related/Duplicate of #11830 #16552 #14725

[backpack5689]

Yeah I think it's related to all three of those. I guess the only difference between #11830 was the field, rather than being "Seeds" I was looking for "Availability" number.

At least as of now, I base my stopping/starting of seeding based on that number that may be incorrect, as it's the best I have to go on in my client. Maybe I shouldn't, but if the application used the same value I would expect that behavior.

Also I do apologize if it's duplicated. I think my terminology mistake contributed to that. If you would consider it a duplicate my feelings won't be hurt if you decide to close this. Thanks for looking at this regardless ❤️