Actually, the better link is:<div><br></div><div><a href="http://www.abstractioneer.org/2009/04/personal-web-discovery.html">http://www.abstractioneer.org/2009/04/personal-web-discovery.html</a></div><div><br></div><div>and the linked posts in <a href="http://hueniverse.org">hueniverse.org</a><br>
<br><div class="gmail_quote">On Fri, Jul 10, 2009 at 11:20 AM, Breno de Medeiros <span dir="ltr"><<a href="mailto:breno@google.com">breno@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
There is already a proposal for this called webfinger:<div><br></div><div><a href="http://www.abstractioneer.org/" target="_blank">http://www.abstractioneer.org/</a></div><div><br></div><div>It leverages the LRDD proposal to provide a generic mechanism for email addresses, xmpp addresses, etc.<div>
<div></div><div class="h5"><br>
<br><div class="gmail_quote">On Fri, Jul 10, 2009 at 11:16 AM, Santosh Rajan <span dir="ltr"><<a href="mailto:santrajan@gmail.com" target="_blank">santrajan@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
It could be the gmail username, and google profile usernames they dont clash.<br>
Problem is only for Google employees who have <a href="http://google.com" target="_blank">google.com</a> email addresses. :)<br>
<div><div></div><div><br>
Eric Sachs wrote:<br>
><br>
> Only a subset of GoogleProfile users register a username, but yes, for<br>
> those<br>
> users that is the common request we get.<br>
><br>
> On Fri, Jul 10, 2009 at 10:46 AM, Santosh Rajan <<a href="mailto:santrajan@gmail.com" target="_blank">santrajan@gmail.com</a>><br>
> wrote:<br>
><br>
>><br>
>> Actually why dont you do discovery on<br>
>> <a href="http://google.com/username" target="_blank">http://google.com/username</a><br>
>> You can do that without clashing with your <a href="http://google.com" target="_blank">google.com</a> namespace by only<br>
>> responding to "Accept" header request with "application/XRD". That would<br>
>> really make a killer OpenID.<br>
>><br>
>><br>
>> Eric Sachs wrote:<br>
>> ><br>
>> > The feature in this area that we get more requests for is to support<br>
>> > OpenID<br>
>> > validation for the relatively new Google Profiles service, i.e.<br>
>> > <a href="http://profiles.google.com" target="_blank">profiles.google.com</a>, which is also a more memorable endpoint for users<br>
>> to<br>
>> > type :-). That support is not yet available, but its definitely on the<br>
>> > list.<br>
>> > On Fri, Jul 10, 2009 at 10:16 AM, Peter Williams<br>
>> > <<a href="mailto:pwilliams@rapattoni.com" target="_blank">pwilliams@rapattoni.com</a>>wrote:<br>
>> ><br>
>> >> Lets hope it prompts google to do much better: <a href="http://op" target="_blank">http://op</a>. <a href="http://google.com" target="_blank">google.com</a>:<br>
>> >> forming the eminently typable "<a href="http://op.google.com" target="_blank">op.google.com</a>".<br>
>> >><br>
>> >> They might even have that redirect to <a href="http://google.com/op" target="_blank">http://google.com/op</a> which they<br>
>> >> might make an xri mount point to the I-brokered authority that serves<br>
>> the<br>
>> >> op<br>
>> >> xrd/s. If their op is a real xri-labelled authority, a ref field in<br>
>> the<br>
>> >> sep<br>
>> >> can even properly provide for delgated authorization of xrd files by<br>
>> user<br>
>> >> authorities (which openid auth hacks up as openid delegation, when<br>
>> >> abusing<br>
>> >> the semantics of the op local id field per jonny bufu's recent<br>
>> message).<br>
>> >><br>
>> >> I dont think its hard to meet professional security engineering<br>
>> standards<br>
>> >> within openid: just be complete about xri semantics (even when using<br>
>> http<br>
>> >> identifiers). We dont need custom extensions for discovery,<br>
>> particularly<br>
>> >> if<br>
>> >> they project idp-centric vs user centric identity models.<br>
>> >><br>
>> >> But lets wait and see how they are signing the xrd files (the way the<br>
>> >> openxri server does it (per the standard), or "otherwise"). The<br>
>> validity<br>
>> >> logic for verifying that signature will tell us what class of trust<br>
>> >> semantics they are working towards: google as ttp for attribute<br>
>> sharing,<br>
>> >> or<br>
>> >> uci.<br>
>> >><br>
>> >> ________________________________<br>
>> >> From: Andrew Arnott <<a href="mailto:andrewarnott@gmail.com" target="_blank">andrewarnott@gmail.com</a>><br>
>> >> Sent: Thursday, July 09, 2009 8:30 PM<br>
>> >> To: Peter Williams <<a href="mailto:pwilliams@rapattoni.com" target="_blank">pwilliams@rapattoni.com</a>><br>
>> >> Cc: Eric Sachs <<a href="mailto:esachs@google.com" target="_blank">esachs@google.com</a>>; <a href="mailto:general@openid.net" target="_blank">general@openid.net</a><br>
>> >> <<a href="mailto:general@openid.net" target="_blank">general@openid.net</a>>;<br>
>> >> Paul Johnston <<a href="mailto:paj@pajhome.org.uk" target="_blank">paj@pajhome.org.uk</a>><br>
>> >> Subject: Re: [OpenID] What is my Google OpenID URL?<br>
>> >><br>
>> >> Wow. I'm going to have to use that tinyurl everywhere now. :-p<br>
>> >><br>
>> >> --<br>
>> >> Andrew Arnott<br>
>> >> "I [may] not agree with what you have to say, but I'll defend to the<br>
>> >> death<br>
>> >> your right to say it." - S. G. Tallentyre<br>
>> >><br>
>> >><br>
>> >> On Thu, Jul 9, 2009 at 8:24 PM, Peter Williams<br>
>> <<a href="mailto:pwilliams@rapattoni.com" target="_blank">pwilliams@rapattoni.com</a><br>
>> >> <mailto:<a href="mailto:pwilliams@rapattoni.com" target="_blank">pwilliams@rapattoni.com</a>>> wrote:<br>
>> >> come on google, it takes you 10s to have a redirector URL<br>
>> >> (<a href="http://op.google.com" target="_blank">op.google.com</a><<br>
>> >> <a href="http://op.google.com" target="_blank">http://op.google.com</a>>, perhaps?) redirect to the<br>
>> >> <a href="https://www.google.com/accounts/o8/id" target="_blank">https://www.google.com/accounts/o8/id</a>. Conforming RPs are require to<br>
>> >> follow the redirect, before detecting that the XRD at that address is<br>
>> an<br>
>> >> law#4-capable OP, vs a user.<br>
>> >><br>
>> >><br>
>> >> <a href="http://tinyurl.com/googop" target="_blank">http://tinyurl.com/googop</a> now produces<br>
>> >> <?xml version="1.0" encoding="UTF-8" ?><br>
>> >> -<file:///C:/Documents%20and%20Settings/peter/Desktop/id.xml#><br>
>> <xrds:XRDS<br>
>> >> xmlns:xrds="xri://$xrds" xmlns="xri://$xrd*($v*2.0)"><br>
>> >> -<file:///C:/Documents%20and%20Settings/peter/Desktop/id.xml#> <XRD><br>
>> >> -<file:///C:/Documents%20and%20Settings/peter/Desktop/id.xml#><br>
>> <Service<br>
>> >> priority="0"><br>
>> >> <Type><a href="http://specs.openid.net/auth/2.0/server" target="_blank">http://specs.openid.net/auth/2.0/server</a></Type><br>
>> >> <Type><a href="http://openid.net/srv/ax/1.0" target="_blank">http://openid.net/srv/ax/1.0</a></Type><br>
>> >> <Type><a href="http://specs.openid.net/extensions/ui/1.0/mode/popup" target="_blank">http://specs.openid.net/extensions/ui/1.0/mode/popup</a></Type><br>
>> >> <Type><a href="http://specs.openid.net/extensions/ui/1.0/icon" target="_blank">http://specs.openid.net/extensions/ui/1.0/icon</a></Type><br>
>> >> <Type><a href="http://specs.openid.net/extensions/pape/1.0" target="_blank">http://specs.openid.net/extensions/pape/1.0</a></Type><br>
>> >> <URI><a href="https://www.google.com/accounts/o8/ud" target="_blank">https://www.google.com/accounts/o8/ud</a></URI><br>
>> >> </Service><br>
>> >> </XRD><br>
>> >><br>
>> >> im sure google can do better than <a href="http://tinyurl.com" target="_blank">tinyurl.com</a><<a href="http://tinyurl.com" target="_blank">http://tinyurl.com</a>>!<br>
>> >><br>
>> >> How about <a href="http://op.google.com" target="_blank">op.google.com</a><<a href="http://op.google.com" target="_blank">http://op.google.com</a>>?!<br>
>> >><br>
>> >> ________________________________<br>
>> >> From: <a href="mailto:general-bounces@openid.net" target="_blank">general-bounces@openid.net</a><mailto:<a href="mailto:general-bounces@openid.net" target="_blank">general-bounces@openid.net</a>> [<br>
>> >> <a href="mailto:general-bounces@openid.net" target="_blank">general-bounces@openid.net</a><mailto:<a href="mailto:general-bounces@openid.net" target="_blank">general-bounces@openid.net</a>>] On<br>
>> Behalf<br>
>> >> Of Andrew Arnott [<a href="mailto:andrewarnott@gmail.com" target="_blank">andrewarnott@gmail.com</a><mailto:<a href="mailto:andrewarnott@gmail.com" target="_blank">andrewarnott@gmail.com</a><br>
>> >]<br>
>> >> Sent: Thursday, July 09, 2009 7:16 PM<br>
>> >> To: Eric Sachs<br>
>> >> Cc: <a href="mailto:general@openid.net" target="_blank">general@openid.net</a><mailto:<a href="mailto:general@openid.net" target="_blank">general@openid.net</a>>; Paul Johnston<br>
>> >> Subject: Re: [OpenID] What is my Google OpenID URL?<br>
>> >><br>
>> >> Note that using your Blogger blog URL is not equivalent to using<br>
>> >> <a href="https://www.google.com/accounts/o8/id" target="_blank">https://www.google.com/accounts/o8/id</a>. Besides the user interface of<br>
>> the<br>
>> >> login experience being completely different, Blogger's Provider is<br>
>> only<br>
>> >> an<br>
>> >> OpenID 1.1 provider, whereas Google's<br>
>> >> <a href="https://www.google.com/accounts/o8/id" target="_blank">https://www.google.com/accounts/o8/id</a> OpenID Provider is a more secure<br>
>> >> OpenID 2.0 provider.<br>
>> >><br>
>> >> --<br>
>> >> Andrew Arnott<br>
>> >> "I [may] not agree with what you have to say, but I'll defend to the<br>
>> >> death<br>
>> >> your right to say it." - S. G. Tallentyre<br>
>> >><br>
>> >><br>
>> >> On Thu, Jul 9, 2009 at 6:38 PM, Eric Sachs <<a href="mailto:esachs@google.com" target="_blank">esachs@google.com</a><mailto:<br>
>> >><br>
>> <a href="mailto:esachs@google.com" target="_blank">esachs@google.com</a>><mailto:<a href="mailto:esachs@google.com" target="_blank">esachs@google.com</a><mailto:<a href="mailto:esachs@google.com" target="_blank">esachs@google.com</a>>>><br>
>> >> wrote:<br>
>> >> If you create a blog on Google's blogger service, then you can type<br>
>> the<br>
>> >> name of that blog into OpenID login boxes.<br>
>> >><br>
>> >> If you are willing to be really geeky, type in<br>
>> >> <a href="https://www.google.com/accounts/o8/id" target="_blank">https://www.google.com/accounts/o8/id</a>. That points to the generic<br>
>> Google<br>
>> >> identity provider, and you will be redirected back with an opaque<br>
>> >> identifier. But we don't actually expect anyone to know to do that<br>
>> which<br>
>> >> is<br>
>> >> why a lot of OpenID relying parties are supporting other user<br>
>> interfaces<br>
>> >> with buttons for Google. For example, see<br>
>> >> <a href="http://uservoice.com/session/new" target="_blank">http://uservoice.com/session/new</a><br>
>> >><br>
>> >> Similarly a lot of blogs allow you to comment and identify you with an<br>
>> >> OpenID URL, and while you can try one of the tricks above, many of the<br>
>> >> blog<br>
>> >> commenting interfaces also include buttons (or the NASCAR style UI as<br>
>> the<br>
>> >> community likes to call it) to help users navigate their way through.<br>
>> >><br>
>> >> On Tue, Jul 7, 2009 at 11:34 PM, Paul Johnston<br>
>> >> <<a href="mailto:paj@pajhome.org.uk" target="_blank">paj@pajhome.org.uk</a><mailto:<br>
>> >><br>
>> <a href="mailto:paj@pajhome.org.uk" target="_blank">paj@pajhome.org.uk</a>><mailto:<a href="mailto:paj@pajhome.org.uk" target="_blank">paj@pajhome.org.uk</a><mailto:<a href="mailto:paj@pajhome.org.uk" target="_blank">paj@pajhome.org.uk</a><br>
>> >>><br>
>> >> wrote:<br>
>> >> Hi,<br>
>> >><br>
>> >> I'm sorry for asking such an obvious question, but after considerable<br>
>> >> time spent searching for this I am unable to figure this out.<br>
>> >><br>
>> >> My google account name is paul.paj. I would like to login to<br>
>> >> <a href="http://bitbucket.org" target="_blank">bitbucket.org</a><<a href="http://bitbucket.org" target="_blank">http://bitbucket.org</a>><<a href="http://bitbucket.org" target="_blank">http://bitbucket.org</a>> using<br>
>> OpenID.<br>
>> >> How do I do it?<br>
>> >><br>
>> >> Paul<br>
>> >> _______________________________________________<br>
>> >> general mailing list<br>
>> >><br>
>> <a href="mailto:general@openid.net" target="_blank">general@openid.net</a><mailto:<a href="mailto:general@openid.net" target="_blank">general@openid.net</a>><mailto:<a href="mailto:general@openid.net" target="_blank">general@openid.net</a><br>
>> >> <mailto:<a href="mailto:general@openid.net" target="_blank">general@openid.net</a>>><br>
>> >> <a href="http://openid.net/mailman/listinfo/general" target="_blank">http://openid.net/mailman/listinfo/general</a><br>
>> >><br>
>> >><br>
>> >> _______________________________________________<br>
>> >> general mailing list<br>
>> >><br>
>> <a href="mailto:general@openid.net" target="_blank">general@openid.net</a><mailto:<a href="mailto:general@openid.net" target="_blank">general@openid.net</a>><mailto:<a href="mailto:general@openid.net" target="_blank">general@openid.net</a><br>
>> >> <mailto:<a href="mailto:general@openid.net" target="_blank">general@openid.net</a>>><br>
>> >> <a href="http://openid.net/mailman/listinfo/general" target="_blank">http://openid.net/mailman/listinfo/general</a><br>
>> >><br>
>> >><br>
>> >><br>
>> >> _______________________________________________<br>
>> >> general mailing list<br>
>> >> <a href="mailto:general@openid.net" target="_blank">general@openid.net</a><br>
>> >> <a href="http://openid.net/mailman/listinfo/general" target="_blank">http://openid.net/mailman/listinfo/general</a><br>
>> >><br>
>> ><br>
>> > _______________________________________________<br>
>> > general mailing list<br>
>> > <a href="mailto:general@openid.net" target="_blank">general@openid.net</a><br>
>> > <a href="http://openid.net/mailman/listinfo/general" target="_blank">http://openid.net/mailman/listinfo/general</a><br>
>> ><br>
>> ><br>
>><br>
>><br>
>> -----<br>
>><br>
>> Santosh Rajan<br>
>> <a href="http://santrajan.blogspot.com" target="_blank">http://santrajan.blogspot.com</a> <a href="http://santrajan.blogspot.com" target="_blank">http://santrajan.blogspot.com</a><br>
>> --<br>
>> View this message in context:<br>
>> <a href="http://www.nabble.com/Google-custom-discovery-tp24431509p24431923.html" target="_blank">http://www.nabble.com/Google-custom-discovery-tp24431509p24431923.html</a><br>
>> Sent from the OpenID - General mailing list archive at Nabble.com.<br>
>><br>
>> _______________________________________________<br>
>> general mailing list<br>
>> <a href="mailto:general@openid.net" target="_blank">general@openid.net</a><br>
>> <a href="http://openid.net/mailman/listinfo/general" target="_blank">http://openid.net/mailman/listinfo/general</a><br>
>><br>
><br>
> _______________________________________________<br>
> general mailing list<br>
> <a href="mailto:general@openid.net" target="_blank">general@openid.net</a><br>
> <a href="http://openid.net/mailman/listinfo/general" target="_blank">http://openid.net/mailman/listinfo/general</a><br>
><br>
><br>
<br>
<br>
-----<br>
<br>
Santosh Rajan<br>
<a href="http://santrajan.blogspot.com" target="_blank">http://santrajan.blogspot.com</a> <a href="http://santrajan.blogspot.com" target="_blank">http://santrajan.blogspot.com</a><br>
--<br>
</div></div>View this message in context: <a href="http://www.nabble.com/Google-custom-discovery-tp24431509p24432348.html" target="_blank">http://www.nabble.com/Google-custom-discovery-tp24431509p24432348.html</a><br>
<div><div></div><div>Sent from the OpenID - General mailing list archive at Nabble.com.<br>
<br>
_______________________________________________<br>
general mailing list<br>
<a href="mailto:general@openid.net" target="_blank">general@openid.net</a><br>
<a href="http://openid.net/mailman/listinfo/general" target="_blank">http://openid.net/mailman/listinfo/general</a><br>
</div></div></blockquote></div><br><br clear="all"><br></div></div>-- <br>--Breno<br><br>+1 (650) 214-1007 desk<br>+1 (408) 212-0135 (Grand Central)<br>MTV-41-3 : 383-A <br>PST (GMT-8) / PDT(GMT-7)<br>
</div>
</blockquote></div><br><br clear="all"><br>-- <br>--Breno<br><br>+1 (650) 214-1007 desk<br>+1 (408) 212-0135 (Grand Central)<br>MTV-41-3 : 383-A <br>PST (GMT-8) / PDT(GMT-7)<br>
</div>