Yes.

I noticed my authenticator app (KeePassXC) offers the ability to customize the TOTP parameters (SHA function, time step, code size). But no combination of settings seems to produce a valid code.

I assume Lemmy uses the suggested defaults in the RFC 6238 standard?

Connect, Sync, and Boost all told me to go kick rocks.

Evidently, whatever happened, it doesn’t seem to be an issue with your platform.

I seem to have been screwed over by TOTP.

Hearing that this update was supposed to make borking your account harder to do when setting it up, I enabled it. Put the secret in my authenticator app, got my six digit code, and away I went.

Now, a few days later, having changed nothing on my end, Lemmy.ml won’t accept my TOTP code. My session token on desktop is expired so I can’t remove it now.

Currently my only lifeline to this account is my logged in session in Voyager, which, as far as I can tell, cannot access the TOTP setting. (Or any profile setting, for that matter… am I just stupid?)

No email to recover from, either. That’s on me, I guess. Ugh.

Not sure what my recourse is, if I even have any.

Thank you for the suggestion of Voyager, I have installed it and it looks quite nice!

Creators of Lemmy, owners of this instance, and creators of the Jerboa app are all the same people. As I understand it, Jerboa won’t be getting an update until they’re happy with the stability of the update to Lemmy itself. Lemmy is getting all the focus first. Also, no sense in pushing a client update for a server update that itself is not finished.

Getting really annoyed at that error toast in Jerboa, though, not gonna lie. And not being able to post on mobile. At least I can still read posts and comments, though. Hopefully the patch will release soon.