Skip to content
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

[FR]: Size check for share limits #472

Open
1 of 2 tasks
NLZ opened this issue Jan 22, 2024 · 0 comments
Open
1 of 2 tasks

[FR]: Size check for share limits #472

NLZ opened this issue Jan 22, 2024 · 0 comments
Assignees
Labels
feature request New feature or request

Comments

@NLZ
Copy link

NLZ commented Jan 22, 2024

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

Some trackers have different seeding time requirements based on the size of the torrents, like AR says 72h under 48GB and 168h above.

Describe the solution you'd like

Would be nice if I could set the share limits accomodate this, maybe like this:

  AR-large:
    priority: 10
    include_all_tags: [AR]
    include_bigger_than: 48 # GB
    max_ratio: 1.0
    max_seeding_time: 10080 # 7 days
  AR-small:
    priority: 11
    include_all_tags: [AR]
    max_ratio: 1.0
    max_seeding_time: 4320 # 3 days

Not sure what would be the best config name for it, min_torrent_size could also work.
Or maybe defining max size instead of min on the other share limit group.

Does your solution involve any of the following?

  • New config option
  • New command option

Describe alternatives you've considered

As of now I just have to use the highest requirement to be sure.

Who will this benefit?

Everyone who are on trackers that have size dependent seeding requirements and want to minimize seeding time.

Additional Information

No response

@NLZ NLZ added the feature request New feature or request label Jan 22, 2024
estebanthi added a commit to estebanthi/qbit_manage that referenced this issue Jun 5, 2024
To apply share limits to torrents bigger than the given size in GB (related StuffAnThings#472)
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