You could well have something on your machine interfering with the sockets/threads that the rank checker is using. When I hit abort, which I don't do often, it does take a short bit to finish up and close the connection down, but it works fine. I don' tthink a lack of a progress bar is "chink". The program works, a status bar is only a visual element, and while it is nice to know its not locked up, its really just for those who might be impatient for the program to work so they know how much longer before they can get at what they want. It could be an enhancement sure. Public proxies are probably your issue, if they are mostly dead, which they could be, even after you test them. Everyone knows google cans proxies super fast now, public anyway. I don't even use proxies. If you put it on 15 sec delay and now proxies, it works great. Sure it takes longer, but just start it and minimize it and do other things and come back. I have used private proxies as with no delay. I run over 100 keywords so it takes a little bit, but something like traffic travis isn't really any faster, not in my experience. Its built with accuracy in mind over speed, which I think anyone can appreciate. I personally wouldn't trust public proxies in the rank tracker, they are going to likely cause more issues then solve, IMHO. Not having control over threads isn't a chink either. I guess the definition of a chink is something that doesn't work or causes something to not work as it should. The program works as it should and its meant to, so having control over threads could be an enhancement I suppose. But frankly, most people would turn them up too high, get all their IPs banned and then complain that it didn't. Already your using public proxies and they are probably banned and your complaining its taking too long.
Id say that in an accuracy based environment like this, Id expect it to take longer then a multi threaded google harvester. Quality over quantity. My 2 cents anyway.
