Skip to main content += 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:  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 to  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

The problem with creation date metadata in PDF documents

Last night Rachel Maddow talked about an apparently fake NSA document "leaked" to her organization.  There's a lot of info there, I suggest you listen to the whole thing:

There's a lot to unpack there but it looks like somebody tried to fool MSNBC into running with a fake accusation based on faked NSA documents, apparently based on cloning the document the Intercept published back on 6/5/2017, which to all appearances was itself a real NSA document in PDF form.

I think the main thrust of this story is chilling and really important to get straight -- some person or persons unknown is sending forged PDFs to news organization(s), apparently trying to get them to run stories based on forged documents.  And I completely agree with Maddow that she was right to send up a "signal flare" to all the news organizations to look out for forgeries.  Really, really, really import…

Why I'm No Longer On The Facebook

I've had a Facebook account for a few years, largely because other people were on it and were organizing useful communities there.  I stuck with it (not using it for private information) even while I grew increasingly concerned about Facebook's inability to be trustworthy guardians of private information.  The recent slap on the wrist from the FTC for Facebook violating the terms of its prior consent agreement made it clear that there wasn't going to be any penalty for Facebook for continuing to violate court orders.
Mark Zuckerberg claimed he had made a mistake in 2016 by ridiculing the idea of election interference on his platform, apologized, and claimed he was turning over a new leaf:
“After the election, I made a comment that I thought the idea misinformation on Facebook changed the outcome of the election was a crazy idea. Calling that crazy was dismissive and I regret it.  This is too important an issue to be dismissive.” It turns out, though, that was just Zuck ly…

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.