<HTML dir=ltr><HEAD></HEAD>
<BODY>
<DIV id=idOWAReplyText56685 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Fascinating! Not the widget itself, but the economics of the strategy of dis-intermediating the IDPs. If it takes off, you can see the model as one of: rewarding IDP adoption and delivery of related service by increasing brand logo presence This will do wonders for JanRain's valuation in the eyes of the dominant OPs/IDPs.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>This is exactly the dynamics that intelligent directory-based infrastructure needs to take off, rather than be a stuffy telco-white pages implementation, a layer 7 service resolver, or layer 3 net address resolver. Outsourcing id is one model, but its not half as explosive a curve as certs were, as openid will be (certs financed two new billionares, and one trip to the space station by a tourist: openid CAN do better!) Lets recall the old war horse story: pure directories (and files like FOAF) tend to always get stuck at the fact that business are dis-incentivised from every publicising their people power; this they dont, even if you (finally) add the security model. Here we have directories moderating a brand market, which is excellent.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Now, we need 10 of these (sounds like we have 2 already) : and a slew of economic/revenue models in which brands can also use indirect $$ or indirect payback or to bias the dis-intermediator to alter the display. Then we need consume rejection, and all the usual arguments that will make the marketing space vibrant -- and (nicely) political. The factors that come into play will be nefarious, just like all the places re-factoring impacts service economies.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV></DIV>
<DIV id=idSignature77949>
<DIV><FONT face=Arial color=#000000 size=2><SPAN style="FONT-SIZE: 7.5pt">_________________________<BR></SPAN><B>Peter Williams<BR></B></FONT><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Lachlan Hardy<BR><B>Sent:</B> Fri 4/18/2008 8:10 PM<BR><B>To:</B> Brian Ellin<BR><B>Cc:</B> general@openid.net<BR><B>Subject:</B> Re: [OpenID] A selector for OpenID<BR></FONT><BR></DIV></DIV>
<DIV><BR>
<DIV class=gmail_quote>
<BLOCKQUOTE class=gmail_quote style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">It's a widget (<A href="https://www.openidselector.com/" target=_blank>https://www.openidselector.com/</A>) that you add to the<BR>existing OpenID login form on your relying party website. It's all<BR>about getting users signed into your website as quickly and<BR>efficiently as possible, and achieves this by providing a simple,<BR>consistent, provider neutral interface, all while educating the user<BR>about OpenID during the process. It hooks into your already<BR>functional OpenID login form, and enhances it with a little bit of<BR>javascript.</BLOCKQUOTE>
<DIV><BR>Very cool, Brian! As I've just spent a week working on a very similar interface for one specific project, I'm very impressed that you've brought out a generic version. (of course, I wish I'd seen this a week ago, but that's my problem). <BR><BR>I'll definitely be looking at implementing it on place of what we built. Thanks!<BR><BR>Lachlan Hardy<BR></DIV></DIV><BR><BR></DIV></BODY></HTML>