If a torrent is right on the threshold, would pausing make the seeds drop and cause it to reengage next time, making it oscillate?
And same for multiple seeds using it, they could start to each drop out and rejoin all at once if they have similar cron frequencies. Especially since trackers have some delay.

I also wouldn't un- and repause paused torrents every cycle. So having a 3rd condition function that filters for being under a somewhat lower seed count (hysteresis) where it unpauses would solve both.

I'd expect qbit to have some overhead for resuming, and also to dos the trackers a little, if there are oscillations or paused torrents are momentarily resumed every run.

Edit: should prob ping @dessalines@lemmy.ml since this is a crosspost.

interesting, 10 has been my threshold for keeping on seeding for years

I just seed everything. Most of the time nothing is actually transferring. Dunno if @dessalines@lemmy.ml actually has an upload problem and is using too much bandwidth. What actually made you write this?

P.S and why not on codeberg or Radicle?

Sounds like a nice thing. Although I think I'll continue doing that manually. I have a habit of evaluating the content that I've got from torrents. I do it in my mind explicitly. And then I share longer proportionally to how good the thing was, and how rare I estimate it is. This is decided once and doesn't change after, with a built-in "share ratio" limit. Once a torrent reaches its ratio and becomes Paused, I know that it's done and can be removed.

In the beginning, all torrents stop as soon as they finished downloading, to let me evaluate the content. (Uninteresting stuff I intentionally don't share back at all.)