[Feature Request] Idle/stop on specific conditions (based on time/ratio/seed time/number of seeders?)

[Neurology0443]

Hello :)

First, you have created a Monster ! Thanks for your useful tool which works perfectly with a very intuitive UX and eye appealing UI. I hope not to many people come across your project xD This could be the downfall of private trackers !

Why would this request be useful? And what would this feature solve?

Sometimes some torrent have "ghost" leechers or slow leechers which could potentially make your ratio sky rocket and stop your seeding torrent very quickly (depending your stop conditions) which isn't ideal ! Also If you want to long term seed a torrent it would be very useful to set a stop condition when the torrent reaches a specific seeder number (e.g. If the torrent has 10 seeders and you have reached your ratio, stop the torrent)

My personal ideas

Add a custom Idle/stop condition (some ideas but not limited to):

• Put the torrent in idle state after X minutes/hours of seeding (with a random number between X and Y minutes/hour) and bring it back after X minutes/hours (also a random number between X and Y minutes/hour)
• Put the torrent in idle state after reaching your seed goal (torrent still in the seed queue without seeding anything. This would allow to increase your seeding time without exploding your ratio OR stopping your torrent)
• Put the torrent in idle state during X min/hours before even starting to seed (seeding when you just started in the seeding queue is very suspicious, specially when there is already a leecher on this torrent)
• Stop the torrent when there are 10 seeders
• Stop the torrent when there are 10 seeders AND you have reached your ratio or seeding time
• (edit) After reaching your ratio goal put it in long idle state for long term seed (generate bonus points for the internal exchange market)
• ...The only limit is your own imagination...

Some questions related to the request.

How does Rustatio behave when I set the upload rate to 0 compared to idle state? Does it continuously send "Seeded 0 KBs" to the tracker? This would look very suspicious from the trackers perspective. Right now I'm trying this out but I'm unsure if this is the same as idle state. Would be way more natural to make it randomly switch between idle to seeding based on specific conditions.

---

Again, thank you and congrats on your project and I'm always impressed how memory safe Rust is... Compared to JOAL, build with javascript which literally eats 400MiB of ram on startup, Rustatio sits quietly with less than 15MiB xD

Bye 👋 !

[Neurology0443]

Okay this is related to PR #81 !

This solves the continue seeding (idle) after a stop condition. However it would still be good to have something like a pre-start condition:

• Put the torrent in idle state during X min/hours (seeding when you just started in the seeding queue is very suspicious, specially when there is already a leecher on this torrent)

[theguy000]

• Stop the torrent when there are 10 seeders

this is not nessesary at all.

• Put the torrent in idle state during X min/hours (seeding when you just started in the seeding queue is very suspicious, specially when there is already a leecher on this torrent)

do you mean add delay before seeding after download is completed?

How does Rustatio behave when I set the upload rate to 0 compared to idle state?

stays idle.

[Neurology0443]

do you mean add delay before seeding after download is completed?

Not after download is completed, a start condition ! Before it even can seed anything (even if there are leechers waiting in the queue). During that time it stays in idle even if there are leecher on the torrent.

e.g. : Stay idle for 24h and do not seed anything even if there are any leechers. After that time is elapsed it can seed again if there are any leechers.

Why you may ask? If have read somewhere that if you are new in the seeding queue you're not supposed to be the the first seeder seeding anything. But I may be wrong here.

---

Another good to have option is to set a randomized range to put the torrent in idle state and bring it back to seeding after another time range.

e.g. :

• randomized time range in minutes, to put the torrent in idle (180, 360)
• randomized time range in minutes, for how much time the torrent stays in idle (60, 100)

This would put for e.g. a torrent in idle state after 200 minutes of seeding and bring it back to normal (either idle or seed if there is any leecher) after 80 minutes. But ONLY for seeding time not idle+seeding time !

Why you may ask? As I said before, on some torrents there are "ghost" leechers which stay for days (config issue, server issue? IDK). With RustUP I had the issue that after a 2 days span I had seeded over 1TB of data to someone who doesn't even was leeching anything...

But i'm just babbling around :) There a already stop safe solutions with rustatio which a really great !

---

Sorry if I'm not clear enough, and I'm probably enable to put my thoughts into words... If that's not something on your mind you can simply close this [Feature Request], Rustatio already does a lot with randomizing the upload speed and has nice stop safe conditions :) (Can't wait for the new PR to put the torrent idle after reaching it's goal) And you for sure know better than I on how the torrent ecosystem works.

Thanks for reading and responding on my Feature Request !

Have a nice day.

[testycro]

I've been working on a Bash script with powerful API rules that allow access to a wide range of custom actions.

It starts with the container as a daemon and is fully configurable and intuitive.

I'm trying to figure out how to submit a pull request, but I'm not familiar enough with GitHub and Docker to integrate it seamlessly, even though I've tinkered with it in a container.

https://github.com/testycro/rustatio