<?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: Roll your own OpenID, the easy way</title>
	<atom:link href="http://blog.iconara.net/2008/08/13/roll-your-own-openid-the-easy-way/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.iconara.net/2008/08/13/roll-your-own-openid-the-easy-way/</link>
	<description></description>
	<lastBuildDate>Tue, 20 Jul 2010 14:27:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Eric Greveson</title>
		<link>http://blog.iconara.net/2008/08/13/roll-your-own-openid-the-easy-way/comment-page-1/#comment-7250</link>
		<dc:creator>Eric Greveson</dc:creator>
		<pubDate>Wed, 13 Aug 2008 21:34:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.iconara.net/?p=259#comment-7250</guid>
		<description>&lt;p&gt;I&#039;ve tried OpenID as an authentication service for Web apps that I&#039;ve written before, and although the coding and management consequences are quite nice (no need to worry about storing usernames and password hashes, writing &quot;reset password&quot; forms, or giving users yet another password to remember), there is a more fundamental problem.&lt;/p&gt;

&lt;p&gt;The URL-as-username model is all well and good for developers and 8-year-olds but it completely throws a large proportion of people who use computers and the internet every day as part of their job. URLs are for typing in the address bar and pasting into emails: usernames are typically either text-only fields or email addresses. Having a username beginning &quot;http://&quot; can confuse otherwise intelligent users, and makes them question if they&#039;re inputting their details correctly.&lt;/p&gt;

&lt;p&gt;The situation can be improved by partially filling in the login box (e.g. typing the &quot;http://&quot; part automatically), but it&#039;s still a bit weird compared to everything else on the web.&lt;/p&gt;

&lt;p&gt;I&#039;d personally like to see some common auth standard emerge, even if it is OpenID, but I won&#039;t be inflicting it on my users again for a while yet.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;ve tried OpenID as an authentication service for Web apps that I&#8217;ve written before, and although the coding and management consequences are quite nice (no need to worry about storing usernames and password hashes, writing &#8220;reset password&#8221; forms, or giving users yet another password to remember), there is a more fundamental problem.</p>

<p>The URL-as-username model is all well and good for developers and 8-year-olds but it completely throws a large proportion of people who use computers and the internet every day as part of their job. URLs are for typing in the address bar and pasting into emails: usernames are typically either text-only fields or email addresses. Having a username beginning &#8220;http://&#8221; can confuse otherwise intelligent users, and makes them question if they&#8217;re inputting their details correctly.</p>

<p>The situation can be improved by partially filling in the login box (e.g. typing the &#8220;http://&#8221; part automatically), but it&#8217;s still a bit weird compared to everything else on the web.</p>

<p>I&#8217;d personally like to see some common auth standard emerge, even if it is OpenID, but I won&#8217;t be inflicting it on my users again for a while yet.</p>]]></content:encoded>
	</item>
</channel>
</rss>
