Skip to content
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

Workaround reCAPTCHA #886

Closed
Perflyst opened this issue Nov 7, 2019 · 7 comments
Closed

Workaround reCAPTCHA #886

Perflyst opened this issue Nov 7, 2019 · 7 comments
Labels
enhancement Improvement of an existing feature

Comments

@Perflyst
Copy link
Contributor

Perflyst commented Nov 7, 2019

Since this was only discussed in the invidious room this issue is now created.

Googles "block" is always done through presenting the user a captcha.
After solving it, the block is gone for 3 hours.
The invidious user should have the ability to solve this captcha for the instance if this is possible.

@TheFrenchGhosty suggested https://anti-captcha.com/ which has an API to solve Captchas and it is very cheap too. This can be used to automatically solve the captcha each 3 hours.

Let's calc
$ Price per 1000
min: 2.36, max: 3.37

I will use 3$ / 1000 reCAPTCHAs
1 CAPTCHA -> 0.003 $
1 day = 8 CAPTACHAs -> 0.024 $
7 days = 56 CAPTACHAs -> 0.168 $
30 days = 240 CAPTCHAs -> 0.72 $
1 year (365 days) = 2920 CAPTACHAs -> 8.76 $

@elypter
Copy link

elypter commented Nov 7, 2019

this sounds reasonable but it is impossible to predict youtubes behavior in the future und thus it could result in unexpected drastic increases of captcha solving. if it is technicaly possible without to much work just let one random user solve it and make it an opt-in option in the preferences. even if just 1% of the users chose to be willing to do this then it would still happen very rarely for the individual volunteer.

@omarroth omarroth added the enhancement Improvement of an existing feature label Nov 8, 2019
@omarroth
Copy link
Contributor

omarroth commented Nov 10, 2019

Added with 71bc9ee. If you have an API key you can add it to your config as captcha_key: aaaaaaaa.

Through some more testing it does not appear to consistently resolve the issue for blocked instances. It may be possible the issue is in submitting or saving cookies between requests.

The invidious user should have the ability to solve this captcha for the instance if this is possible.

It is not possible to embed or present CAPTCHAs to users.

@Perflyst
Copy link
Contributor Author

Thank you. As already mentioned in the chat the longest time the instance was working through anti captcha was 4 minutes.

Also the "redirect captcha block" is not handled yet

$ curl -s https://www.youtube.com/watch?v=QmyhcjpsF6E -4
<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">
<TITLE>302 Moved</TITLE></HEAD><BODY>
<H1>302 Moved</H1>
The document has moved
<A HREF="https://www.google.com/sorry/index?continue=https://www.youtube.com/watch%3Fv%3DQmyhcjpsF6E&amp;q=EgRf2BjmGJKaoO4FIhkA8aeDSwTc2PRqzI476Aa-2iHKmGCVxucTMgFy">here</A>.
</BODY></HTML>

@Perflyst
Copy link
Contributor Author

Perflyst commented Dec 5, 2019

Both endpoints were added, workaround reCAPTCHA is successful.

@haizrul
Copy link

haizrul commented Feb 7, 2020

1 day = 8 CAPTACHAs -> 0.024 $
7 days = 56 CAPTACHAs -> 0.168 $
30 days = 240 CAPTCHAs -> 0.72 $
1 year (365 days) = 2920 CAPTACHAs -> 8.76 $

My anti-captcha usage statistics are doubled from what you suggest. Is this normal?

Opera Snapshot_2020-02-08_013443_anti-captcha com

@TheFrenchGhosty
Copy link
Member

@haizrul What you spend depend on your bid, and it doesn't look that different

@Perflyst
Copy link
Contributor Author

I have around the same usage, 15-20 captchas a day. Still 0.04$ a day is nothing.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Improvement of an existing feature
Projects
None yet
Development

No branches or pull requests

5 participants