People are bragging at Google for too much tracking, saving their cookies for to long and in general being big-brother, I think this scenario is worse… but that’s just my opint of view!

Oh, and by the way Josh – OpenID is not a “company” it’s community driven and build on a open-source idea, so it’s also your responsibility to take action and contribute in case you think there is something wrong or something could be done better.

This article makes a good point about focusing on marketing. I just wrote a post on how the OpenID movement could explain its concept better

First, I wrote about the “eggs in one basket” argument against OpenID here:

http://factoryjoe.com/blog/2008/12/26/responding-to-criticisms-about-openid/

If you use one email address for signing up for new services, OpenID is no worse for you (in fact, it could be better, since OpenID works over secure connections, whereas email doesn’t always).

Second, with regards to URLs as usernames — email addresses already play that role, and we’re working to enable email addresses as OpenIDs in OpenID 2.1. I think with MySpace, we’re going to see people finally able to think of identifying themselves by URLs. For now, for a lot of folks, it’s probably awkward, but eventually I think people will be able to tell someone else that they are “factoryjoe” on twitter.com — and voila, they’re using URLs to identify themselves.

Third, OpenID won’t just be about logins in the future. It’ll be the way that you point to your data across web services, like people do with their c:\ drives today. What do you do when you have photos on Flickr, videos on YouTube, friends on MySpace, posts on Tumblr and Twitter and you want to access them on some new service? Do you really want to specify each of those accounts individually? Using a technology called “Discovery” on your OpenID, you can point to all of them — and choose who gets to see what data.

It’s a little ways off still, but I think if you look out far enough, you can start to see how useful OpenID will become.

OpenId is fundamentally broken because it requires URLs as usernames.

But you don’t have to show people that. Yahoo are doing this really well — if you’re using Yahoo as an OpenID server, you *could* enter an OpenID, but you don’t have to. You can just enter yahoo.com.

It’s one of the reasons why I am not using OpenID myself, even though I acknowledge its benefits.

What if someone from OpenID itself hacks into my account and gets access to some other membership websites?

Perhaps, it’s the reasons why OpenID is still taking time testing and figuring out solutions for the worst case scenarios.

Does anyone know what are the developers of openid doing for it?? Its really a big issue….

@brian what do u mean bu unified registration and login experience.??

A name should be a name and nothing more! Even I can not justify why my name needs to have a networking protocol scheme and a dns name and possibly a tcp port in it.