wh0/snail-cli

`auth send-email` may soon require recaptcha

wh0 opened this issue · 7 comments

wh0 commented

image

They've added a recaptcha widget to the magic code form.

I tried going through the flow just now with Snail, but it was still working. But it may be a short matter of time before they add server-side verification of the recaptcha.

But it may be a short matter of time before they add server-side verification of the recaptcha.

Would it be possible to bypass this?

Yonle commented

I heard that there's a trick to solve this issue by getting ReCaptcha code from client localStorage then send it to server. But i didn't think that method will work like how NewPipe grabs ReCaptcha code

wh0 commented

do you have any references on how newpipe does it?

wh0 commented

extra note: this applies to the recently added auth password too, the web equivalent there also bearing a captcha lately

wh0 commented

I think this has just happened.

$ HOME=/tmp/fake-home snail auth send-email user@snail.example.com
Error: Glitch auth email response 500 not ok, {"message":"Internal server error"}
    at Command.doAuthSendEmail (/app/src/index.js:421:22)
    at process._tickCallback (internal/process/next_tick.js:68:7)
wh0 commented

added a note on the website 💁

wh0 commented

updated the instructions more thoroughly. that's all we can do