<?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: Beef: Usernames are a Terrible Login Requirement</title>
	<atom:link href="http://www.acleandesign.com/2009/05/usernames-are-a-terrible-login-requirement/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.acleandesign.com/2009/05/usernames-are-a-terrible-login-requirement/</link>
	<description>Innovation in usability research and interaction design.</description>
	<lastBuildDate>Thu, 09 Sep 2010 02:46:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Livia Labate</title>
		<link>http://www.acleandesign.com/2009/05/usernames-are-a-terrible-login-requirement/comment-page-1/#comment-1710</link>
		<dc:creator>Livia Labate</dc:creator>
		<pubDate>Tue, 16 Feb 2010 18:43:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.acleandesign.com/?p=205#comment-1710</guid>
		<description>You&#039;re right, it&#039;s time to do something about this. *pulls up sleeves*</description>
		<content:encoded><![CDATA[<p>You&#8217;re right, it&#8217;s time to do something about this. *pulls up sleeves*</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt M</title>
		<link>http://www.acleandesign.com/2009/05/usernames-are-a-terrible-login-requirement/comment-page-1/#comment-417</link>
		<dc:creator>Matt M</dc:creator>
		<pubDate>Mon, 03 Aug 2009 13:01:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.acleandesign.com/?p=205#comment-417</guid>
		<description>I think that reason that many system designers end up employing a username instead of an email address, is because designing the logic for the case of a user having to change their email address ends up being too complex.</description>
		<content:encoded><![CDATA[<p>I think that reason that many system designers end up employing a username instead of an email address, is because designing the logic for the case of a user having to change their email address ends up being too complex.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cuesta</title>
		<link>http://www.acleandesign.com/2009/05/usernames-are-a-terrible-login-requirement/comment-page-1/#comment-307</link>
		<dc:creator>Mike Cuesta</dc:creator>
		<pubDate>Mon, 29 Jun 2009 20:30:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.acleandesign.com/?p=205#comment-307</guid>
		<description>I think it really depends on the kind of site. There are some communicate that you&#039;ll want to be involved in and you won&#039;t particularly want to be using your real name. (Gaming communities are the best example). 

I agree with Loren that it&#039;s usually more cumbersome than it is helpful, and should probably never be used for the login credentials.</description>
		<content:encoded><![CDATA[<p>I think it really depends on the kind of site. There are some communicate that you&#8217;ll want to be involved in and you won&#8217;t particularly want to be using your real name. (Gaming communities are the best example). </p>
<p>I agree with Loren that it&#8217;s usually more cumbersome than it is helpful, and should probably never be used for the login credentials.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: W. Scott Williams</title>
		<link>http://www.acleandesign.com/2009/05/usernames-are-a-terrible-login-requirement/comment-page-1/#comment-292</link>
		<dc:creator>W. Scott Williams</dc:creator>
		<pubDate>Fri, 05 Jun 2009 09:32:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.acleandesign.com/?p=205#comment-292</guid>
		<description>While I totally agree with the nightmare of login schemas, I do enjoy having the option of using email or username for login on a site (like Twitter). I plan on offering both options on future UI designs for login forms. There really should be a law. :-)

However, being constantly aware of security and bots and spiders and the other evil minions of the phishers on the interwebs, I have taken the (slightly paranoid) route of setting up a Gmail account specifically for the purpose of logging into accounts. While this won&#039;t help my current registrations, I will be using it going forward.

Why Gmail? Well, 1st it&#039;s free; 2nd Gmail&#039;s spam filter is pretty hard to beat; 3rd I can pretty much access Gmail from anywhere (desktop mail client, web, mobile device). It allows not only the inevitable spam a place to die a slow 30 day death, but also keeps my personal email inbox(es) clean and safe. It also provides a centralized dumping ground for all correspondence of my online life.

Just my 2¢</description>
		<content:encoded><![CDATA[<p>While I totally agree with the nightmare of login schemas, I do enjoy having the option of using email or username for login on a site (like Twitter). I plan on offering both options on future UI designs for login forms. There really should be a law. <img src='http://www.acleandesign.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>However, being constantly aware of security and bots and spiders and the other evil minions of the phishers on the interwebs, I have taken the (slightly paranoid) route of setting up a Gmail account specifically for the purpose of logging into accounts. While this won&#8217;t help my current registrations, I will be using it going forward.</p>
<p>Why Gmail? Well, 1st it&#8217;s free; 2nd Gmail&#8217;s spam filter is pretty hard to beat; 3rd I can pretty much access Gmail from anywhere (desktop mail client, web, mobile device). It allows not only the inevitable spam a place to die a slow 30 day death, but also keeps my personal email inbox(es) clean and safe. It also provides a centralized dumping ground for all correspondence of my online life.</p>
<p>Just my 2¢</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AdamC</title>
		<link>http://www.acleandesign.com/2009/05/usernames-are-a-terrible-login-requirement/comment-page-1/#comment-290</link>
		<dc:creator>AdamC</dc:creator>
		<pubDate>Sat, 30 May 2009 00:28:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.acleandesign.com/?p=205#comment-290</guid>
		<description>I agree. The user name can be used to keep a email address private, but to actually log into the system the email address is not only unique, but memorable. I can remember every email address I&#039;ve ever had (in over 15 years of being on the net).</description>
		<content:encoded><![CDATA[<p>I agree. The user name can be used to keep a email address private, but to actually log into the system the email address is not only unique, but memorable. I can remember every email address I&#8217;ve ever had (in over 15 years of being on the net).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dmitry</title>
		<link>http://www.acleandesign.com/2009/05/usernames-are-a-terrible-login-requirement/comment-page-1/#comment-285</link>
		<dc:creator>Dmitry</dc:creator>
		<pubDate>Sat, 23 May 2009 08:47:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.acleandesign.com/?p=205#comment-285</guid>
		<description>Right things! Look at Friendfeeds authorization model. I find it most user-friendly: you can use both of email or login for authorization.</description>
		<content:encoded><![CDATA[<p>Right things! Look at Friendfeeds authorization model. I find it most user-friendly: you can use both of email or login for authorization.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
