8000 Add alternative connection limits option for seeding torrents by lstrsrt · Pull Request #23065 · qbittorrent/qBittorrent · GitHub
[go: up one dir, main page]

Skip to content

Conversation

@lstrsrt
Copy link
@lstrsrt lstrsrt commented Aug 5, 2025

This PR adds a new option to the Connection settings: a checkbox + spinbox "Maximum number of connections per seeding torrent" which allows the user to configure a different connection limit for seeding torrents. The rationale for this is laid out in #2193 -- basically it is not necessary to have as many connections when seeding a torrent vs when downloading it. I have not worked on this codebase before, let me know if there is a better way to achieve this.

image

Resolves #2193.

Edit: Updated screenshot.

@glassez
Copy link
Member
glassez commented Aug 5, 2025

What immediately caught my eye in the screenshot is the confusing option "Alternative limit for seeding torrent". It looks like it should be a sub-option of "Maximum number of connections per torrent". Otherwise, it should contain the same text, e.g. "Maximum number of connections per seeding torrent".

@lstrsrt
Copy link
Author
lstrsrt commented Aug 5, 2025

The option naming was inspired from the screenshot in the linked issue. It is meant to imply that it is a suboption of the option above it (the screenshot doesn't show it, but the checkbox can only be toggled when "Maximum number of connections per torrent" is enabled).

I'm thinking it may be better to just make it a separate option though, so that users can set a limit only for seeding torrents.

Edit: Also starting to think that the "AltConnections" naming in the code is unclear. "SeedConnections" would be clearer. Will update this later.

@glassez
Copy link
Member
glassez commented Aug 6, 2025

It is meant to imply that it is a suboption of the option above it (the screenshot doesn't show it, but the checkbox can only be toggled when "Maximum number of connections per torrent" is enabled).

Usually suboptions in qBittorrent look like the following:
000

@glassez
Copy link
Member
glassez commented Aug 6, 2025

I'm thinking it may be better to just make it a separate option though, so that users can set a limit only for seeding torrents.

I agree.

the "AltConnections" naming in the code is unclear.

👍

@glassez
Copy link
Member
glassez commented Aug 6, 2025

"SeedConnections" would be clearer.

👎
It's a torrent who is seed.
So it should be "MaxConnectionsPerSeedingTorrent".
"MaxConnectionsPerTorrent" should become "MaxConnectionsPerDownloadingTorrent" to be consistent.

@lstrsrt

This comment was marked as resolved.

@glassez

This comment was marked as resolved.

@lstrsrt
Copy link
Author
lstrsrt commented Aug 6, 2025

Ok, renaming done. Hopefully didn't miss anything (I tried to automate it with sed as best as I could).

Also I guess this requires a DB upgrade due to changing an existing option name... see newest commit.

Edit: Or alternatively this commit could be dropped and the DB name kept as-is. But then it would be inconsistent with the names in the code.

@github-actions
Copy link

This PR is stale because it has been 60 days with no activity. This PR will be automatically closed within 7 days if there is no further activity.

@github-actions github-actions bot added the Stale label Oct 29, 2025
@lstrsrt
Copy link
Author
lstrsrt commented Oct 29, 2025

Bump. As far as I can tell, the failed checks are unrelated to the code added here.

@github-actions github-actions bot removed the Stale label Oct 30, 2025
@lstrsrt
Copy link
Author
lstrsrt commented Nov 4, 2025

I think all reviews so far are covered now.

@glassez glassez requested a review from a team November 4, 2025 17:24
@glassez glassez added GUI GUI-related issues/changes Core and removed GUI GUI-related issues/changes labels Nov 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Alternate connections per torrent while seeding.

2 participants

0