I've been looking at the whole OpenID thing vaguely squinty-eyed for a while, since while we've done a great deal to improve upon LJ's implementation thereof, it's still not anywhere near what I'd consider easily usable. We have this suggestion for integrating the concepts of OpenID login and "named anonymous"/pseudonymous commenting level (ie, you give the system a name and a URL to identify yourself as), which I think will be a step forward, but I let this suggestion through despite the similarity because of what I view as the key difference here, namely changing the various login/identification options in a context-sensitive manner on an account-by-account basis depending on the crosspost settings.
Generally speaking, though, we're ideologically against doing things that refer to one specific other service (such as, but not limited to, LJ) -- solutions should be generalizable for any external site as much as possible. One thing I've seen elsewhere on the OpenID-speaking internet that I really like as a solution is some sort of box/dropdown/display/etc that shows the icons and/or names of popular OpenID-enabled services, as a "enter your username for thus-and-such service here", and the system then constructs the OpenID URL for you behind the scenes.
The thing I'd be concerned about with your suggestion exactly as it's presented is that we already have people who expect to be able to log onto DW with their LJ username and password (and get very irate when they can't) -- it's a very common problem among LJ clonesites/DW-based code forks, and a major source of confusion and anger. As presented, I think your suggestion would increase that confusion instead of making it better, so I'd be more inclined to go for something like in the other suggestion I linked: an "enter your website/journal URL" field, which the system then queries to see if it's OpenID enabled. If it is, it treats the comment/commenter as an OpenID login attempt; if not, it defaults to the (not yet added, but On The List) pseudonymous comment option.
no subject
Generally speaking, though, we're ideologically against doing things that refer to one specific other service (such as, but not limited to, LJ) -- solutions should be generalizable for any external site as much as possible. One thing I've seen elsewhere on the OpenID-speaking internet that I really like as a solution is some sort of box/dropdown/display/etc that shows the icons and/or names of popular OpenID-enabled services, as a "enter your username for thus-and-such service here", and the system then constructs the OpenID URL for you behind the scenes.
The thing I'd be concerned about with your suggestion exactly as it's presented is that we already have people who expect to be able to log onto DW with their LJ username and password (and get very irate when they can't) -- it's a very common problem among LJ clonesites/DW-based code forks, and a major source of confusion and anger. As presented, I think your suggestion would increase that confusion instead of making it better, so I'd be more inclined to go for something like in the other suggestion I linked: an "enter your website/journal URL" field, which the system then queries to see if it's OpenID enabled. If it is, it treats the comment/commenter as an OpenID login attempt; if not, it defaults to the (not yet added, but On The List) pseudonymous comment option.