<?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: Sites with bad OpenID support</title>
	<atom:link href="http://joped.com/2008/12/sites-with-bad-openid-support/feed/" rel="self" type="application/rss+xml" />
	<link>http://joped.com/2008/12/sites-with-bad-openid-support/</link>
	<description>Grumpy geek from Jersey living in San Francisco</description>
	<lastBuildDate>Thu, 20 Oct 2011 18:00:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: ProfessorTom</title>
		<link>http://joped.com/2008/12/sites-with-bad-openid-support/comment-page-1/#comment-16320</link>
		<dc:creator>ProfessorTom</dc:creator>
		<pubDate>Tue, 15 Feb 2011 02:49:58 +0000</pubDate>
		<guid isPermaLink="false">http://joped.com/?p=47#comment-16320</guid>
		<description>I want to use Live Journal as my OpenID provider, but Google can&#039;t seem to talk nicely with LJ. Annoying. As. Hell.

In recent days, I&#039;ve come to view Twitter as my &lt;a href=&quot;http://www.codinghorror.com/blog/2010/11/your-internet-drivers-license.html&quot; rel=&quot;nofollow&quot;&gt;internet driver&#039;s license&lt;/a&gt;, but not enough sites allow me to identify via Twitter. Maddening.</description>
		<content:encoded><![CDATA[<p>I want to use Live Journal as my OpenID provider, but Google can&#8217;t seem to talk nicely with LJ. Annoying. As. Hell.</p>
<p>In recent days, I&#8217;ve come to view Twitter as my <a href="http://www.codinghorror.com/blog/2010/11/your-internet-drivers-license.html" rel="nofollow">internet driver&#8217;s license</a>, but not enough sites allow me to identify via Twitter. Maddening.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Messina</title>
		<link>http://joped.com/2008/12/sites-with-bad-openid-support/comment-page-1/#comment-933</link>
		<dc:creator>Chris Messina</dc:creator>
		<pubDate>Mon, 29 Dec 2008 20:47:09 +0000</pubDate>
		<guid isPermaLink="false">http://joped.com/?p=47#comment-933</guid>
		<description>I call this flow the &quot;double taxation of OpenID&quot;. I think that we need to develop a better and more uniform way of passing data from OPs to RPs, in a similar fashion to Facebook Connect. And only if that fails, then the secondary profile form should be shown -- even though that&#039;s a major hurdle that turns off a lot of folks.

In the Yahoo OpenID research that was done, any additional sign up process will cause people to bolt, so it&#039;s actually bad for business on the one hand. On the other, site operators want to collect as much information about people as possible, so there&#039;s a balance to be struck. 

This is clearly an emerging area, but the tension that you describe gets at the heart of one of the core challenges we must address with OpenID usability.</description>
		<content:encoded><![CDATA[<p>I call this flow the &#8220;double taxation of OpenID&#8221;. I think that we need to develop a better and more uniform way of passing data from OPs to RPs, in a similar fashion to Facebook Connect. And only if that fails, then the secondary profile form should be shown &#8212; even though that&#8217;s a major hurdle that turns off a lot of folks.</p>
<p>In the Yahoo OpenID research that was done, any additional sign up process will cause people to bolt, so it&#8217;s actually bad for business on the one hand. On the other, site operators want to collect as much information about people as possible, so there&#8217;s a balance to be struck. </p>
<p>This is clearly an emerging area, but the tension that you describe gets at the heart of one of the core challenges we must address with OpenID usability.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joped</title>
		<link>http://joped.com/2008/12/sites-with-bad-openid-support/comment-page-1/#comment-931</link>
		<dc:creator>Joped</dc:creator>
		<pubDate>Sun, 28 Dec 2008 05:15:22 +0000</pubDate>
		<guid isPermaLink="false">http://joped.com/?p=47#comment-931</guid>
		<description>Ya, Sourceforge is one of the major offenders of this.  I contacted them a ways back about this and they made some silly suggestions that this requirement was due to how they handle SSH keys for SVN access.</description>
		<content:encoded><![CDATA[<p>Ya, Sourceforge is one of the major offenders of this.  I contacted them a ways back about this and they made some silly suggestions that this requirement was due to how they handle SSH keys for SVN access.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://joped.com/2008/12/sites-with-bad-openid-support/comment-page-1/#comment-930</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Sun, 28 Dec 2008 03:32:55 +0000</pubDate>
		<guid isPermaLink="false">http://joped.com/?p=47#comment-930</guid>
		<description>I wanted to mention SourceForge as a huge offender here.  Basically, you login with openid, then you register as usual, but you can choose to login in the future with openid for that account.  WTF?</description>
		<content:encoded><![CDATA[<p>I wanted to mention SourceForge as a huge offender here.  Basically, you login with openid, then you register as usual, but you can choose to login in the future with openid for that account.  WTF?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

