by Lanigiro » 25 Oct 2014 18:21
Any solution involving adding security rules to Shareaza (manually or automatically) will cause Shareaza to get slow and wonky, in my experience, as it tends to if there are a bazillion security rules rather than a couple of dozen or so.
Any solution involving banning from outside Shareaza (operating system level or router -- IPtables, firewall rules, PeerBlock, software firewall, etc.) will interfere with non-Shareaza applications, e.g. web browsing, and thus have unwanted side effects.
I don't see a problem with my original suggestion. Even if some people use Shareaza from inside China, they're a minority and furthermore Shareaza could use the net-facing IP of itself to decide whether to exclude the three country codes noted from the G2 cache or exclude everything else. Or if it's asymmetrical, exclude nothing when operated inside China. Or always exclude China from G2 hub list (which is what the code will do if used unmodified). Whatever seems to work best for both sides of the GFW.
If the other suggestion on QA packets would work, maybe modify it to just silently not add to the hostcache, without gumming up Shareaza with (eventually) thousands of security rules that will bog things down. As long as the problem hubs never make it into the G2 hostcache the problem is solved.