`auth send-email` may soon require recaptcha

[wh0]

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.

[khalby786]

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]

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]

do you have any references on how newpipe does it?

[wh0]

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

[wh0]

I think this has just happened.

$ HOME=/tmp/fake-home snail auth send-email [email protected]
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]

added a note on the website 💁

[wh0]

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