Hey. a small bird told me that you guys might not be cleaning the input you are receiving from the user. This might be a problem if the user is autofilling their username into the form with a password manager and their password manager has spaces saved where their credentials are saved.
Trying eliminating spaces and tabs from the data your receive from the user, like their username or bluesky handle. That might fix a lot of unintended usability problems with your login.
Yeah, that does seem like a likely culprit here. Checking the logs on our backend I didn’t see any obvious whitespace but that doesn’t rule out more devious unprintable characters
So, sanitizing input may not be the only culprit but it was definitely one of them. After I helped someone create an account, I tried creating one myself. I had to use the sign up option more than once before actually logging in worked.
Some more debugging might be required to find out how the information is being handled. I hope this helps and wish you the best.
lmao tangled.sh/@tangled.sh/...
seen quite a few of these in the wild bsky.app/profile/shri...
fix will be included in the next release github.com/bluesky-soci...
unicode ltr chars strike again
niiiiice!
Oh my god I have done the Linux highlight and middle mouse button paste so often on atproto oauths and accidentally copied this character, finally someone is bringing this up
