normally i dont request features, for as programmer i know how it feels when users ask too much from a no fee software. however, Mon's request encouraged me. so i'm gonna say it. no need feel pressure. definitely/totally/100% doesn't matter if no time or interest to do it.
0. ideally, i wish there's not only preset/hardcoded rules, but so called advanced rules like "if the task satisfies condition X, then execute command Y", in which X can be "seeders are more than ~" or "running time is more than ~" etc, and Y can be "stop the task" or "change the upload speed to ~" or even "announce/scrape once (at one's own risk)" etc. advanced users can freely splice rules to meet their own needs. a software enthusiast may see this kind of design pattern in millions of software, OmniFocus/TotalCommander/IFTTT/etc. flexible and powerful at the same time.
however, clearly this feature request is excessive, so maybe i should simplify/specified it to 2 simpler parts. hope it doesn't appear too picky. they are both to help further automation because i don't like to check peerlist or webpage every 15 minutes.
1. when seeder drops to 0, the download speed also drops to 0KB/s
in the absence of other better choices, sometimes i have to choose this kind of seed, like seeder=1, leecher=64, and here's the risk: even if we preset a reasonable download speed, once the seeder becomes 0, like the only seeder turn off computer and go to sleep, and we are not aware of this(don't like to check peerlist or webpage every 15 minutes), so the RMP keep fake leeching, which result in our file progress% may run ahead of everyone else and even become the only one who has arrived 100% without any seeder, which is definitely suspicious and become the target. - this is why this feature is needed.
some people may object that even if this only seeder is not offline, we may still finish ahead of everyone else and become the target. in fact, if our download speed B is set to B = 0.9 * A/(1-Z), in which A=average upload speed of the only seeder and Z=the max progress % of the leechers, it's safe enough. some may also object that we have already the similar feature "auto stop when seeders are less than ~", yeah, but this feature request is to joint the following start/restart feature together. once the task stopped, the announce with tracker stopped and the automation stopped, which is not we want here.
2. when leechers or seeders are MORE than X, set the upload or download speed to Y
when the number of leechers is too small, cheating is not safe, and also due to delay of announce, i usually preset "when leechers are less than 8, upload speed limit to 0KB/s" for every task. for the sake of better automation, i think "when leechers are more than X, set upload speed (back) to Y" is a wonderful correlative feature.
similarly, in order to cooperate with 1st request, it's also a good feature that "when seeder are more than 0, set the download speed (back) to Y" here(what is the appropriate value of Y is not discussed here)
some people may object that automation this much is risky. i think kitchen knife can hurt people is not a reasonable reason to ban the sale of kitchen knives. The key factor here is people. there're many other ways to avoid risks, such as hiding these advanced features from newbie users(like shift-f2 in uTorrent), or very clear big red warning.
3. allow scrape during running (like mR did), even allow automatically scrape every X min when running, in which X equals to like random(15, 40)
most of the posts i saw here said you should not use scrape because it is a feature vector that can identify you're cheating. therefore, there is a high probability that this feature will not be realized, but i'm willing to try to put forward. i've been using scrape for several weeks on a tracker where announce don't return leechers' amount, and haven't got caught. the benefit is the leechers number can be obtain, so the task can be automated, and the cost is only a risk that may be banned. one is benefit fact, another is downside possibilities. so yeah, i'm definitely willing to take this risk, because cheating is already taking the risk.
i do use some trackers that don't return leecher numbers, so scrape must be used for the sake of automation. i'd rather give up PT if i have to check peerlist every 15 minutes like Sisyphus.
---
again, thank you for writing this software in your spare time, no matter whether these features can be realized or not, i think it is already an awesome and helpful tool.:wink2:
---------- Post Merged at 05:41 ---------- Previous Post was at 04:08 ----------
what does <Condition has already met and torrent can't be started> mean? first time met this prompt. :eek13:
https://www.youtube.com/watch?v=wKnr_QNuIJ8