[OpenID] A selector for OpenID

[larry drebes]

Max,
The primary goal is to make is to improve the end-user experience for
OpenID.  There is a large user education problem that is throttling OpenID
growth.  We were also trying to make it simple for the RP, and neutral for
the OPs.

The javascript attaches to an existing OpenID login form.  In the (rare)
case the javascript could not load from the (high available) idselector
server, the form will continue to work, just with out a default value.

larry-

On Sat, Apr 19, 2008 at 7:29 AM, Max Metral <max at artsalliancelabs.com>
wrote:

> Yeah, I really agree with Peter here.  There is nothing inherent in the
> tool that requires an "app key" or any sort of locking into Janrain.  I
> don't begrudge them the attempt or desire to build a large "addressable"
> installed widget base, and in fact for most people it will be just fine.
> For me, I would only use it if I could have all the resources served
> locally, or at worst some img tag with a "delayed" javascript load.  So
> I think that basically puts the question to Brian and Janrain of "Was
> your primary goal to build widget installs or to help OpenId?  If the
> latter, would you just give out the code, perhaps with a branding and
> link requirement but w/o resource hosting?"
>
> I would be totally fine with "widget installs" and "no," but it'd
> probably make me wait for another implementation.
>
> --Max
>
> -----Original Message-----
> From: general-bounces at openid.net [mailto:general-bounces at openid.net] On
> Behalf Of Peter Watkins
> Sent: Saturday, April 19, 2008 7:45 AM
> To: Lachlan Hardy
> Cc: general at openid.net
> Subject: Re: [OpenID] A selector for OpenID
>
> On Sat, Apr 19, 2008 at 01:10:46PM +1000, Lachlan Hardy wrote:
> > 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).
>
> I've been thinking that something like this was needed, too, though I
> had not gotten as far as any coding. We're about to launch some login-
> required apps at work, and I like the idea of letting users reuse their
> existing accounts -- AOL and Yahoo! are probably quite prevalent (it's
> a shame there are no official Gmail and Passport/Hotmail OPs), but I
> don't expect users to understand OpenID URLs.
>
> I haven't looked at the guts, but I'd ask that this be designed &
> licensed to allow me to install the JS, images, etc. on my own server
> -- both to eliminate a point of failure and for privacy reasons. As a
> matter of security policy, I don't allow embedding any Javascript that
> I don't control on my login, logout, and other account management pages,
> and I try hard not to reference even images on other servers (privacy
> reasons).
>
> On a purely aesthetic point, I'd suggest adding another "Sign in" link
> in the provider pick list drop down for those providers that require
> a specific identity, e.g. add a Sign in link next to the screenname
> input when the user chooses AOL/AIM.
>
> And the Help link should display more help on the same page as the
> selector.
>
> But this is really quite nice!
>
> -Peter
>
> _______________________________________________
> general mailing list
> general at openid.net
> http://openid.net/mailman/listinfo/general
> _______________________________________________
> general mailing list
> general at openid.net
> http://openid.net/mailman/listinfo/general
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20080420/d8f4fa1b/attachment-0002.htm>