Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I would say because it relies on an hardware key, which few of your users are going to have anyway. Any tech requiring an hardware component is going to be much slower to deploy.

I know there is still much interest in deploying it for internal/employee authentication in large organizations where you control the app login and the employee hardware. Some organizations that wrongly deployed multi factor auth based on SMS have realized that was a poor choice and are looking for alternatives.



> I would say because it relies on an hardware key

This isn’t true on Apple, Google, or Microsoft devices which have a trusted hardware store – I use my MBP’s Secure Enclave for 90% of my logins since it’s just a Touch ID check.


Well, there is a hardware key, it's just that it's the device you're using.


In other words, having a hardware key is not a real barrier to use.


The opposite. It's a barrier because most users don't have one.


…and yet most users are browsing using a device which itself contains a hardware key… and thus it is not a barrier.


What if I don't like viewing web pages on a phone?


Right, but that gets rid of the objection: there’s no second thing to buy and carry around, it’s faster, and it’s more secure than the alternatives.




Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: