Tested on windows 7 vps 1GB memory 3ghz core. virus scanned and all clean.
- Using a list of 470 elite and anon proxies and 300 threads I got 0 valid with the new judge, but 4 with the classic one.
- Using 200 threads, 1 valid with the new judge / 50 with classic. (success didn't get much better after lowering threads to 100)
- Using 100 threads, 1 valid with new judge / 110 valid with classic (yay!)
- Put this list of 470 into scrapebox and got...7 Google Passed and 1 IP Passed.................Fun.
Ignoring Google, I got 151 IP Passed consistently after 3 runs...ywgacliwerhbshrbvs....son of a bitch...
- Using a php proxy judge I found online for the HOST (put in random text I found on the page for VERDICT), I got pretty much the same results as the classic judge comparatively for 300, 200, 100 threads.
I tried changing the new (google) judge to this:
Code:
[JUDGE]
HOST=http://www.google.com/search?tbm=isch&hl=en&source=hp&biw=&bih=&q=a&btnG=Search+Images&gbv=1
VERDICT=Business
[SETTINGS]
THREADS=100
TIMEOUT=30
This judge helped me get many more valid results and still uses google, but did not give me proxies I could use to scrape with (not blaming the software. i am noob)
- Using a list of 900 transparent proxies, I got 200-222 valid with my google judge, the posted classic judge, and my php judge. I was able to post with these, but could not scrape.
I put a list of 50 proxies that google and IP passed in SB, but got 0 valid from this list with all judge tweaking in CHPAG.
I tried posting to 20,000 AA's with the 50 proxies that passed SB and 50 of those that were valid in CHPAG but failed SB's test: Proxies that passed CHPAG posted with a success rate of 60% and SB proxies posted at 20% on the same list.
Even if CHPAG isn't currently validating proxies to scrape for me, because I'm clearly messing something up, it's an excellent and very lightweight tool to find proxies you can post with (not that you should exactly be posting with shared proxies).
You might be asking yourself at this point in my post, "hey, asshole, of course the proxies won't work with google if you're not checking them against google correctly." Jerks. I've been trying a bunch of things, and my only concern are the 50 proxies that did pass SB, but were labeled invalid for CHPAG. This is the only true bug I can see: proxies that can scrape are being labeled invalid. CHPAG might have a bias against transparent proxies as all the ones that did pass SB were transparent.
This is probably my own networking amateurism, as the same issue happens with pretty much every proxy tool I use, but the lists start off checking very fast and get slower and slower as it gets towards completion of the list. I know it's because it reduces the amount of threads and it's not a glitch, but sometimes this checker lowers threads to the point where it hangs at ~95%.
Because I love the interface (and it allows multiple instances without having to do anything, yay
) I decided to mess around to try to break it. I pressed the start/stop button a lot and what eventually happened was I was pressing stop and it would not stop or it would immediately go into another scan. Sometimes when at 100% it would continue scanning over the maximum number of proxies in the list.
Sidenote: Simple Google Scraper 1.41 is only looking for the keywords in the domain for me now. Even with intitle: or another operator, the results only have the keyword in the domain.
Been testing for almost 3 hours. Sleep time. Sorry if this is illegible.
These programs you're developing are so on point, and you're giving them away. Can't say it enough: Too cool.
