Skip to content

[FR]: Allow to change the upload_speed after a certain seed_time is reached #737

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 of 2 tasks
AN1MATEK opened this issue Jan 24, 2025 · 0 comments
Open
1 of 2 tasks
Assignees
Labels
feature request New feature or request

Comments

@AN1MATEK
Copy link

AN1MATEK commented Jan 24, 2025

Is your feature request related to a problem? Please elaborate.

I was trying to get this logic to work, but it seems not possible at the moment.

Seedtime < 180 days = no share limits
Seedtime > 180 days = limit speed to 2Mb/s

A new option in the strategy could allow users with limited bandwidth to keep seeding old torrents instead of pausing them or relying on min_num_seeds.

Describe the solution you'd like

A new option, may be named something like upload_limit_trigger or something, that can be set to a X amount of time. Before that, the global setting is used; after that moment, the configured limit_upload_speed can go into force.

Does your solution involve any of the following?

  • New config option
  • New command option

Describe alternatives you've considered

A script that will run once a day and tag such torrents is a viable alternative. I figured as this promotes long term seeding, FR would be considered.

Who will this benefit?

It seems like everybody: seeders, leechers and trackers.

Additional Information

No response

@AN1MATEK AN1MATEK added the feature request New feature or request label Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants