Proxy Buddy separates the Proxies in
- +Working (Online)
- +Google Passed (Online + Passed Google Search)
- +Down (Offline or Timed out)
- +Not tested
- =Total Proxies
I don't think that this is confusing.
I see that Scrapebox separate the list into Total Proxies, Anonymous (Online + Anonymous and or Elite) and Google Passed.
I think Scrapebox is more confusing because where you see the total amount of proxies that are online? How many proxies are offline? Where you see if the source is worth it? ...
I will attempt to explain a little further for you. In the explanation, I will show a side by side example with a program that dailly 180 initially wrote, and that I extended to include two methods of proxy checking in which there is an actual connection through the proxy server and a download of a page from the search engine rather than simply checking for headers of 200, 302, 404, etc.
I had done some other work to add a server connection timeout and a read/write timeout in addition to testing though Google and Bing as well as changing the search from http to https. The WebClient is SSL (all versions) enabled. The WebRequest not so much.
This program is not something developed to compete with you. Rather, it is a testing of a new form off polymorphism that I developed that I call "Object Based" polymorphism. The program execution changes based on what item it pulls from the queue. That object can be any object including custom classes. I currently have no code written for the load functions, but that is a simple matter. In a few days, when I remember the credentials for one of my Google accounts, I will put a demonstration video online and more than likely the source on GitHub or CodeProject as well as make it available here.
Lets look at the first picture. You have a total of 52 proxies out of which 121 are working, and out of that total of 52 proxies 61 have passed your Google check. Gee... The numbers just do not add up the reality is that there ae only 51 proxies in the list, or if you wish 52 because I am using zero based counting (in other areas, that is corrected, but not here).
In a C&P from PB to PPS (Public Proxy Scraper), and a removal of dups in which no lines are removed, 51 total proxies are shown. The numbers in PB are simply incorrect! You cannot have a total of 51/52 proxies of which 61 have passed Google checking, and of which 60 are down. Too boot, this is from a list of 51 of which 121 are working. Do you see the problem? Do you see why your user interface (GUI) is confusing. The scheduling button also falls into both poor user experience and poor user interface choices. You cannot see it. If you would have not pointed that button out, I would have never seen it (my corrected eyesite is 20/20 and I am about 18 inches from two 20 inch monitors, one monitor is 1600 X 900 and the other is 1280 X 1024, both are DVI). On my laptops, the GUI is even worse (1400 X 900 displays).
Moving on from the display and GUI problems, to the testing of the proxies. Simply reading headers to determine if a proxy is Google passed just does not cut it! I took the list of Google passed proxies from PB and C&P'd them to PPS. I used the WebClient that is SSL enabled by default and tested to see if I could download pages from the Google URL shown in the background of Visual Studio. The following image shows that out of 52 proxies, only 8 can download data from Google - 44 are Google blocked. If I test against Bing, the vast majorities of the proxies will download data, which means the proxy is up and working. Also, as long as I do not scrape or check proxies with both PB and PPS .net will not crash.
You are probably using a different method of connecting to the proxy server than I am. I have everything abstracted away rather than directly handling the connections. However, this does not excuse the incorrect results that PB is providing. It appears that you are reading the headers to check for a connection. This provides incorrect results, more than likely, because of the proxy servers cache; but I really do not know. At some time, the timers you have will fire and attempt to correct the numbers, but they are still incorrect.