mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
rss downloader ratio setting #4284
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#4284
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jae110488 on GitHub (May 17, 2016).
This really isnt an issue but I was redirected from https://qbforums.shiki.hu/index.php/topic,654.0.html and told to mark this as '[Wishlist]'
I know there is already a setting for the client to allow a ratio limit. When this is enabled and torrents (that might have come from a private tracker) are up to the limit change status to completed. You also, can't even force the torrent to continue to seed after that, it automatically reverts to 'completed'.
However when i'm sleeping and my rss refreshes and downloads a torrent that is from a public tracker it seeds all night long. Some ISPs set a cap of data that can come through. So is possible that a future release include a setting under RSS to have ratio limits that apply to that specific rule definition?
@TerrorFactor commented on GitHub (Nov 3, 2017):
Seeding rules based on category (which could be based on tracker) would be great.
That's the main reason I am still torn between qbittorrent and deluge or rtorrent.
#3650 #5266 #6343 are roughly similar.
@tainewoo commented on GitHub (Nov 14, 2023):
+1 for setting the share limit per rss rule.
@thalieht commented on GitHub (Feb 1, 2024):
It's coming in 5.0.