<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: OAuth spec and a shiny new OpenID.net</title>
	<atom:link href="http://blog.claimid.com/2007/10/oauth-spec-and-a-shiny-new-openidnet/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.claimid.com/2007/10/oauth-spec-and-a-shiny-new-openidnet/</link>
	<description>Manage your online identity.</description>
	<lastBuildDate>Wed, 22 Apr 2009 04:00:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Terrell Russell</title>
		<link>http://blog.claimid.com/2007/10/oauth-spec-and-a-shiny-new-openidnet/comment-page-1/#comment-49555</link>
		<dc:creator>Terrell Russell</dc:creator>
		<pubDate>Mon, 19 Nov 2007 14:46:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.claimid.com/2007/10/oauth-spec-and-a-shiny-new-openidnet/#comment-49555</guid>
		<description>Bob, thanks for the questions.

My first reaction is that it seems there&#039;s a potential privacy concern about pulling the username given a microid query... but it does seem that the point of publishing a microID would be to announce your ownership of a link...

I&#039;ll think on it some more - it would be useful to check microIDs found in the wild against a database of known items (and we&#039;re really the only one at this point in time).  Feel free to convince me/us.

As far as the http component is concerned - we&#039;re using the complete URL provided by the user for a particular link.  If they leave off a trailing slash, then it&#039;s calculated that way.  This sometimes leads to some confusion, but anything else would be arbitrary on our part and more confusing to debug if something unexpected is being seen down the line.

Thanks.</description>
		<content:encoded><![CDATA[<p>Bob, thanks for the questions.</p>
<p>My first reaction is that it seems there&#8217;s a potential privacy concern about pulling the username given a microid query&#8230; but it does seem that the point of publishing a microID would be to announce your ownership of a link&#8230;</p>
<p>I&#8217;ll think on it some more &#8211; it would be useful to check microIDs found in the wild against a database of known items (and we&#8217;re really the only one at this point in time).  Feel free to convince me/us.</p>
<p>As far as the http component is concerned &#8211; we&#8217;re using the complete URL provided by the user for a particular link.  If they leave off a trailing slash, then it&#8217;s calculated that way.  This sometimes leads to some confusion, but anything else would be arbitrary on our part and more confusing to debug if something unexpected is being seen down the line.</p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Aman</title>
		<link>http://blog.claimid.com/2007/10/oauth-spec-and-a-shiny-new-openidnet/comment-page-1/#comment-49553</link>
		<dc:creator>Bob Aman</dc:creator>
		<pubDate>Mon, 19 Nov 2007 04:17:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.claimid.com/2007/10/oauth-spec-and-a-shiny-new-openidnet/#comment-49553</guid>
		<description>Also, when claimID generates a microid, what is the value of the http url component being used?</description>
		<content:encoded><![CDATA[<p>Also, when claimID generates a microid, what is the value of the http url component being used?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Aman</title>
		<link>http://blog.claimid.com/2007/10/oauth-spec-and-a-shiny-new-openidnet/comment-page-1/#comment-49551</link>
		<dc:creator>Bob Aman</dc:creator>
		<pubDate>Mon, 19 Nov 2007 04:10:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.claimid.com/2007/10/oauth-spec-and-a-shiny-new-openidnet/#comment-49551</guid>
		<description>Bleh, that API call is wrong, should be:

GET http://claimid.com/api/get_username?microid=mailto+http:sha1:32b56025d21ba8c1c07ff6915b990bcddda5062f</description>
		<content:encoded><![CDATA[<p>Bleh, that API call is wrong, should be:</p>
<p>GET <a href="http://claimid.com/api/get_username?microid=mailto+http:sha1:32b56025d21ba8c1c07ff6915b990bcddda5062f" rel="nofollow">http://claimid.com/api/get_username?microid=mailto+http:sha1:32b56025d21ba8c1c07ff6915b990bcddda5062f</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Aman</title>
		<link>http://blog.claimid.com/2007/10/oauth-spec-and-a-shiny-new-openidnet/comment-page-1/#comment-49549</link>
		<dc:creator>Bob Aman</dc:creator>
		<pubDate>Mon, 19 Nov 2007 04:07:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.claimid.com/2007/10/oauth-spec-and-a-shiny-new-openidnet/#comment-49549</guid>
		<description>Speaking of specs and APIs, is there a particularly good reason why I can&#039;t:

GET http://http://claimid.com/api/get_username?microid=mailto+http:sha1:32b56025d21ba8c1c07ff6915b990bcddda5062f

That seemed to me like it&#039;d be an obvious thing to have around, but it&#039;s not there.  Actually, there&#039;s not much of an API at all. :-P</description>
		<content:encoded><![CDATA[<p>Speaking of specs and APIs, is there a particularly good reason why I can&#8217;t:</p>
<p>GET <a href="http://http://claimid.com/api/get_username?microid=mailto+http:sha1:32b56025d21ba8c1c07ff6915b990bcddda5062f" rel="nofollow">http://http://claimid.com/api/get_username?microid=mailto+http:sha1:32b56025d21ba8c1c07ff6915b990bcddda5062f</a></p>
<p>That seemed to me like it&#8217;d be an obvious thing to have around, but it&#8217;s not there.  Actually, there&#8217;s not much of an API at all. <img src='http://blog.claimid.com/wp-includes/images/smilies/icon_razz.gif' alt=':-P' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: People Over Process &#187; links for 2007-11-07</title>
		<link>http://blog.claimid.com/2007/10/oauth-spec-and-a-shiny-new-openidnet/comment-page-1/#comment-49397</link>
		<dc:creator>People Over Process &#187; links for 2007-11-07</dc:creator>
		<pubDate>Wed, 07 Nov 2007 07:23:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.claimid.com/2007/10/oauth-spec-and-a-shiny-new-openidnet/#comment-49397</guid>
		<description>[...] OAuth spec and a shiny new OpenID.net (tags: openauth openid identity identity2.0) [...]</description>
		<content:encoded><![CDATA[<p>[...] OAuth spec and a shiny new OpenID.net (tags: openauth openid identity identity2.0) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jclove</title>
		<link>http://blog.claimid.com/2007/10/oauth-spec-and-a-shiny-new-openidnet/comment-page-1/#comment-49045</link>
		<dc:creator>jclove</dc:creator>
		<pubDate>Sun, 14 Oct 2007 16:03:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.claimid.com/2007/10/oauth-spec-and-a-shiny-new-openidnet/#comment-49045</guid>
		<description>myID wasn&#039;t expecting anything like this. So imagine our suprise and pleasure when we found myID on the list at the openID website. It&#039;s great to know that we are in the same league  as neat providers like claimID and others.  Come see us and join the OpenID fun at our blog.</description>
		<content:encoded><![CDATA[<p>myID wasn&#8217;t expecting anything like this. So imagine our suprise and pleasure when we found myID on the list at the openID website. It&#8217;s great to know that we are in the same league  as neat providers like claimID and others.  Come see us and join the OpenID fun at our blog.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

