mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Tracker's full answer not visible to user #3470
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#3470
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Username0x on GitHub (Dec 6, 2015).
In a simple BitTorrent client named Transmission, there is a feature which shows detailed statistics on the "Trackers" tab of the torrent's "Properties" window. Enabling more details (by a tick) is very useful for diagnostics of tracker's connection. It shows seeders and leechers that tracker gave us in its last answer.
Example #1:
"Tracker had 8 seeders and 1 leechers 2 minutes ago
Asking for peer count in 26 minutes".
This means that torrent is not banned on tracker and everything if good.
When the torrent is banned on a tracker, it shows various answers which may help the user to understand that the torrent was banned or something else went wrong.
Example #2:
"Tracker had 0 seeders and 0 leechers 2 minutes ago
Asking for peer count in 15 minutes".
This answer shows us that tracker blocks our client or bans the torrent.
Example #3:
"Tracker had -1 seeders and -1 leechers 2 minutes ago
Asking for peer count in 15 minutes".
Again, it shows ban of block.
Would be very great to see the same feature in qBittorrent in the nearest future!
Thank You!
@chrishirst commented on GitHub (Dec 6, 2015):
It probably won't happen, it's just one more resource hogging 'feature' that is not that useful to most users.
@Username0x commented on GitHub (Dec 6, 2015):
Maybe, then (to make it simple and not resource-taking) it would be great to have a green or red lamp for each tracker in "Trackers" tab?
Green would mean that tracker did gave us good answer, and red means that -1/-1 or 0/0 or other banned/blocked status.
Because, present "Working" status means only that tracker is online. It does not really show if the tracker gives as really working status. So, users do not really know what happens!
@sledgehammer999 commented on GitHub (Dec 6, 2015):
Use latest version. In the sidepanel there are 2 categories for trackers with warnings and errors. It filters the torrents these trackers belong to. Then you can go to the Tracker tab of each torrent and see the "Message" and "Status" columns for each tracker. Usually trackers that ban you, return a message that is displayed there.
@chrishirst commented on GitHub (Dec 6, 2015):
No, a 'Working' status means that libtorrent was able to contact the tracker and useful and valid information was received.
Is "Not Working" not a sufficient indicator of a problem?
If no message is displayed it indicates the tracker could NOT be contacted or returned no data.
If "Not Working" has a message included it means the tracker WAS contacted but returned an error message which is then displayed.
How exactly is a message from a working tracker 'useful'???
@sledgehammer999 commented on GitHub (Dec 6, 2015):
In v3.3.x the "Working" status should now truly mean that we succeeded in announcing to the tracker and it didn't ban/block us.
In the v3.2.x series this isn't the case.
@Username0x commented on GitHub (Dec 18, 2015):
Thank you! =)