Quote:
I'm not sure what you want us to do about it. We didn't write it, we don't promote it, we can't stop people from using it. Perhaps they could figure out a way to just detect the mod version and only ban that? (unlikely I know)
But if that's the reason, then they must have banned qBittorrent because of its leecher mod too?
If No, then why haven't they? Why single only BiglyBT out when every other open source client has this problem?
There is a solution that would make everyone happy:
Have the tracker owners write up a tracker/peer spec that is spoof-proof and all clients that want to use those trackers can implement it. No more client blacklists or whitelists needed, no more inspecting each new client version for approval -- either the client follows the spec and thus the rules and they are allowed, or they don't follow the spec, and they are banned.
Therefore, I don't expect any changes regarding how traffic is reported or peers are authenticated for the foreseeable future.