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

[Feature Request] Add a fake connected hubs counter for connected hubs #16

Open
andry81 opened this issue May 1, 2021 · 6 comments
Open

Comments

@andry81
Copy link

andry81 commented May 1, 2021

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?

@Tantrix
Copy link

Tantrix commented Dec 24, 2021

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.

@andry81
Copy link
Author

andry81 commented Dec 25, 2021

TE hublist? How to lookup percentage stats?

@Tantrix
Copy link

Tantrix commented Dec 25, 2021

See the Unique parameter for each hub.

https://www.te-home.net/?do=hublist&action=hubstats#unique

@andry81
Copy link
Author

andry81 commented Dec 25, 2021

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.

@Tantrix
Copy link

Tantrix commented Dec 25, 2021

A hub should not know which one hub the client is connected in first place nor the quantity of hubs.

That does not correspond to protocol requirements actually.

http://mydc.ru/index.html?showtopic=915&view=findpost&p=6721

I am not sure how is that connected to the issue.

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.

@andry81
Copy link
Author

andry81 commented Dec 26, 2021

A hub should not know which one hub the client is connected in first place nor the quantity of hubs.

That does not correspond to protocol requirements actually.

http://mydc.ru/index.html?showtopic=915&view=findpost&p=6721

There is a list of some commands without relation to the issue and it has no any "requirements" related to the issue.

I am not sure how is that connected to the issue.

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.

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's how it works.

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.

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

No branches or pull requests

2 participants