Skip to main content

Netscape.com += OpenID; more...

Note: The folks over at Netscape are doing this on their own and I haveno inside information whatsoever.  So I can blog freely.

It's great to see Netscapestart accepting OpenIDs.  It's good to see the user experienceissues being worked out -- the best methods will win out over time.  Dmitry Shechtman calls for theelimination of registration, though what he actually says is a bitstronger:
The usefulness of OpenID is void if yourservice requires all users to sign upregardless of whether they have an OpenID. This doesn’t mean that youshouldn’t ask them to provide additional details, such as an activee-mail address (although OpenID Simple Registration usually handlesthat for you). You can do it after the user signs in for thefirst time. Just don’t ask her to sign up.
I understand this point of view, but disagree:
  • Users expect to find "sign up" or "register" links when going toa new site; not providing them breaks their expectations and that's bad.
  • If a user doesn't have an OpenID already, they do need toregister with your site.  You have to make this just as easy as beforeyou added OpenID to your UI.
  • Sometimes you really do need to gather an e-mail address, agreeto Terms of Service legalese, etc. before using a site.
Whether you call this "providing additional details" or "registration"the flow is much the same.  I do agree that in the long run itwould be better if you could simply let OpenID-enabled people sign in,collect whatever registration info you can automatically, and thendecide if and when to bother them with registration administrivia atthat point or when you actually need it.  In the short run, it's simplynot feasible to optimize for OpenID experience at the expense of yourother users.

Unfortunately, you don't currently know who has an OpenID and whodoesn't.  Maybe there's room here for a service: gotopenid.org.  Yousign in there once with your OpenID, and it cookies you as someone whowants to use OpenID wherever possible.  Sites that want to offer anOpenID-streamlined experience could make a JSON call tohttp://gotopenid.org/check.js.  This would tell the site that the userknows what OpenID is and prefers to use it for signing in.

On a side note, it looks to me by the screen shots that the AOL/AIMscreen name integration is simply using the AOL OpenID identityservice.  We'll see on Monday;  certainly that's the easy way to do it-- a convenience wrapper around an OpenID sign in.

Tags: , , ,

Popular posts from this blog

Personal Web Discovery (aka Webfinger)

There's a particular discovery problem for open and distributed protocols such as OpenID, OAuth, Portable Contacts, Activity Streams, and OpenSocial.  It seems like a trivial problem, but it's one of the stumbling blocks that slows mass adoption.  We need to fix it.  So first, I'm going to name it:

The Personal Web Discovery Problem:  Given a person, how do I find out what services that person uses?
This does sound trivial, doesn't it?  And it is easy as long as you're service-centric; if you're building on top of social network X, there is no discovery problem, or at least only a trivial one that can be solved with proprietary APIs.  But what if you want to build on top of X,Y, and Z?  Well, you write code to make the user log in to each one so you can call those proprietary APIs... which means the user has to tell you their identity (and probably password) on each one... and the user has already clicked the Back button because this is complicated and annoying.

XAuth is a Lot Like Democracy

XAuth is a lot like democracy:  The worst form of user identity prefs, except for all those others that have been tried (apologies to Churchill).  I've just read Eran's rather overblown "XAuth - a Terrible, Horrible, No Good, Very Bad Idea", and I see that the same objections are being tossed around; I'm going to rebut them here to save time in the future.

Let's take this from the top.  XAuth is a proposal to let browsers remember that sites have registered themselves as a user's identity provider and let other sites know if the user has a session at that site.  In other words, it has the same information as proprietary solutions that already exist, except that it works across multiple identity providers.  It means that when you go to a new website, it doesn't have to ask you what your preferred services are, it can just look them up.  Note that this only tells the site that you have an account with Google or Yahoo or Facebook or Twitter, not what the…
Twister is interesting.  It's a decentralized "microblogging" system based on putting together existing protocols:  Bitcoin, distributed hash tables, and Bittorrent.  The most interesting part for me is using Bitcoin for user registration and spam control.  Federated systems handle this with federated trust, which is at least conceptually simple.  The Twister/Bitcoin mechanism looks intriguing though I don't know enough about Bitcoin to really comment.  Need to read further.