<?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: Confirm Password, Idiot.</title>
	<atom:link href="http://www.keepthewebweird.com/confirm-password-idiot/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.keepthewebweird.com/confirm-password-idiot/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Thu, 03 Dec 2009 02:47:07 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: don</title>
		<link>http://www.keepthewebweird.com/confirm-password-idiot/comment-page-1/#comment-195</link>
		<dc:creator>don</dc:creator>
		<pubDate>Fri, 06 Feb 2009 16:09:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.keepthewebweird.com/?p=28#comment-195</guid>
		<description>I am just reworking a form for my site and wanted to confirm my suspessions about the password field.  Even very large companies have the password repeated, but why?  Isn&#039;t that why we have a &quot;forgot password&quot; link?</description>
		<content:encoded><![CDATA[<p>I am just reworking a form for my site and wanted to confirm my suspessions about the password field.  Even very large companies have the password repeated, but why?  Isn&#8217;t that why we have a &#8220;forgot password&#8221; link?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Buck</title>
		<link>http://www.keepthewebweird.com/confirm-password-idiot/comment-page-1/#comment-52</link>
		<dc:creator>Buck</dc:creator>
		<pubDate>Wed, 11 Jun 2008 14:38:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.keepthewebweird.com/?p=28#comment-52</guid>
		<description>That&#039;s pretty interesting, really. I wonder what users would think if there was an option next to the password field stating &quot;don&#039;t obscure my password&quot;? It would definitely take users aback if the default was that the option was checked-- I wonder if they would care that much, since they&#039;ve been trained to expect that field to be obscured, no matter what type of application they are using. 

It does make a lot of sense to *not* obscure it when they&#039;re registering initially, though.</description>
		<content:encoded><![CDATA[<p>That&#8217;s pretty interesting, really. I wonder what users would think if there was an option next to the password field stating &#8220;don&#8217;t obscure my password&#8221;? It would definitely take users aback if the default was that the option was checked&#8211; I wonder if they would care that much, since they&#8217;ve been trained to expect that field to be obscured, no matter what type of application they are using. </p>
<p>It does make a lot of sense to *not* obscure it when they&#8217;re registering initially, though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: C</title>
		<link>http://www.keepthewebweird.com/confirm-password-idiot/comment-page-1/#comment-51</link>
		<dc:creator>C</dc:creator>
		<pubDate>Wed, 11 Jun 2008 05:02:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.keepthewebweird.com/?p=28#comment-51</guid>
		<description>Just found your site via SVN. Couldn&#039;t agree with you more. Taking it one step further, why obscure it in the first place? Are there really that many people looking over your shoulder?</description>
		<content:encoded><![CDATA[<p>Just found your site via SVN. Couldn&#8217;t agree with you more. Taking it one step further, why obscure it in the first place? Are there really that many people looking over your shoulder?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.358 seconds -->

<!-- Page not cached by WP Super Cache. Could not get mutex lock. -->
