Meta - Generic announcement posted in locked topics where general users cannot react #16902

New issue

Open

opened 2026-02-22 03:31:13 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-22 03:31:13 -05:00

Owner

Originally created by @hugeblank on GitHub (May 23, 2025).

Originally assigned to: @xavier2k6 on GitHub.

From the announcement:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.

Adding reactions is unavailable to users in issues where commenting has been locked, like #4163. I'd suggest either unlocking the topic or moving things like feature requests to discussions where they can be unlocked and upvoted.

Originally created by @hugeblank on GitHub (May 23, 2025). Originally assigned to: @xavier2k6 on GitHub. From the announcement: > 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. Adding reactions is unavailable to users in issues where commenting has been locked, like #4163. I'd suggest either unlocking the topic or moving things like feature requests to discussions where they can be unlocked and upvoted.

deekerman added the

Project management

Meta

labels

2026-02-22 03:31:13 -05:00

deekerman commented

2026-02-22 03:31:19 -05:00

Author

Owner

@stalkerok commented on GitHub (May 24, 2025):

also https://github.com/qbittorrent/qBittorrent/issues/164

@stalkerok commented on GitHub (May 24, 2025): also https://github.com/qbittorrent/qBittorrent/issues/164

deekerman commented

2026-02-22 03:31:21 -05:00

Author

Owner

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

@hugeblank @stalkerok @nchevsky I am aware of those tickets from a open/locked search & because they've been brought up in the past previously in other discussions.

There are only 3 locked tickets!

I'll refer you & others in relation to #164 to our maintainers https://github.com/qbittorrent/qBittorrent/issues/164#issuecomment-388520313 & will quote it completely below for transparency:

I think this has gone offtopic too much.

The desire for a permanent "sequential mode" option is noted.

The desire for a streaming option is also noted.

We're almost ~3 volunteers working in a somewhat stable fashion on this project. There are also quite few other volunteers contributing in a more relaxed fashion. All of us code the things we care about and those we find incentive to fix or implement. It is our free time and we choose on how to spend it.

Anyone wanting to implement point 1 or 2 or both, should come up with a PR. We will discuss there about implementation details.

Because this topic has been discussed to death I am locking this thread. Members with write access should have the ability to comment and unlock.

I'd suggest either unlocking the topic

I had planned to revisit & unlock those tickets at the end of posting the "announcement" as I am aware that users can't post reactions or provide constructive feedback.

I will now unlock:

#164
#4163

I will not (for now) unlock:

#13094

moving things like feature requests to discussions where they can be unlocked and upvoted.

This was discussed previously & IIRC there was some caveats to doing this so it was rejected/deferred.

@xavier2k6 commented on GitHub (May 24, 2025): @hugeblank @stalkerok @nchevsky I am aware of those tickets from a [open/locked search](https://github.com/qbittorrent/qBittorrent/issues?q=is%3Aissue%20state%3Aopen%20is%3Alocked) & because they've been brought up in the past previously in other discussions. There are only 3 locked tickets! - #164 - #4163 - #13094 I'll refer you & others in relation to #164 to our maintainers https://github.com/qbittorrent/qBittorrent/issues/164#issuecomment-388520313 & will quote it completely below for transparency: > I think this has gone offtopic too much. > > 1. The desire for a permanent "sequential mode" option is noted. > 2. The desire for a streaming option is also noted. > 3. We're almost ~3 **volunteers** working in a somewhat stable fashion on this project. There are also quite few other volunteers contributing in a more relaxed fashion. All of us code the things we care about and those we find incentive to fix or implement. It is our free time and we choose on how to spend it. > 4. Anyone wanting to implement point 1 or 2 or both, should come up with a PR. We will discuss there about implementation details. > > Because this topic has been discussed to death I am locking this thread. Members with write access should have the ability to comment and unlock. ____ >I'd suggest either unlocking the topic I had planned to revisit & unlock those tickets at the end of posting the "announcement" as I am aware that users can't post `reactions` or provide constructive feedback. **I will now unlock:** - #164 - #4163 **I will not (for now) unlock:** - #13094 >moving things like feature requests to discussions where they can be unlocked and upvoted. This was discussed previously & IIRC there was some caveats to doing this so it was rejected/deferred.

deekerman commented

2026-02-22 03:31:21 -05:00

Author

Owner

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

NOTE:

I'll refer you & others in relation to https://github.com/qbittorrent/qBittorrent/issues/4163 to the following https://github.com/qbittorrent/qBittorrent/issues/4163#issuecomment-652467673 & will quote it completely below for transparency:

PR is merged!
arvidn/libtorrent#4123

Note that the PR has been merged to the master branch. qBittorrent will only benefit from this once: 1- this is merged into one of libtorrent's RC_x_y branches (according to the libtorrent author in arvidn/libtorrent#4123 (comment): "some other branch after 2.0") 2- qBittorrent supports said RC_x_y branch.

It will be a while until those last 2 conditions are met. In the meantime, this can be left open, but I'll lock it preemptively to prevent spam until there are new developments

@xavier2k6 commented on GitHub (May 24, 2025): **NOTE:** I'll refer you & others in relation to https://github.com/qbittorrent/qBittorrent/issues/4163 to the following https://github.com/qbittorrent/qBittorrent/issues/4163#issuecomment-652467673 & will quote it completely below for transparency: > > PR is merged! > > [arvidn/libtorrent#4123](https://github.com/arvidn/libtorrent/pull/4123) > > Note that the PR has been merged to the `master` branch. qBittorrent will only benefit from this once: 1- this is merged into one of libtorrent's `RC_x_y` branches (according to the libtorrent author in [arvidn/libtorrent#4123 (comment)](https://github.com/arvidn/libtorrent/pull/4123#issuecomment-676074545): "some other branch after 2.0") 2- qBittorrent supports said `RC_x_y` branch. > > It will be a while until those last 2 conditions are met. In the meantime, this can be left open, but I'll lock it preemptively to prevent spam until there are new developments