Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please change "stalled" status to "No peer connections", which actually informs the user what the issue is #10059

Open
ghost opened this issue Dec 26, 2018 · 3 comments

Comments

@ghost
Copy link

ghost commented Dec 26, 2018

When the user sees their torrent as "stalled" they think something is wrong with the torrent or even something wrong with the client, but if qBittorrent would actually describe the problem accurately, by saying qBittorrent can't connect to any peers, it would clear that there's either no peers available or that no connections could be made to any existing peers.

It's about time that the word "stalled" stops confusing users and becomes a meme throughout Github and other forums. Please just use a better descriptor that informs the user what the issue is.

@Supralateral
Copy link

Well er, the Stalled status is already more informative than other clients (uTorrent, as an example, will just list the torrent as Downloading and not indicate anything wrong)

I think qBt may also use Stalled for some I/O (or other, non peer-related) issues, so blanket replacing it in such a way would be a problem

@ghost
Copy link
Author

ghost commented Dec 29, 2018

@Supralateral just because uTorrent is even less informative doesn't mean we should remain stagnant when there's something to improve.

As for I/O issues, qBittorrent should explicitly say if a torrent is having I/O issues so this wouldn't be blanket replacing it, it would creating new statuses for each problem.

@evansan
Copy link

evansan commented Dec 30, 2018

I agree qBt should use different words for I/O issues and connection issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants