News for hackers. Stuff that matters.
Re:How BrowserID differs from OpenID by Osiris on Friday July 15, 2011 @11:41PM (#2770055)
I do like their last point that the system is designed to be integrated directly into the browser. That avoids the issue of OpenID requiring that a popup be displayed to the user from their OpenID provider, which was a significant usability problem.

Having the browser handle the authentication makes for a much more seamless experience.

Re:How BrowserID differs from OpenID by wmf on Saturday July 16, 2011 @12:18AM (#2770106)
If you have browser support, the browser could log you in to your OpenID provider so there'd be no popup.
Re:How BrowserID differs from OpenID by simcop2387 on Saturday July 16, 2011 @03:22AM (#2770326)
The problem is that OpenID doesn't specify that part of it. I could have one that needs a key-fob token to authenticate there.
Re:How BrowserID differs from OpenID by pornel on Saturday July 16, 2011 @08:15AM (#2770631)
You can authenticate any way you want, so that's not a problem.

If NAT and firewalls weren't such PITA, browser could even act as an OpenID provider for itself (e.g. Opera Unite makes it possible).

The problem with OpenID is lack of discovery. AFAIK there is no way to advertise that website supports OpenID login and where it should be submitted, so browsers are unable to have integrated UI for it.

Re:How BrowserID differs from OpenID by mbreese on Saturday July 16, 2011 @10:57AM (#2770881)
Since it isn't specified as part of the spec, browsers would potentially have a different implementation for each OpenID provider, so yeah, that's a problem.
Re:How BrowserID differs from OpenID by pornel on Sunday July 17, 2011 @08:25AM (#2773167)
Client<>Provider authentication method is not visible in the in OpenID protocol between Provider<>Consumer. Can you elaborate where the problem lies?

Why would different auth methods in browsers cause problems, when different provider's methods don't?

AFAIK client auth method is invisible and irrelevant, especially in the case where client and provider are the same thing (the browser).

In fact, in-browser OpenID (where browser is the provider) could skip client authentication completely and just say "yes" to every consumer (because browser knows and trusts its own identity).

Re:How BrowserID differs from OpenID by wmf on Saturday July 16, 2011 @01:27PM (#2771158)
Realistically everyone is going to become compatible with whatever the browsers support.