<?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: The OpenID Dillemma</title>
	<atom:link href="http://pthree.org/2008/02/20/the-openid-dillemma/feed/" rel="self" type="application/rss+xml" />
	<link>http://pthree.org/2008/02/20/the-openid-dillemma/</link>
	<description>Linux.  GNU.  Freedom.</description>
	<lastBuildDate>Fri, 17 May 2013 20:46:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.6-beta2-24176</generator>
	<item>
		<title>By: Frederique</title>
		<link>http://pthree.org/2008/02/20/the-openid-dillemma/#comment-109935</link>
		<dc:creator>Frederique</dc:creator>
		<pubDate>Tue, 21 Apr 2009 09:21:02 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=552#comment-109935</guid>
		<description><![CDATA[I really do think that OpenID is the future. The previous months a lot of big player finnaly supported OpenID loggin. But I agree it&#039;s still a bit of a way to go...]]></description>
		<content:encoded><![CDATA[<p>I really do think that OpenID is the future. The previous months a lot of big player finnaly supported OpenID loggin. But I agree it&#8217;s still a bit of a way to go&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anthony Picciano</title>
		<link>http://pthree.org/2008/02/20/the-openid-dillemma/#comment-109381</link>
		<dc:creator>Anthony Picciano</dc:creator>
		<pubDate>Thu, 15 Jan 2009 19:25:52 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=552#comment-109381</guid>
		<description><![CDATA[The dilemma is that OpenID is based on trust. You cannot force a provider to trust any OpenID -- there&#039;s no trust there.

I agree that in its present condition OpenID is broken and almost useless.]]></description>
		<content:encoded><![CDATA[<p>The dilemma is that OpenID is based on trust. You cannot force a provider to trust any OpenID &#8212; there&#8217;s no trust there.</p>
<p>I agree that in its present condition OpenID is broken and almost useless.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: paul</title>
		<link>http://pthree.org/2008/02/20/the-openid-dillemma/#comment-106275</link>
		<dc:creator>paul</dc:creator>
		<pubDate>Sat, 09 Aug 2008 17:14:55 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=552#comment-106275</guid>
		<description><![CDATA[Stop crying and read up on the trust model of OpenID (or better: the lack thereof). Why on earth should the website you&#039;re trying to login trust some random OpenID provider?]]></description>
		<content:encoded><![CDATA[<p>Stop crying and read up on the trust model of OpenID (or better: the lack thereof). Why on earth should the website you&#8217;re trying to login trust some random OpenID provider?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ori Avtalion</title>
		<link>http://pthree.org/2008/02/20/the-openid-dillemma/#comment-92273</link>
		<dc:creator>Ori Avtalion</dc:creator>
		<pubDate>Sat, 23 Feb 2008 11:23:46 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=552#comment-92273</guid>
		<description><![CDATA[Hmm.. Wasn&#039;t there an OpenID login on this site? :)

I apologize in advance for this horribly long comment.

The reason why so many websites are becoming providers is because it&#039;s relatively easy:
Just hook the authentication server into your already-existing cross-site login system, and add a meta tag at the top of the user&#039;s personal page.

(&quot;Cross-site login system&quot; may not be the correct term, but I&#039;m referring to the service that TypeKey, Yahoo, Google, MS Passport etc. offer which allows you to integrate their authentication mechanisms on your personal website&#039;s login page -- basically the proprietary alternative for OpenID)

Becoming a Consumer is much harder. You have to create new tables in the database that link OpenID accounts to your exiting user accounts, and figure out how ito integrate it with your existing interface which would allow the common non-techy user to discover/ignore OpenID if he/she pleases to.

In the recent OpenID DevCamp, an effort was started to provide recommended methods of interface integration, with the help of UI experts. (I may not have all the details straight, but it&#039;s one of the goals).
Once this is done, I expect big-time consumers to appear in a slightly faster rate.

Until that happens, almost any web-user will have at least one OpenID account through a popular website which is a Good Thing. Consumers will be able to implement &quot;smart&quot; login forms with &quot;login with &quot; fields instead of &quot;login with OpenID&quot;.

Then the only problem would be to teach the users that they were really using OpenID ;)]]></description>
		<content:encoded><![CDATA[<p>Hmm.. Wasn&#8217;t there an OpenID login on this site? <img src='http://pthree.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>I apologize in advance for this horribly long comment.</p>
<p>The reason why so many websites are becoming providers is because it&#8217;s relatively easy:<br />
Just hook the authentication server into your already-existing cross-site login system, and add a meta tag at the top of the user&#8217;s personal page.</p>
<p>(&#8220;Cross-site login system&#8221; may not be the correct term, but I&#8217;m referring to the service that TypeKey, Yahoo, Google, MS Passport etc. offer which allows you to integrate their authentication mechanisms on your personal website&#8217;s login page &#8212; basically the proprietary alternative for OpenID)</p>
<p>Becoming a Consumer is much harder. You have to create new tables in the database that link OpenID accounts to your exiting user accounts, and figure out how ito integrate it with your existing interface which would allow the common non-techy user to discover/ignore OpenID if he/she pleases to.</p>
<p>In the recent OpenID DevCamp, an effort was started to provide recommended methods of interface integration, with the help of UI experts. (I may not have all the details straight, but it&#8217;s one of the goals).<br />
Once this is done, I expect big-time consumers to appear in a slightly faster rate.</p>
<p>Until that happens, almost any web-user will have at least one OpenID account through a popular website which is a Good Thing. Consumers will be able to implement &#8220;smart&#8221; login forms with &#8220;login with &#8221; fields instead of &#8220;login with OpenID&#8221;.</p>
<p>Then the only problem would be to teach the users that they were really using OpenID <img src='http://pthree.org/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary W. Longsine</title>
		<link>http://pthree.org/2008/02/20/the-openid-dillemma/#comment-92221</link>
		<dc:creator>Gary W. Longsine</dc:creator>
		<pubDate>Thu, 21 Feb 2008 17:03:23 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=552#comment-92221</guid>
		<description><![CDATA[The Djinni is probably out of the bottle now, but this seems like a problem that might have been addressable with the proper type of license from the outset.  It could have been specified that use of the &quot;OpenID&quot; name requires acceptance of OpenID credentials from elsewhere, for example.  As with so many problems like this, how to put the Djinni back in the bottle isn&#039;t immediately apparent. 

/gary]]></description>
		<content:encoded><![CDATA[<p>The Djinni is probably out of the bottle now, but this seems like a problem that might have been addressable with the proper type of license from the outset.  It could have been specified that use of the &#8220;OpenID&#8221; name requires acceptance of OpenID credentials from elsewhere, for example.  As with so many problems like this, how to put the Djinni back in the bottle isn&#8217;t immediately apparent. </p>
<p>/gary</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://pthree.org/2008/02/20/the-openid-dillemma/#comment-92216</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Thu, 21 Feb 2008 12:51:36 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=552#comment-92216</guid>
		<description><![CDATA[I second this. There need to be more OpenID consumer enabled sites.
I often find myself skipping registration on a site, which does not support OpenID yet.

A directory of OpenID enabled sites is available at https://www.myopenid.com/directory]]></description>
		<content:encoded><![CDATA[<p>I second this. There need to be more OpenID consumer enabled sites.<br />
I often find myself skipping registration on a site, which does not support OpenID yet.</p>
<p>A directory of OpenID enabled sites is available at <a href="https://www.myopenid.com/directory" rel="nofollow">https://www.myopenid.com/directory</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Louise</title>
		<link>http://pthree.org/2008/02/20/the-openid-dillemma/#comment-92209</link>
		<dc:creator>Louise</dc:creator>
		<pubDate>Thu, 21 Feb 2008 11:47:30 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=552#comment-92209</guid>
		<description><![CDATA[OpenID is a great idea. Can’t wait to see it accepted by everyone. In the meantime, while waiting for wider acceptance, password managers are a great alternative. So basically you store all non-OpenID logins in one place. 
Something to consider while waiting for OpenID to go global!

I work at PassPack, an online password manager. You may want to have a look:

http://passpack.com/info/home/

Louise]]></description>
		<content:encoded><![CDATA[<p>OpenID is a great idea. Can’t wait to see it accepted by everyone. In the meantime, while waiting for wider acceptance, password managers are a great alternative. So basically you store all non-OpenID logins in one place.<br />
Something to consider while waiting for OpenID to go global!</p>
<p>I work at PassPack, an online password manager. You may want to have a look:</p>
<p><a href="http://passpack.com/info/home/" rel="nofollow">http://passpack.com/info/home/</a></p>
<p>Louise</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dmitri</title>
		<link>http://pthree.org/2008/02/20/the-openid-dillemma/#comment-92203</link>
		<dc:creator>Dmitri</dc:creator>
		<pubDate>Thu, 21 Feb 2008 05:50:24 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=552#comment-92203</guid>
		<description><![CDATA[I think you have a typo: &quot;large companies to become OpenID providers, but now allow logging into their service with your OpenID account&quot;, you probably mean &quot;not allow&quot; rather then &quot;now&quot;.

I totally agree with your article tho, it&#039;s stupid to provide IDs but not accept them for creating accounts.]]></description>
		<content:encoded><![CDATA[<p>I think you have a typo: &#8220;large companies to become OpenID providers, but now allow logging into their service with your OpenID account&#8221;, you probably mean &#8220;not allow&#8221; rather then &#8220;now&#8221;.</p>
<p>I totally agree with your article tho, it&#8217;s stupid to provide IDs but not accept them for creating accounts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://pthree.org/2008/02/20/the-openid-dillemma/#comment-92188</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Wed, 20 Feb 2008 23:04:45 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=552#comment-92188</guid>
		<description><![CDATA[@Dax Kelson-  Partial YUP.  I can only use my OpenID URL to comment, not to create a LiveJournal or Blogger account, or use an existing OpenID to authenticate for logging into those accounts.  As far as I&#039;m concerned, it&#039;s not good enough.  Leaving comments on peoples blogs with your OpenID is different than logging into that account with OpenID.]]></description>
		<content:encoded><![CDATA[<p>@Dax Kelson-  Partial YUP.  I can only use my OpenID URL to comment, not to create a LiveJournal or Blogger account, or use an existing OpenID to authenticate for logging into those accounts.  As far as I&#8217;m concerned, it&#8217;s not good enough.  Leaving comments on peoples blogs with your OpenID is different than logging into that account with OpenID.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dax Kelson</title>
		<link>http://pthree.org/2008/02/20/the-openid-dillemma/#comment-92187</link>
		<dc:creator>Dax Kelson</dc:creator>
		<pubDate>Wed, 20 Feb 2008 23:02:19 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=552#comment-92187</guid>
		<description><![CDATA[&quot;What about LiveJournal? Wordpress? Yahoo!? Blogger? etc. NOPE.&quot;

Sorry. Two of your 4 &quot;NOPE&quot; examples are actually &quot;YUP&quot;. LiveJournal and Blogger let you leave comments with OpenID authentication.]]></description>
		<content:encoded><![CDATA[<p>&#8220;What about LiveJournal? WordPress? Yahoo!? Blogger? etc. NOPE.&#8221;</p>
<p>Sorry. Two of your 4 &#8220;NOPE&#8221; examples are actually &#8220;YUP&#8221;. LiveJournal and Blogger let you leave comments with OpenID authentication.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Artūras B.</title>
		<link>http://pthree.org/2008/02/20/the-openid-dillemma/#comment-92184</link>
		<dc:creator>Artūras B.</dc:creator>
		<pubDate>Wed, 20 Feb 2008 20:13:45 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=552#comment-92184</guid>
		<description><![CDATA[My two cents to this discussion:
I think big companies just found a good (open and free) solution that siutes their SSO needs - for the whole portfolio of their services. And this is pitty...
I think that the OpenID license should include some additional terms for public OpenID providers - they must not only provide OpenIDs but also accept external ones for logins. That would mean full (consumer plus provider) OpenID support for public OpenID services.]]></description>
		<content:encoded><![CDATA[<p>My two cents to this discussion:<br />
I think big companies just found a good (open and free) solution that siutes their SSO needs &#8211; for the whole portfolio of their services. And this is pitty&#8230;<br />
I think that the OpenID license should include some additional terms for public OpenID providers &#8211; they must not only provide OpenIDs but also accept external ones for logins. That would mean full (consumer plus provider) OpenID support for public OpenID services.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Hasler</title>
		<link>http://pthree.org/2008/02/20/the-openid-dillemma/#comment-92180</link>
		<dc:creator>Sam Hasler</dc:creator>
		<pubDate>Wed, 20 Feb 2008 19:24:17 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=552#comment-92180</guid>
		<description><![CDATA[Who cares about the big players, it&#039;s the long tail of consumer sites where OpenID will be really useful.

I&#039;ve got accounts for most the bigger sites anyway and since I use them frequently it&#039;s not a burden to remember my username/password for them. It&#039;s the long tail of little sites that lots of people may check out but can&#039;t be bothered to create an account for, or forget their login details when the revisit   two months since they last used it that will get the most benefit from consuming OpenIDs.]]></description>
		<content:encoded><![CDATA[<p>Who cares about the big players, it&#8217;s the long tail of consumer sites where OpenID will be really useful.</p>
<p>I&#8217;ve got accounts for most the bigger sites anyway and since I use them frequently it&#8217;s not a burden to remember my username/password for them. It&#8217;s the long tail of little sites that lots of people may check out but can&#8217;t be bothered to create an account for, or forget their login details when the revisit   two months since they last used it that will get the most benefit from consuming OpenIDs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dread Knight</title>
		<link>http://pthree.org/2008/02/20/the-openid-dillemma/#comment-92179</link>
		<dc:creator>Dread Knight</dc:creator>
		<pubDate>Wed, 20 Feb 2008 19:18:42 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=552#comment-92179</guid>
		<description><![CDATA[Anyway, i am sure google will do lots of good with gmail. I bet my money on google.]]></description>
		<content:encoded><![CDATA[<p>Anyway, i am sure google will do lots of good with gmail. I bet my money on google.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dread Knight</title>
		<link>http://pthree.org/2008/02/20/the-openid-dillemma/#comment-92178</link>
		<dc:creator>Dread Knight</dc:creator>
		<pubDate>Wed, 20 Feb 2008 19:17:42 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=552#comment-92178</guid>
		<description><![CDATA[//Large greedy companies are free to su** on my big co**.

I noticed this myself these days. OpenID went straight to the dump yard for me, too bad since it was a good concept.]]></description>
		<content:encoded><![CDATA[<p>//Large greedy companies are free to su** on my big co**.</p>
<p>I noticed this myself these days. OpenID went straight to the dump yard for me, too bad since it was a good concept.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wolfger</title>
		<link>http://pthree.org/2008/02/20/the-openid-dillemma/#comment-92174</link>
		<dc:creator>Wolfger</dc:creator>
		<pubDate>Wed, 20 Feb 2008 17:53:40 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=552#comment-92174</guid>
		<description><![CDATA[I have two LJ accounts. One I created a long time ago, and one for my Wordpress OpenID. So yes, LJ supports OpenID. I simply haven&#039;t tried the others.]]></description>
		<content:encoded><![CDATA[<p>I have two LJ accounts. One I created a long time ago, and one for my WordPress OpenID. So yes, LJ supports OpenID. I simply haven&#8217;t tried the others.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
