[Wishlist] Several suggestions

Bug #955177 reported by FullNameHere
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qBittorrent
New
Undecided
Unassigned

Bug Description

Using Windows XP, qBittorrent 2.9.5

1) Search history : it seems stored in qbittorrent.ini file, and kept even after shutdown/restart, even if all search tabs have been closed and cleared in the graphic interface. I suggest that the user is informed about this (as a privacy concern), and that he is able to easily see it and erase it from the graphic interface. Or, maybe better, that it is not stored at all once removed from graphic interface search tabs. Is there any reason why this is kept, by the way ?

2) Fully downloaded files : the content tab of a given torrent lists percentage downloaded for each file. However, it is not clear if for a very large file among several other unfinished in a torrent, 100.0% may mean almost but not exactly fully downloaded, for example 0.01% remaining... This could lead to effectively corrupted (unfinished) files being used outside qbittorrent without the user noticing immediately. I suggest making it totally unambiguous in the graphic interface when a file in the content list is fully downloaded (for example with a change of color of the file name of download bar ? a small icon ? a specific new column ?).

3) IP ban list : I suggest that it is possible to see this list in the graphic interface, and more specifically different lists for each ban reason (corrupted data received, manual ban, maybe external IP filter also). The user could also be informed where this list is stored. And he should be able to clear a sublist or unban a specific IP. It may be argued that automatic bans from client should not be unbanned, but shouldn't one be able to see them at least, and more importantly, to unban a manually banned IP ? It should be made clear if IP ban list is kept for session or forever too, as I've read contradictory information about this.

4) Trackers banning qbittorent : if that behavior still exists, I suggest that it is possible to know that this has happened when connecting to a tracker (if that's possible and not already the case, pardon my ignorance).

5) Show encryption : I suggest that it is shown if connection with a peer is encrypted or not

6) Random port at start : I suggest that this option is made available (if it doesn't make it harder to find some peers, pardon my ignorance)

7) Smart updates : I suggest a self-update capability which does not involve uninstalling and reinstalling the whole software, if possible

8) DHT nodes info : I suggest to make it more explicit to the user (in the interface, documentation, journal tab...) what the client connects to when using DHT, especially for bootstrap ("well-known default" DHT nodes, nodes stored from previous session...), if all this makes any sense (sorry for my ignorance again). Would it also make sense to be able to browse the user's locally stored DHT information ? The whole system seems a bit obscure to me...

Tags: wishlist
Revision history for this message
Christophe Dumez (hydr0g3n) wrote :

No way I can track several feature requests in one report.

Regarding 1), it is already there: right-click on the search field and select "Clear completion history".

2) 100% means that it is complete, there is no rounding issue.

3) looks valid

4) If the tracker blacklists qBittorrent, it usually sends a message back explaining so. qBittorrent will then mark the tracker as "not working" in the tracker list and will display the message returned by the tracker there.

5) looks valid and easy

6) looks valid and easy

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.