Login process now requires reCAPTCHA about fantiadl HOT 8 CLOSED

Are you using the binary? This should have been addressed in #26. I uploaded a new release so please let me know if the issue persists.

from fantiadl.

I am using the source version (have also just tried the new 1.4.3 binary) and the session is still invalid. The response code is always 401.

from fantiadl.

I guess the login process has changed as https://id.fantia.jp/auth/login now fails and login is done at https://fantia.jp/sessions/signin. That requires reCAPTCHA so the only option now may be having the user provide their session cookie.

from fantiadl.

I wouldn't mind the change. If there is a place in-source where I could set the hard-coded value, that would be enough for me. If there was a CLI option, then even better.

from fantiadl.

Ideally I think it should have -c/--cookie to provide it directly and also a way to read from a cookies.txt, so I'll try to include both.

from fantiadl.

Yeah the binary has the same issue, I'll try again with _session_id when you implement it.

from fantiadl.

@EivV Please test from this branch: https://github.com/bitbybyte/fantiadl/tree/use-session-cookie

from fantiadl.

Yes, it is working now.

from fantiadl.