Re:OpenID Is Why I Hate The Internet
by derefr on Tuesday September 02, 2008 @05:13PM
(#293218)
I can bet you that I could fix all the problems you have with this story with one teensy little change: allow the OpenID providers to recieve "theme" information (basically a base URL for CSS files and images) from the sender site. Then the registration page would look like it was part of your site. Then, when rendering the login page/div, check whether the user is already logged into the provider using some onunfocus AJAX, and then smoothly drop the password field down underneath it if it's needed. (of course, then, you have to handle sending that password to that provider in a secure way, but we're focusing on user-persoective advantages now, so, like with IE6 support, a lot of sweat is to be expected.) from the user's perspective, if they don't know what the little "OpenID-enabled" icon next to the username box means, they can just go along with their business, and everything will happen as usual.
The only problem at this point is the URL username. To answer that, think about what, for example, gmail does: when you have a gmail.com address, you can drop that part and just use the username part of it. Likewise, I'd allow my users to strip off the domain part of whatever my "preferred provider" was, and just say that the "foreign IDs" basically need a "passport stamp" to get in--an attached domain name.
The only problem at this point is the URL username. To answer that, think about what, for example, gmail does: when you have a gmail.com address, you can drop that part and just use the username part of it. Likewise, I'd allow my users to strip off the domain part of whatever my "preferred provider" was, and just say that the "foreign IDs" basically need a "passport stamp" to get in--an attached domain name.
Still too confusing?