Registered Member
|
I was wondering if it would be possible for you to implement an auto ban client type.
For example you could set it so all peers utilizing Bitcomet are automatically added to the ban list and is not dependant on the tracker filtering out the clients. |
Registered Member
|
I think the problem when we would deal this problem this way, is that it will push them a little harder to spoof their client.
In my view it would be a better deal if we'd had a few settings that would say like: - give higher priority to peers that support the protocol (leeching and seeding) - do not deal with peers who interfere with the protocol (leeching) There would be made a whole detection algorithm for this to be working(which could be a big task only doing a draft), but it would work far better then blocking information that is 1) spoofable in the first place and 2) we actually make a choise and say we do it because of securing/supporting the protocol. |
Registered Member
|
Granted you are never gonning to be able to weed out 100% of the wanted clients because of spoofing but you will weed out a large majority of them. I just want the ability to weed out the majority of people using cheating clients (which is the only reason they use them, either intentionally or unintentionally). I would much rather be able to on the fly support the peers with my bandwidth that use a complient and friendly client vs ones that hammer trackers, leak like a sieve and cheat on stats.
|
Moderator
|
|
Registered Member
|
|
Registered Member
|
|
Registered Member
|
Just to let you l know there are plugins for this available for Azureus.
http://prdownloads.sourceforge.net/azcv ... 2.1.22.jar And it works extremely well. |
Registered users: Bing [Bot], Evergrowing, Google [Bot]