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

What exactly are OpenID usability issues? I personaly prefer to use OpenID where it is available, yet I don't use any login provider but a php script on my own website.


I'm not sure myself. I've used claimid.com for years and have never had a problem -- love that it's saved me creating dozens of one-off accounts.


I use a TondioPlug[1] as a provider, and I've never had a problem with it. It is simple to use and doesn't require me to know anything about how OpenID works.

I suspect that until things like a TondioPlug become useful for a lot of people, (if they ever do) asking people to be their own provider will be a lost cause.

[1]http://www.tonidoplug.com/tonido_plug.html


The problem is that the number of people hosting their own OpenID solutions is, and will be, rather insignificant.


It doesn't matter when yahoo, google, aol and more offer openid, it's just a click on a button, what could be easier than that? I agree that entering a whole URL is horrible though but that's not how I use openid, I just click on the google button and that's it, just like facebook or twitter connect.


StackOverflow is a good example (IMHO) of OpenID login done right. It's so easy to sign up for a StackOverflow account, and I don't have to remember or write down yet another fucking password!

IMHO, one of the things they do correctly is that the user doesn't have to remember an OpenID url in most cases, just click on the logo for which of your likely ID providers (Google, Facebook, Yahoo, etc.) that you want to use. What could possibly be easier or friendlier for the end user?


StackOverflow is a good example (IMHO) of OpenID login done right.

The problem is that StackOverflow is also about the only example of OpenID done right, or done at all...

Yes, there are a few others. But at least in my internet usage I hardly ever run into one. I can't remember having used my OpenID for any site other than SO in the past couple years.


Other examples of user-friendly OpenID login pages:

* Tripit.com only supports Google, Google Apps, and Facebook, but it's very end-user friendly to use any of those three.

* Catch.com, like Tripit, supports Google and Facebook OpenID logins.

* mindmeister.com supports Google, Google Apps, or a generic OpenID login.

* springnote.com supports a number of openID providers including generic OpenID. This one is actually an even better example than StackOverflow of an end-user friendly OpenID login/signup page.

Those are just ones I pulled from my Google account settings page. I'm sure there are other good examples out there.


It shows that it's possible. The question is then why others don't implement it well. Obviously it's not worth it to them, but I think that say more about those doing the poor implementations than it does about OpenID.


Many of these providers have bugs and quirks. It is nontrivial to support them all.


Couldn't that be obviated by wrapping it much as jQuery makes browser support less painful?




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

Search: