So the onboarding improvements are still on the roadmap with no timeline. Good to know.
I keep coming back to the friction point because it keeps getting brushed off. Multiple people in this thread have raised it and the response has basically been that they don’t care enough about their own security, or that it’s minimal, or that this is standard everywhere. None of that actually addresses the concern.
People don’t come to this site the way they go to their bank. They come here impulsively, anonymously, a lot of the time just out of curiosity. A new user who hits a mandatory MFA setup screen before they’ve even seen what the site has to offer isn’t going to think “oh let me learn about passkeys”. They’re going to close the tab. Fewer signups, fewer people coming back, smaller community. That’s just how it works.
And here’s the thing that I don’t think has been properly addressed. The people who are going to struggle the most with this setup are also the people it would protect the least. Someone who downloads malware thinking it’s a game, or falls for a social engineering attack, or just clicks something they shouldn’t, isn’t going to be saved by having passkeys enabled. The attacker already has what they need by then. Someone raised this point earlier and it got kind of sidestepped. Mandatory enforcement doesn’t make those users safer. It just makes things harder for everyone else.
“If they won’t protect themselves, I will” sounds strong but it doesn’t really track. You can’t protect someone from their own mistakes with a login screen. You’re just adding friction for the people who weren’t the problem.
The people in this thread still confused about what they need to do before March 31st aren’t being obtuse. They’re showing you exactly what the gap looks like.
And it’s hard not to notice that this all moved very fast because it hit close to home. One incident involving a friend and within hours there’s an announcement, a deadline, a banner at the top of the site, and a Discord seminar. That kind of urgency is appreciated when it’s there. It’s just not always there. There are other improvements that affect how welcome people feel on this site that have been on the roadmap a lot longer than MFA has, with a lot less movement.
Nobody is saying MFA is a bad idea. For people who want it and know how to use it, great, encourage it, make it easy to set up. But there’s a big difference between offering something and forcing it. The better version of this is MFA as a clearly explained option inside a proper onboarding flow, one where users are actually walked through what it is and why it matters and then get to decide. That works for security without making people feel like they’re being punished for not already knowing this stuff. And that kind of onboarding could do a lot more than just explain passkeys. A new user who joins and gets the immediate impression that the site wasn’t really built with them in mind is just as likely to close the tab as someone who can’t get through an MFA setup screen. But that’s probably a conversation for another thread.