How are the working conditions at DeathByCaptcha

With 9kw, activate confirmation (Confirm) in this case because then the error rate is lower. If necessary, reduce the timeout to 300 seconds, if the default setting is available, in addition to using priority if it is too slow.

Otherwise also common measures such as changing IP, taking a break, changing PC (uh, reinstall uh, uh use !?) and ask Google why it doesn't work again despite the seemingly perfect solution. Try Google account if necessary.

Quota:

Originally Posted by Jiaz

In our experience, the error rate at 9kW is simply too high.

9kw moves between 75% and 90% with correct solutions on average according to its own statistics (60 days) and the feedback as from JD2. The tendency due to the measures (also bugfxies) is increasing recently.

The so-called error rate is often a justifiable solution, but in individual cases a perfect solution is required. PhantomJS may be a bit more picky than in a full-fledged browser. Completely wrong solutions are less likely to be found.

Repeated completely wrong entries in the system lead to the fact that the respective user is completely excluded. Possibly report to the support of 9kw if a user has not yet been noticed. Credit is also generously reimbursed in individual cases with concrete help to push the answer quality further towards 100%.

Quota:

Originally Posted by Jiaz

Automated services simply do not provide the required reliability of correct answers





Quota:

Originally Posted by Jiaz

The best option is in the browser. Remote (via PhantomJS) is no longer that * optimal *. We are investigating solutions on how to solve the problem remotely in the browser, until then only the PhantomJS detour remains

Either only via browser add-on or mobile app or as a desktop app with an integrated browser. Otherwise, the security of normal browsers does not allow you to access the respective website.
__________________
Join 9kw.eunow and let your JD continue downloads while you sleep.