11–20 of 92 posts
Anything that means I won't have to use yet another password is a good thing. However I fail to see how this is useful: no sites use it, because no users use it. Let's not muddy the waters. Use openid. No excuses.
Anything that means I won't have to use yet another password is a good thing. However I fail to see how this is useful: no sites use it, because no users use it. Let's not muddy the waters. Use openid. No excuses.
I had to create an account a couple of days ago because it was the only way to log in to openphoto.me. Are there any clear differences between BrowserID and OpenID?
In its current form, BrowserID requires the user to do the email-verification dance once for each email address they want to authenticate as, and from then on they can just pick it from a list instead of doing the dance yet again.
In its ideal form, once the BrowserID API is implemented directly in browsers and webmail systems (instead of the shim at browserid.org), the user doesn't need to remember anything: they click "sign in" on the web-page, the browser brings up its standard 'pick an email address to authenticate as' dialog (populated from all the webmail sites the user has logged into), the user selects one from the list, and off they go.
What does BrowserID do that every existing OpenID provider cannot? The BrowserID FAQ says the architecture is "decentralized", but login relies on Mozilla's browserid.org server.
- validating the signed authentication token you get back from calling the authentication function. As user "decentralized" points out, this is just a convenience; your service can do this itself if you don't mind getting your hands dirty with crypto code.
- Serving the JS shim for user-agents that don't implement navigator.id.getVerifiedEmail() natively. Once browsers implement this function themselves, and webmail systems can tell the browser that the user owns a particular email address, this won't be needed either.
What does BrowserID do that every existing OpenID provider cannot? The BrowserID FAQ says the architecture is "decentralized", but login relies on Mozilla's browserid.org server.
It provides a canonical identifier for your account without compromising your identity to BrowserID-enabled services. The OpenID spec divulges who you are.
How does it compare to client-side certificates?
Earlier quoted context omitted.
It provides a canonical identifier for your account without compromising your identity to BrowserID-enabled services. The OpenID spec divulges who you are.
How does it compare to Microsoft Passport? How does it compare to client-side certificates?
Anything that means I won't have to use yet another password is a good thing. However I fail to see how this is useful: no sites use it, because no users use it. Let's not muddy the waters. Use openid. No excuses.
It looks like Firefox is not going to support OpenID, so any site that wants to take advantage of browser support will have to adopt BrowserID.
I know, I know, it's 2011, but still I feel it's unnecessarily limiting.
I'm not seeing how BrowserID differs from the standard email verification sign up. I went through the sign up process (enter email, click link in verification email, enter password, sign in with password). I also read Mozilla's 'really short version' explaining browserid ( https://wiki.mozilla.org/Labs/Identity/VerifiedEmailProtocol ) and will give the longer version a shot.
Anything that means I won't have to use yet another password is a good thing. However I fail to see how this is useful: no sites use it, because no users use it. Let's not muddy the waters. Use openid. No excuses.
I had to create an account a couple of days ago because it was the only way to log in to openphoto.me. Are there any clear differences between BrowserID and OpenID?
As far as OpenPhoto, we're pushing BrowserID because we think it's a much better authentication system than something like Facebook Connect. It's open, distributed and secure. We do have FB Connect plugins for OpenPhoto but we believe that defaultly using BrowserID is the right thing to do.
http://blog.theopenphotoproject.org/post/13914931003/the-int...
Maybe I'm stupid, but the linked article gives me the idea that JavaScript is requirement to be enabled to allow log-in. Is this true? I know, I know, it's 2011, but still I feel it's unnecessarily limiting.