Indie iOS app developer with a passion for SwiftUI
Current 2FA implementation in Lemmy is a bit janky with the risk of being locked out.
First things first: DO NOT UNDER ANY CIRCUMSTANCES LOG OUT UNTIL YOU’RE 100% SURE YOUR AUTHENTICATOR WORKS AND THAT YOU CAN LOGIN USING ITS GENERATED 2FA CODE
Now that that’s out of the way, here are some steps to follow:
If you can’t get it to work then you can disable it in the window you’re still logged into.
If you share which authenticator you use, people might be able to give you more specific instructions to get you through step 1.
Whatever you do, don’t log out. You will be locked out!
Unlike most common implementations, there is no built in step to verify if you can successfully generate a TOTP before 2FA is fully enabled.
Pro tip: if you do insist on using Google scroll to the bottom until you see a notice like the one below.
You can then click on the complaint to see the URLs that were removed.
They’ve wisened up a bit and now require a (throwaway) email to access the links, but chances are that if you’re looking for something more obscure, the link you seek is still there.
It’s hard to explain without a similar sound existing in English.
The “eu” part in “neuken” and “keuken” is pronounced like the French word for 2: deux.
The ”-ken” end of both words is almost exactly pronounced as the word “cunt” without the t.
“de” is pronounced like “the” but with a “d” sound, like “duh” but not in the exaggerated way you’d do it when you’re mocking someone. And “in” is the same pronunciation as the English one.
So putting that all together, I’d write it out as follows if I’d like to make it pronounceable for an English speaker: “neuxcun in duh keuxcun”