3 ms·
I've had precisely one "issue" with Twitter logins in the last almost 14 years (and I have used it around the world (either physically in the country (like when
by warrenm 3y ago
I've had precisely one "issue" with Twitter logins in the last almost 14 years (and I have used it around the world (either physically in the country (like when I first signed up while living in Singapore), or via VPN), on mobile devices and desktops
And that was this week when trying to login on a new browser on a new laptop, but couldn't provide the 2fa from my authenticator app because I forgot to setup a replacement authenticator token when I changed phones a couple years ago
And the fix was simple: disable 2fa (from a browser already logged in), then enable 2fa, add it to my authenticator app, and go about my day
Took about 30 seconds
I cannot recall having gotten a captcha with Twitter (or, now, X) since I first signed up in '09
Are you sure you do no have sandboxing or javascript blocking or the like enabled in your browser that you are trying to sign-on in?
- 5350-uiop-1130 3y agothanks. no it's happening on different IPs, different browsers. maybe on every 2nd or 3rd refresh it locks the account and forces the captcha the process. and the captcha process itself is the most difficult i've ever seen. i'm not using 2fa btw.