21–25 of 25 posts
BrowserID. please.
BrowserID. please.
No, please, keep reinventing the wheel, keep doing the same thing that everyone has been doing for the last two years. "We need a better way to do identity and auth!" "[here's a rehashed email-login system]" or "[here's a new identity management system I built instead of using an existing one. surely this one will take off!!!!!1111]"
Earlier quoted context omitted.
No, please, keep reinventing the wheel, keep doing the same thing that everyone has been doing for the last two years. "We need a better way to do identity and auth!" "[here's a rehashed email-login system]" or "[here's a new identity management system I built instead of using an existing one. surely this one will take off!!!!!1111]"
Did you just troll yourself? Wtf.
Earlier quoted context omitted.
I cannot agree with this enough. I implemented BrowserID on one of my sites once, and never looked back. Now every new project uses BrowserID as the only way to log in. It is superior to all other ways I've seen in usability, which is ultimately what counts, and integration takes all of two minutes, much less than traditional password auth. Plus, you don't even need to secure any passwords. I really, really hope it c…
How does BrowserID work in the use case of a native mobile app?
BrowserID. please.
No, please, keep reinventing the wheel, keep doing the same thing that everyone has been doing for the last two years. "We need a better way to do identity and auth!" "[here's a rehashed email-login system]" or "[here's a new identity management system I built instead of using an existing one. surely this one will take off!!!!!1111]"