You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
@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.
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.
The text was updated successfully, but these errors were encountered: