It looks like you're new here. If you want to get involved, click one of these buttons!
All GSA SER does is calling there decaptcha api on 127.0.0.1:<port you set in there config>.
So if it does not work, blame them. And yes, there service doesn't seem to be that stable.
A regular problem with mega ocr is when you first sign up, the accounts take a while to get set up.
Best and quickest way to get hold of them is via Skype. They are on the Belize time zone, what ever that is
Skype contact is mega.ocr
You might have a program using port 80
IIS service does and I have to stop it every time I reboot my vps
The best way for speed and believe me, I have spent time testing
Run cb as first captcha option. That way cb will whip through captchas at the mega speed it works
Then mega ocr as the second option to mop up what cb cant do
Make sure you don't have cb running as a webserver
I just run mega ocr as is
Never tried asking for a different ip for the server used
Im more than happy with the daily results I get with ser and have had very little down time with mega ocr
No idea in all honesty. But my daily verified is good
The only way you could check what the success rate is like is if you check each and every captcha as its answered
Did best part of 200,000 verified one day last week, which I think gives a good indication of what can be done and the system works
When Im doing 100,000 to 200,000 submissions in ser in a day, checking the answers is physicaly impossible
Another bit I forgot to mention is the order you start cb and mega ocr
Start cb first. Let it finish loading up and then start mega ocr
Then check that mega ocr
Im sure Sven will correct me if Im wrong on this
If you send captchas through cb, cb waits for that captcha to be answered before doing the next captcha
Just glancing at mega ocr and my own average solve time per captcha is about six seconds
In cb, my average solve time is about 0.24 seconds
Doing it their way will, will bog you submissions down
I don't run cb as a webserver. No need to, with how Sven has programmed it
In ser, I have mega ocr set as my second service
That way cb does what it does best and flies through captchas
Its not waiting on the answers from mega ocr, since that's being run as an independent captcha service
I had to reset my vps yesterday after doing the windows updates. But since doing the reset, out of 74,000 captchas sent to mega ocr, 53,000 were answered.
Im a tight git. Run the cheapest basic package
Don't want to be building too many links in a day and I do 100,000 verified a lot with nothing more than cb and mega ocr
I push the 100,000 limit on IncredibleIndexer most days
The way I think it works
Active threads is how many connections at one time to their server
Software threads is cued up captchas
That's my own understanding of how it works
The basic package is all I run
Roughly 2/3 of my captchas are done with cb, the rest with mega ocr
LpM looks good, when I used to do 250,000 submitted in a day, the numbers were impressive.
But, the end goal, has always been verified
You see the posts on here all the time about high submitted and low verified.
When I kill engines with low performance, I use the verified stats and common sense
If you have a 70% success rate and only 50 verified, why waste time submitting to that engine, if you have another engine with 5,000 verified and a 30% success rate. All it means is the latter engine has far more targets ser can find on the net and more places to submit links
I ran a test, by mistake and it gave surprising results, then logic kicked in to explain why
I set one project, on all tiers, to automatic verify, rather than a custom time of 1440, like most people do
Something I will admit to never fully understanding why so many wanted the option added and just went into silly sheep mode and used it myself. I know there was some profound logic spread at the time.
After a month, I cleared all the dead links every where.
That one project, had more verified on every tier. About 10k per tier, that were still live.
The logic part, is a lot of sites will limit how long you have to verify or complete a registration
Custom footprints, in the early days I did use them.
But, with the way ser can be updated. Keeping up with the changes can be a time killer
I gave up on the idea after spending a day making changes, only to have the same engine files updated the next day and from memory, two days later
Needless to say I gave up the will to live and decided to stick with the standard ones used in ser
megaocr and ser engines. If you look at the thread on here, I did show the results you can get when some were moaning about poor rates.
The stats I shared there, were with nothing more than cb and mega ocr
There is one engine I leave unchecked. Thats FC2
Running mega ocr in ser. I run it as a second service in ser rather than through cb
If you run it through cb, cb will wait on each answer before moving onto the next captcha
This way, you run them as two separate services.
cb whips through its captchas and mega ocr is then left running at its maximum threads