-
Website
http://avdi.org/devblog -
Original page
http://avdi.org/devblog/2008/04/12/why-your-social-website-should-support-openid/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
bryanl
4 comments · 3 points
-
François Beausoleil
1 comment · 1 points
-
obiefernandez
1 comment · 2 points
-
gambling
3 comments · 2 points
-
Jakub Narebski
1 comment · 5 points
-
-
Popular Threads
-
Simplicity is Complicated
1 week ago · 25 comments
-
Double-Load Guards in Ruby
2 weeks ago · 4 comments
-
Array-ifying Values
2 weeks ago · 3 comments
-
ISO8601 Dates in Ruby
1 week ago · 2 comments
-
My WebOS Makefile
2 weeks ago · 2 comments
-
Simplicity is Complicated
OK, so the blog post, "Do Users Really Even Exist?"
http://gilesbowkett.blogspot.com/2008/03/do-use...
The answer is no. Users are a convenient fiction. What actually exists are logins. OpenID assumes users map directly to logins. Because of this it is only useful to Web developers. In real life people share logins with each other or have more than one login. That's my point in the blog post. You dissed it on Twitter saying it was an interesting theory, but that was silly. It's not an interesting theory. It's an observation of the disconnect between how Web developers like to imagine people act and how you can actually see people acting in the real world.
OpenID is Web-developer-centric and based on an assumption that is wrong. It would be cool, IN THEORY, like Communism, but in reality, it's just ridiculous BS. Theories based on ideas which are repeatedly shown to be factually incorrect are theories which will not get you anywhere no matter how pretty they turn out to be.
Also, Microsoft tried to do an OpenID style thing years ago, and failed. Here's the pattern with OpenID and Passport: developers decide it should exist, they build it, and nothing happens. Whenever you have a pattern like that, it means that the real world displays characteristics that people are repeatedly failing to recognize. This is similar to micropayments. Several attempts at micropayments failed in a row before developers decided to give in gracefully and stop providing a technology that the world clearly didn't want. After a while Clay Shirky figured out why:
http://shirky.com/writings/fame_vs_fortune.html
One day Clay Shirky will figure out why OpenID never happened either. And it'll be really freaking interesting to read. But until then OpenID really isn't worth taking very seriously, and when it becomes taking very seriously, it'll only be as a way of leveraging Clay Shirky's remarkable brain. OpenID in and of itself is really not worth taking very seriously.
QED.
http://idcorner.org/2007/08/22/the-problems-wit...
I'm not concerned so much about the issue of centralization - I am my own OpenID provider. (And yes, I realize that I am in the minority in that). The fact that I *can* be my own provider, though, makes OpenID less centralized than previous attempts at single sign-on.
I could probably be convinced that OpenID is not the best solution, although it would take concrete examples of better solutions. What I am not interested in is people telling me that it serves no purpose. It serves me well, and if it is flawed I want to hear about improvements, not hand-waving about how nobody needs it anyway.
"The idea that I would want the same login at LiveJournal, where I post my personal soap operas semi-privately to very old friends with too much time on their hands, and Digg, where I post my own blog entries to promote them to the worldwide professional developer community, is flawed at best."
This is why a good OpenID provider (such as MyOpenID, who I use) will allow you to create personas. You can share as much or as little as you like between your various online accounts. Please don't rag on something until you're aware of all its aspects.
While I certainly respect Stefan Brands, I don't agree with many of the points he made as I later blogged. http://daveman692.livejournal.com/310578.html