Feature Request: Add the options "Ignore seeding limits for private torrents" and "Ignore rate limits for private torrents" to the settings #15794

New issue

Open

opened 2026-02-22 02:30:09 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-22 02:30:09 -05:00

Owner

Originally created by @microraptor on GitHub (May 26, 2024).

Suggestion

Under Options -> BitTorrent -> Seeding Limits add a checkbox saying "Ignore seeding limits for private torrents". If it is enabled, the global seeding limits won't be used for torrents with the private flag enabled.

Similarly, under Options -> Speed -> Rate Limits Settings add a checkbox saying "Ignore rate limits for private torrents". If it is enabled, the global rate limits won't be used for torrents with the private flag enabled.

Use case

These simple settings make sure not all the bandwidth is used up by torrents from public trackers if also seeding private torrents.

Extra info/examples/attachments

More complex somewhat related feature requests:
#15386
#9602
#7486
#3650

Originally created by @microraptor on GitHub (May 26, 2024). ### Suggestion Under Options -> BitTorrent -> Seeding Limits add a checkbox saying "Ignore seeding limits for private torrents". If it is enabled, the global seeding limits won't be used for torrents with the private flag enabled. Similarly, under Options -> Speed -> Rate Limits Settings add a checkbox saying "Ignore rate limits for private torrents". If it is enabled, the global rate limits won't be used for torrents with the private flag enabled. ### Use case These simple settings make sure not all the bandwidth is used up by torrents from public trackers if also seeding private torrents. ### Extra info/examples/attachments More complex somewhat related feature requests: #15386 #9602 #7486 #3650

deekerman added the

Feature request

label

2026-02-22 02:30:09 -05:00

deekerman commented

2026-02-22 02:30:14 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 25, 2025):

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.
Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
(new/existing contributors/developers are always welcome)

DO:

Provide constructive feedback.
Display how other projects implemented same/similar etc.

DO NOT:

Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

@xavier2k6 commented on GitHub (May 25, 2025): ## ANNOUNCEMENT! For anybody coming across this **_"Feature Request"_** & would like/love to see a potential implementation in the future! **Here are some options available to you:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. Please feel free _(If you have the "skillset")_ to create a **_"Pull Request"_** implementing what's being requested in this ticket. **_(new/existing contributors/developers are always welcome)_** ____ **DO:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**