Is the settings page broken for anyone else? I’ve tried to change my language and enable 2FA on both Firefox and Ungoogled Chromium. The button just spins for a split second, and then nothing. The language settings worked before the upgrade, so I’m wondering if anything broke?
what’s supposed to open from the
otpauth
URI scheme? i have keepassxc and nothing happened. i had to manually copy the damn thing and there’s no way to confirm whether these codes work unless i log out???wait i can’t even log out. i have to clear my cookie manually.
Use incognito to test if it works before trying to log out!
don’t know why private browsing didn’t occur to me, but i ended up having to manually delete all storage and cookies related to lemmy.blahaj.zone
anyway i’m fine i guess. this is a very poor implementation of 2fa though.
This really is a terrible implementation of 2FA. I just tried it out.
I use Bitwarden and it didn’t pick up the URI scheme at all. I fed the hash into it, and could generate a code. Trying to login through incognito was a failure. I was able to go back to my original window and remove the checkmark so I could still access my account. There was no prompt to remove the code or enter a password. I think I will take that one to GitHub issues.
It’s definitely a Lemmy issue. I had the developer console open when trying to save settings. I got a
400 bad request
on the JSON that gets generated by the save button.Cookie redacted.
Response Header
HTTP/1.1 400 Bad Request Date: Tue, 04 Jul 2023 10:28:30 GMT Content-Type: application/json Transfer-Encoding: chunked Connection: keep-alive Server: nginx vary: accept-encoding, Origin, Access-Control-Request-Method, Access-Control-Request-Headers access-control-allow-origin: https://lemmy.blahaj.zone content-encoding: gzip
Request Header
PUT /api/v3/user/save_user_settings HTTP/1.1 Host: lemmy.blahaj.zone User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/114.0 Accept: */* Accept-Language: en-US,en;q=0.5 Accept-Encoding: gzip, deflate, br Content-Type: application/json Content-Length: 914 Referer: https://lemmy.blahaj.zone/settings Origin: https://lemmy.blahaj.zone Sec-Fetch-Dest: empty Sec-Fetch-Mode: cors Sec-Fetch-Site: same-origin DNT: 1 Sec-GPC: 1 Connection: keep-alive Cookie: [REDACTED]
The response tab had something interesting to me.
{"error":"bio_length_overflow"}
I’ve had the same bio since I started my account here, and nothing had changed except for my languages a few days before the upgrade.
Editing the bio to be blank and then pasting the contents back solved my issues. That brings me to a new question. @[email protected] is there a character limit on bio lengths that the frontend isn’t showing?
My issue is fixed, and I am leaving this up for anyone who has the same.
Edit: After more testing (see: removing one character at a time), I found the limit is 286 characters, including new lines and formatting.