[freshhawk]

I should have been more clear. I don't like browserID because there is no route for this to become widespread except for "a significant portion of sites implement this".

You know that saying about any spam solution that begins with "well first we change email" is a stupid solution? Same issue here.

First you need a good password manager front and center in the browser. Then you start augmenting the experience by allowing better integration with the password manager through some standard. If the user already uses the functionality for every site and the experience is better on sites that implement the standard then you might actually see real amounts of integration.

[natrius]

As a web developer, I think that using BrowserID in its current state without browser support is better than implementing my own authentication. As a web user, I'd prefer to use BrowserID to sign up for sites than use individual authentication systems. A system that is better for developers and better for users has a clear path to adoption.

[freshhawk]

I agree. BrowserID is a good authentication solution.

It's not a solution to the problem we're talking about though, I'm complaining about a lack of solutions for easy credential management.

Once everyone implements it then sure, you only need to remember your email password. Unless you have multiple personas, then you'll have a bunch of passwords. And realistically there will be a lot of sites that have different systems or antiquated username/password forms.

So aren't we back were we started? I need a password manager and I'd like my browser to be aware of my password manager and help mediate. BrowserID would be a great place for it to send the appropriate password for sure.