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

Identity is hard. What is the ID you'd mandate for every website on the internet? Your bank might use your email, but your retirement accounts probably use SSN. Your message board might use a made up handle (and you don't even want it to know an email associated with you). Modern services might be using a passkey/webauthn hardware device. Some sites even have multiple identity fields, like I have bank accounts that I have to specify id/email and type of account (personal, professional, etc.) to login. The point is there isn't any single concept of identification or principle that can work for everything on the web.



You can still handle all those cases but just with three new buttons in the browser itself. Users would never have to find the login link buried in the footer or forget password only available after you fail a login. Web developers would implement where to go on each button click and unimplemented clicks on these three buttons would be like a 404 and considered broken.


Forgot password isn't enough, what if I forgot my login ID? But then it circles back to my point--what _is_ an identity? Would the button say 'forgot email'? But not every site uses email as principle ID...

It gets even more complicated when I have multiple accounts. Who lets me pick what account I want to use? Is the site responsible for that, or does the browser now need a concept of storing multiple IDs (whatever they might be) and managing them?

It gets extremely complicated extremely fast.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

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

Search: