16
submitted 11 months ago* (last edited 11 months ago) by user224 to c/sdfpubnix

I am sorry for posting about this, since it's a recurring issue, but I can't do anything else about it.

you are viewing a single comment's thread
view the rest of the comments
[-] user224 1 points 11 months ago* (last edited 11 months ago)

That was possibly done to recover locked-out users. Lemmy 0.19.x switched to SHA-1 for 2FA from SHA256 and added TOTP verification for enabling 2FA. Since SHA256 isn't supported by many authenticator apps, only generating invalid tokens, it left many users locked-out. Doing the upgrade disabled previously enabled 2FA. So it makes sense. lemmy.ml is also on RC, by the way.

[-] bitcrafter 1 points 11 months ago

lemmy.ml is also on RC, by the way.

Sure, but that is the instance specifically run by the Lemmy developers.

[-] user224 1 points 11 months ago

Sure, but it's a regular instance. They do have one that's primarily for testing, voyager.lemmy.ml.

[-] necropola 3 points 11 months ago

Sure, but the idea of running, monitoring and supporting the (final) RC on lemmy.ml is to see how it performs under real life conditions, before letting it loose in the wild. And it was properly announced beforehand. This is quite different from what SDF did with this instance.

this post was submitted on 07 Dec 2023
16 points (100.0% liked)

sdfpubnix

1330 readers
4 users here now

Fans of SDF

founded 2 years ago
MODERATORS
SDF