-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NoCaptcha #68
Comments
Hi, --9kweu=KEY 9kw.eu captcha (API) key --antigate=KEY Antigate.com captcha key --captchabhood=USER:PASSWD CaptchaBrotherhood account --captchacoin=KEY captchacoin.com API key --deathbycaptcha=USER:PASSWD DeathByCaptcha account Don't know if CaptchaBrotherhood is working; captchacoin seems dead. So you would like support for: |
Kind of. Anti-Captcha supports the antigate API so it already works with plowdown for image-based captchas. The issue is more that the additional complexity of NoCaptcha means the idea of Captcha solvers merely needing an image file---as the --captchaprogram assumes---is no longer viable. At the minimum they need the site URL and the site's public key but ideally they need details of a user-supplied proxy in case Google requires the captcha to be solved from the same IP the page is requested by, the original cookies, the useragent, etc. My thinking was rather than complicate the Captcha code in core.sh any more we could just delegate to a user-supplied binary. |
The temporary proxy could be setup in the captchaprogram.
This is tricky..considering architecture point of view. Do you know an hoster site using this new NoCaptcha ? (I think this name is confusing and stupid) [EDIT] Dont know if I have been clear enough, I speak about Anti-Captcha v2 support not v1 (which is "old school" like antigate). |
CBH is gone and unavailable. Is 9kweu for both image and nocaptcha (e.g. recaptcha v2+v3) ? |
New hosters are increasingly using NoCaptcha, and existing hosters using ReCaptcha are advised to upgrade. Any work being done on support for these captchas? I'm prototyping using --captchaprogram with the extra variables been passed by Plowdown as environment variables. (For instance, this is how Anti-Captcha works with NoCaptcha: https://anticaptcha.atlassian.net/wiki/display/API/Documentation+in+English).
The text was updated successfully, but these errors were encountered: