standardizing on openid
From the get go, I’ve always planned on using OpenID for this site. Now, to go a step further, I am now implementing the sign on and registration process solely via OpenID. Why? Because (A), I’m no Yahoo!, AOL, or Google for me to command another brain cell occupation for username and password credentials. (B), the Acegi (Spring) Security Plugin comes with OpenID support out of the box. And (C), it’s different 
. Jeff Atwood couldn’t have detailed it any better. As well as how Simon Willison did. So I’ll spare myself and my 3 readers the long (annoying, senseless) text.
I really don’t know if having OpenID as the sole key to this site’s doors would turn away possible users. At the moment, 99% of those supporting OpenID has this dual registration system. I don’t want the extra clutter. I’m choosing one scheme. If OpenID won’t catch fire, let this site attempt a spark.
You could also mention that Yahoo already supports OpenID. It’s somewhere in the user settings where you can define an OpenID id and be able to use that
Not sure if google/gmail has it too.
the only problem i have with yahoo openid is that the url that the provider returns appends a whole bunch of crap in the end value.
google supports openid via blogspot