TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Passwords have problems, but passkeys have more

49 点作者 duncans8 个月前

3 条评论

p0seidon8 个月前
This rant is utterly factless and at an absolute novice level. It is correct that building a passkey-first system (without fallbacks) is not possible today, but that's like going all in on Google Social login and then ranting about why not all users can access the system.
评论 #41498470 未加载
tbeseda8 个月前
&gt; we built the early authentication system entirely around [Passkeys]. It was not a simple setup!<p>it is though<p>&gt; Handling passkeys properly is surprisingly complicated on the backend,<p>it&#x27;s not though<p>&gt; but we got it done. Unfortunately, the user experience kinda sucked,<p>true<p>&gt; so we ended up ripping it all out again.<p>fair enough, but don&#x27;t couch that in misdirection about the spec and work involved.
klingoff8 个月前
The relying party not being able to assume the user can take one secret with them is a feature that comes with a cost.. The lack of a reference correct relying party library in each language is a reason that cost is too high.