-
Notifications
You must be signed in to change notification settings - Fork 7
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
[Feature Request] Add a fake connected hubs counter for connected hubs #16
Comments
Those limitations are not 'ridiculous'. The normal hubs count is ~20. Check TE hublist for share percentage stats, maybe you will be shocked. That is, most DC hubs are totally useless. |
TE hublist? How to lookup percentage stats? |
See the Unique parameter for each hub. |
I am not sure how is that connected to the issue. A hub should not know which one hub the client is connected in first place nor the quantity of hubs. If it does then you specifically expose it. |
That does not correspond to protocol requirements actually. http://mydc.ru/index.html?showtopic=915&view=findpost&p=6721
The issue is that users sometimes do stupid things like connecting tons of useless hubs. You do not like hub restrictions? Well, go connect another million of hubs with no restrictions at all. No? Then respect the decision of the hub administrator. That's how it works. |
There is a list of some commands without relation to the issue and it has no any "requirements" related to the issue.
This is a user choice to decide which one hub is useless, which one to connect and search until it is not a spam, abuse or manipulation.
That is how it works in THIS software, not how it should work in decent software which does not force strange features without ask the user. |
Some hubs disconnects you with the message like that:
"Too many open hubs, maximum is 40 and you have 50."
Can you add a fake counter to bypass ridiculous hub limitations like that?
The text was updated successfully, but these errors were encountered: