Decius wrote:

It occurs to me that this could actually be strapped onto the side of the existing openID system...

Certainly.

The OpenID spec says:

It's also recommend that the form field be named openid_url so browsers auto-complete user's URLs between different sites, in the same way the ecommerce world tends to use conventions like "address1" and "address2".

Which I lump into a similar class of hack. I guess I don't understand the multiple icons thing. One could set up an OpenID transaction service: developers target authenticating with the transaction service, and the service handles all of the cross-authentication services. But I am not necessarily sure why one would write or run that service for the public good. It would be like tinyURL or weblogs.com but less visible. And dealing with authentication issues makes it more sensitive -- not because the service would see the users' login information, but it could false authenticate users selectively.

Why multiple icons?

RE: news: OpenID support