Facebook joins OpenID Foundation Board
openid.net
openid.net
It will be good if people can start logging on to "real" sites with an OpenID. But I have a feeling Facebook only wants OpenID so that people can use their facebook password to log on "everywhere". This is how Google "supports" OpenID also.
Further, OpenID is about positively identifying somebody online. Since Facebook has one of the stricter naming policies online, isn't that a good thing that they want to make Facebook IDs more openly available?
It will become very worthwhile when major sites start letting me use it to log in.
(I always compare OpenID to email. Going with that analogy, right now, every site gives you an email address that anyone can send to. But each site will only send e-mail to its own addresses, completely eliminating any value.)
It's good for smaller sites, though. If I want to bootstrap my users and I'm going for a Facebook-like crowd, having instant access via Facebook ID might be nice to have.
I'm not really a heavy user of it, I probably wouldn't have joined - but they make it ridiculously easy to register.
We're taking on OpenID 2.0 as part our our development as a consequence. I know it has it's drawbacks, but as you say, getting the penetration up front is key.
Either way - hopefully a sign of things to come.
It adds nothing. First it was an address book in the midst of a sea of similar address books. It added OpenID to gain an "edge" and it got publicity despite its still having a meaningless featurelist. Plaxo 3 added Pulse, which is just a watered-down FriendFeed, which is a pretty watered-down site to begin with. It's ugly - it was obviously design-by-committee, which made it incredibly harmless and hideously generic - it adds nothing, and it has uglier ads than most of the sites it's ripping off. The name is terrible. It's the ultimate example of the meaningless short name.
Facebook can easily continue to do whatever they want with their API and still do OpenID. It would be nice, however, if they did a hybrid OpenID/OAuth flow and then have an OpenSocial API that you could get access to with the oauth token. The user experience would be pretty much the same.
[edit] Ah I see why you wrote that. I was writing/thinking about two protocols at once and came out with an incoherent comment.