mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Seeding Limit default improvement #14498
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#14498
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 @Programmer96 on GitHub (Apr 8, 2023).
Suggestion
Have you checked this? it's like 2 hours time limit; Really Bad for the Torrent Community. I think the Seed Limit default should be 4 weeks=40320 mins AND Ratio=11.0 as default, so people actually be seeders, so torrents don't die fast. So please implement this as a default ASAP, it's IMO urgent for the torrent community.
I always save my configuration folder and restore it after a fresh Windows installation, so I never worry about it, as I use these suggested numbers myself
Use case
I've been using torrents for about 10 years and most torrents, no matter how popular they are have only a few seeders, because after the initial seed most clients, stop seeding, I used uTorrent for like 5 years and it also has a Low Seeding Limit Default, so torrents after having sometimes 1,000,000+ seeder and leechers, they'll drop greatly after 2+ hrs.
Extra info/examples/attachments
No response
@glassez commented on GitHub (Apr 8, 2023):
IIRC, seeding limits are entirely disabled by default. Everything else is responsibility of the user who enables them.
@Programmer96 commented on GitHub (Apr 8, 2023):
I'd like a Dev. to confirm this
@thalieht commented on GitHub (Apr 8, 2023):
Confirmed.
@Programmer96 commented on GitHub (Apr 8, 2023):
OK then, the seeding is eternal, Amen.