<?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: Does OpenID need to be hard?</title>
	<atom:link href="http://factoryjoe.com/blog/2009/04/06/does-openid-need-to-be-hard/feed/" rel="self" type="application/rss+xml" />
	<link>http://factoryjoe.com/blog/2009/04/06/does-openid-need-to-be-hard/</link>
	<description>This can all be made better. Ready? Begin.</description>
	<lastBuildDate>Sat, 20 Mar 2010 00:41:35 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Designing for the gut - SxDSalon: A group blog on social interaction design</title>
		<link>http://factoryjoe.com/blog/2009/04/06/does-openid-need-to-be-hard/comment-page-1/#comment-117277</link>
		<dc:creator>Designing for the gut - SxDSalon: A group blog on social interaction design</dc:creator>
		<pubDate>Sun, 14 Feb 2010 18:31:35 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=1318#comment-117277</guid>
		<description>[...] experience with choice is an engineer&#8217;s solution that I&#8217;ve come to accept is bound to fail. Instead, the act of selecting an identity to &#8220;perform as&#8221; must happen early in [...]</description>
		<content:encoded><![CDATA[<p>[...] experience with choice is an engineer&#8217;s solution that I&#8217;ve come to accept is bound to fail. Instead, the act of selecting an identity to &#8220;perform as&#8221; must happen early in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Hills</title>
		<link>http://factoryjoe.com/blog/2009/04/06/does-openid-need-to-be-hard/comment-page-1/#comment-117261</link>
		<dc:creator>Chris Hills</dc:creator>
		<pubDate>Fri, 12 Feb 2010 13:30:31 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=1318#comment-117261</guid>
		<description>The OpenID I use most often is an i-name (&quot;=chris.hills&quot; or &quot;xri://=chris.hills&quot;) since it is short and sweet, and has proper service discovery through xrds.

http://dev.inames.net/wiki/XRI_and_OpenID</description>
		<content:encoded><![CDATA[<p>The OpenID I use most often is an i-name (&#8220;=chris.hills&#8221; or &#8220;xri://=chris.hills&#8221;) since it is short and sweet, and has proper service discovery through xrds.</p>
<p><a href="http://dev.inames.net/wiki/XRI_and_OpenID" rel="nofollow">http://dev.inames.net/wiki/XRI_and_OpenID</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Some links for light reading (7/4/09) &#171; Max Design</title>
		<link>http://factoryjoe.com/blog/2009/04/06/does-openid-need-to-be-hard/comment-page-1/#comment-117022</link>
		<dc:creator>Some links for light reading (7/4/09) &#171; Max Design</dc:creator>
		<pubDate>Fri, 29 Jan 2010 11:18:01 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=1318#comment-117022</guid>
		<description>[...] Does OpenID need to be hard? [...]</description>
		<content:encoded><![CDATA[<p>[...] Does OpenID need to be hard? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Links for 2010-01-11 &#124; the fabulous freak</title>
		<link>http://factoryjoe.com/blog/2009/04/06/does-openid-need-to-be-hard/comment-page-1/#comment-116415</link>
		<dc:creator>Links for 2010-01-11 &#124; the fabulous freak</dc:creator>
		<pubDate>Mon, 11 Jan 2010 19:39:50 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=1318#comment-116415</guid>
		<description>[...] Does OpenID need to be hard? [FactoryCity] [...]</description>
		<content:encoded><![CDATA[<p>[...] Does OpenID need to be hard? [FactoryCity] [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OpenID Connect &#124; FactoryCity</title>
		<link>http://factoryjoe.com/blog/2009/04/06/does-openid-need-to-be-hard/comment-page-1/#comment-114903</link>
		<dc:creator>OpenID Connect &#124; FactoryCity</dc:creator>
		<pubDate>Mon, 04 Jan 2010 23:59:07 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=1318#comment-114903</guid>
		<description>[...] been thinking about how we make OpenID both easier and sexier for quite a while now. As frustrating as the answer may be to technologists, the problem [...]</description>
		<content:encoded><![CDATA[<p>[...] been thinking about how we make OpenID both easier and sexier for quite a while now. As frustrating as the answer may be to technologists, the problem [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Designing for the gut &#124; FactoryCity</title>
		<link>http://factoryjoe.com/blog/2009/04/06/does-openid-need-to-be-hard/comment-page-1/#comment-114187</link>
		<dc:creator>Designing for the gut &#124; FactoryCity</dc:creator>
		<pubDate>Sat, 28 Nov 2009 17:27:58 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=1318#comment-114187</guid>
		<description>[...] experience with choice is an engineer&#8217;s solution that I&#8217;ve come to accept is bound to fail. Instead, the act of selecting an identity to &#8220;perform as&#8221; must happen early in [...]</description>
		<content:encoded><![CDATA[<p>[...] experience with choice is an engineer&#8217;s solution that I&#8217;ve come to accept is bound to fail. Instead, the act of selecting an identity to &#8220;perform as&#8221; must happen early in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Google Users Profiles Are OpenID Enabled &#8211; Spread OpenID</title>
		<link>http://factoryjoe.com/blog/2009/04/06/does-openid-need-to-be-hard/comment-page-1/#comment-113973</link>
		<dc:creator>Google Users Profiles Are OpenID Enabled &#8211; Spread OpenID</dc:creator>
		<pubDate>Wed, 25 Nov 2009 21:47:02 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=1318#comment-113973</guid>
		<description>[...] Google has been an OpenID provider since October 2008 already. However users had to remember a rather cryptic URL, www.google.com/accounts/o8/id, which was the same for all users. Alternatively, relying parties and users could rely on the Google login button (see below), which led to the infamous NASCAR problem of OpenID, a term coined by Daniel Burka and made famous by Chris Messina. [...]</description>
		<content:encoded><![CDATA[<p>[...] Google has been an OpenID provider since October 2008 already. However users had to remember a rather cryptic URL, <a href="http://www.google.com/accounts/o8/id" rel="nofollow">http://www.google.com/accounts/o8/id</a>, which was the same for all users. Alternatively, relying parties and users could rely on the Google login button (see below), which led to the infamous NASCAR problem of OpenID, a term coined by Daniel Burka and made famous by Chris Messina. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Unintended Side Effects - SxDSalon: A group blog on social interaction design</title>
		<link>http://factoryjoe.com/blog/2009/04/06/does-openid-need-to-be-hard/comment-page-1/#comment-113785</link>
		<dc:creator>Unintended Side Effects - SxDSalon: A group blog on social interaction design</dc:creator>
		<pubDate>Mon, 23 Nov 2009 07:43:25 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=1318#comment-113785</guid>
		<description>[...] Now when I go onto a site, a site wanting to embrace open standards, a site committed to allowing their users to sign in with authentication credentials they already have, I am assaulted by a thousand logos and options, usually in addition to the ability to create a new account. Chris Messina, labels this the Nascar problem. [...]</description>
		<content:encoded><![CDATA[<p>[...] Now when I go onto a site, a site wanting to embrace open standards, a site committed to allowing their users to sign in with authentication credentials they already have, I am assaulted by a thousand logos and options, usually in addition to the ability to create a new account. Chris Messina, labels this the Nascar problem. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emir Bukva</title>
		<link>http://factoryjoe.com/blog/2009/04/06/does-openid-need-to-be-hard/comment-page-1/#comment-113583</link>
		<dc:creator>Emir Bukva</dc:creator>
		<pubDate>Fri, 20 Nov 2009 01:34:14 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=1318#comment-113583</guid>
		<description>I think a big problem that the general public has with current implementations is the name used on links and buttons. &quot;Use OpenID&quot;; &quot;Log in with OpenID&quot;; &quot;Sign in with OpenID&quot; all have a tendency to confuse people because they contain &quot;OpenID&quot; and people have no idea what that means. Yes, I know it&#039;s the name of the thing but imagine me asking you to &quot;use Refeget!&quot; Would you have any idea what I&#039;m referring to? (It&#039;s a made up word that means nothing).

&quot;Conncect with Facebook&quot; works primarily because Facebook is so popular but it&#039;s also successful because people get it. I think microformats detection plug-ins suffer from the same problem. Most of them detect &quot;hCards&quot; instead of &quot;Contacts&quot; or &quot;hCalendards&quot; instead of &quot;Events&quot;.

Designers fight trench battles to persuade hospitals to use nomenclatures such as &quot;Ear/Nose/Throat&quot; rather than &quot;Otolaryngology&quot; when doing wayfinding systems and I bet more people would know what &quot;Otolaryngology&quot; means compared to &quot;OpenID&quot;.

I don&#039;t really have a solution, but there must be a way to separate the name of the technology from the language used in the interface to guide actions. Something along the lines of &quot;Conncect with existing account&quot; maybe? If I can use an account I already have, great. If not, guide a sign-up workflow for a preferred openID provider.</description>
		<content:encoded><![CDATA[<p>I think a big problem that the general public has with current implementations is the name used on links and buttons. &#8220;Use OpenID&#8221;; &#8220;Log in with OpenID&#8221;; &#8220;Sign in with OpenID&#8221; all have a tendency to confuse people because they contain &#8220;OpenID&#8221; and people have no idea what that means. Yes, I know it&#8217;s the name of the thing but imagine me asking you to &#8220;use Refeget!&#8221; Would you have any idea what I&#8217;m referring to? (It&#8217;s a made up word that means nothing).</p>
<p>&#8220;Conncect with Facebook&#8221; works primarily because Facebook is so popular but it&#8217;s also successful because people get it. I think microformats detection plug-ins suffer from the same problem. Most of them detect &#8220;hCards&#8221; instead of &#8220;Contacts&#8221; or &#8220;hCalendards&#8221; instead of &#8220;Events&#8221;.</p>
<p>Designers fight trench battles to persuade hospitals to use nomenclatures such as &#8220;Ear/Nose/Throat&#8221; rather than &#8220;Otolaryngology&#8221; when doing wayfinding systems and I bet more people would know what &#8220;Otolaryngology&#8221; means compared to &#8220;OpenID&#8221;.</p>
<p>I don&#8217;t really have a solution, but there must be a way to separate the name of the technology from the language used in the interface to guide actions. Something along the lines of &#8220;Conncect with existing account&#8221; maybe? If I can use an account I already have, great. If not, guide a sign-up workflow for a preferred openID provider.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Data Without Borders Episode 7: Report from the Internet Identity Workshop :: Data Without Borders</title>
		<link>http://factoryjoe.com/blog/2009/04/06/does-openid-need-to-be-hard/comment-page-1/#comment-111859</link>
		<dc:creator>Data Without Borders Episode 7: Report from the Internet Identity Workshop :: Data Without Borders</dc:creator>
		<pubDate>Mon, 09 Nov 2009 16:58:57 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=1318#comment-111859</guid>
		<description>[...] The real problem with NASCAR [...]</description>
		<content:encoded><![CDATA[<p>[...] The real problem with NASCAR [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
