Looking for captcha solving software? There are 2 options: Captcha Sniper and Captcha Breaker. Captcha Sniper has been around longer, and is cheaper and is run by a two-man team that includes well known BHW guy Mikey (mikeybobikey). Captcha Breaker is the new kid on the block. CB comes from Sven @ GSA, the maker of the famous Search Engine Ranker software. Sven's designated rep here is the indefatigable S4ntOs. Below are the results of 48 hours of testing I did with both solvers. Let's cover the basics. The testing was done on my VPS with Berman Hosting. I am a happy Berman customer and if you're looking for a VPS they deserve consideration. Each solver was run in conjunction with the aforementioned Search Engine Ranker software. If you aren't familiar with it you probably should be. For this project I ran a campaign on 4 sites with 3 tiers apiece. Time for some numbers. Captcha Breaker vs Captcha Sniper mano a mano: whose cuisine reigns supreme? Captcha Breaker alone for 24 hrs: SER reports 32420 link submissions, 557 verified SER reports 17438 captchas were assigned to CB, 2378 to AskMeBot* CB says it "recognized" 11730 of 14938 with average time of 0.247. Catpcha Sniper alone for 24 hrs: SER reports 30978 link submissions 606 verified SER reports 21262 captchas sent to CS, 2266 to AskMeBot* CS says it solved 10788 solved with an average time of ~0.538 * AskMeBot.com offers a pay-as-you-go solution for so-called "text captchas". Questions like "Is the sky blue?". Cost is $5 per month and so far I'm pretty happy with it. Before I analyze I gotta say I expected CS to win this. I'm not a CS fanboy. My expectation simply derives from CS having been around a lot longer. Captcha solving is a decidedly non-trivial task. You don't see coders hacking around with stuff like this for the sheer fun of it. Experience counts for something. A look at the forest says this contest is a tie. The submitted link count goes to CB by about 5%. The verified goes to CS by about 5%. I consider both to be trivial differences that could easily be reversed were I to run another test. For me a tie means CB is the effective winner. CB is the new kid on the block and to get a tie against more experienced opposition suggests that in the future it will probably overtake CS or at least stay even. My brother-in-law sometimes calls me Mr Qualifier, because he says I can't answer even the simplest of questions in under 35 words. Let's qualify these results a bit. There are a large number of captcha types. I'm sure that at some types CS is better then CB and vice versa. Test results are in some measure dependent on the types of captchas encountered on the platforms and targets. I'd bet that on my first tier my projects probably don't share so much in common with the average SER user. On the lower tiers my stuff is going to look a lot more like yours. Your mileage may vary. Now let's look at the trees. The SER stat bar says it assigned nearly 4K more captchas to CS then CB. I have no idea why this would be. Given the overall results I'm not sure it matters. Maybe Sven/S4ntOs can offer a guess on this. Average solve time looks like a big edge to CB. Maybe. Depends on how the solving time is calculated by each program. SER isn't telling us how fast each solver returns an answer. These times come from the solvers themselves. Since the big picture numbers are similar I'm guessing the solve time differential isn't really as much as it appears at first glance. Or as my BIL would put it, I'm putting a qualifier on this. I had meant to make this exercise a 12 hour test, not 24. I screwed up in the CS testing phase. After testing for 12 I didn't take the proper steps in SER to change over to CB and ended up getting another 12 of CS. I threw up the numbers for the 2nd 12-hour block and things looked up so much for CS that Sven suggested (half-jokingly I think) that Mikey had contacted me to help goose things along. That didn't happen. Mikey has spent some time with me personally and I'm very appreciative. But no help was offered on this exercise. Still the improvement was stark enough to take a look. In the first 12 hours CS racked up 12055/227, in the 2nd 12 the numbers were 18923/379. Big improvement. More then 50%. I've been stopping SER and resetting its stats and futzing with the captcha settings every 12 hours. When I started it was on a schedule of 10:15am EST to 10:15pm EST. Now with the time at breaks spent futzing I'm up to about 11:30 as the break point. What I realized for EACH solver the prime time was from the AM to the PM. Overnight numbers are relatively weak. This result may be *far* more important then which solver is used. It suggests that perhaps - I qualify everything don't I?! - the VPS's CPU should be dedicated to other tasks at some point in the overnight hours. If I'm seeing results this strong I'll bet you will too. Implications? I'm using SER to scrape for new targets. Maybe what I should be doing is turning loose Scrapebox on the the search engines to find new targets during those hours when SER is less productive. If SER is producing a third less submissions during a large 12 hour block its stands to reason that the performance hit is even more severe in some subsection of that block. That would be the time to run SB to get fresh targets. With the target scraping done for it SER would be even more productive during the fertile hours of the day. Testing isn't done yet. GSA SER is capable of sending failed captchas to a *second* provider. Next up I will look at how CS & CB can work together. In the meantime I'm sure you have some questions. Fire away! Oh, one more thing. The thread title. I actually saw a live Texas Death Cage match once. At Cobo Hall in Detroit. My grandfather wanted to go, and my dad offered - very, very reluctantly - to take him along with me and my brother. The feature event pitted Chief Jay Strongbow against someone I don't recall. Am pretty sure Strongbow won. He was carried from the ring on a stretcher, rose from the dead and hoisted the stretcher over his head and conked his opponent. My dad wanted to disappear. Don't think he ever willingly spoke of it again.