<?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: UI Design Mistakes</title>
	<atom:link href="http://www.netsplit.com/2007/10/07/ui-design-mistakes/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.netsplit.com/2007/10/07/ui-design-mistakes/</link>
	<description></description>
	<pubDate>Tue, 06 Jan 2009 22:05:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jon</title>
		<link>http://www.netsplit.com/2007/10/07/ui-design-mistakes/comment-page-1/#comment-853</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Mon, 02 Jun 2008 14:11:34 +0000</pubDate>
		<guid isPermaLink="false">#comment-853</guid>
		<description>on first reading I thought this was insane. Then, I thought, what if Scott meant take the text input, hash it assuming caps is off, hash it assuming caps is on, try both.</description>
		<content:encoded><![CDATA[<p>on first reading I thought this was insane. Then, I thought, what if Scott meant take the text input, hash it assuming caps is off, hash it assuming caps is on, try both.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alex</title>
		<link>http://www.netsplit.com/2007/10/07/ui-design-mistakes/comment-page-1/#comment-717</link>
		<dc:creator>alex</dc:creator>
		<pubDate>Mon, 21 Jan 2008 07:11:23 +0000</pubDate>
		<guid isPermaLink="false">#comment-717</guid>
		<description>If you knew how passwords were encrypted, you would realize that the password checker has no idea that your password rejection is due to a case figure. But since it sees that the caps lock key is on, it gives an advice that it may be your issue.
In fact the system only know a hash of your password, that was generated when you created it. There is no way to figure out the original password from this hash.
Then, everytime some program asks for your password, it in hashs your entry and compare the resulting hash with the one stored on system. And if it does not match, it is rejected.
You see, at no time you original password is compared, and so no guess about case sensitive can be done.</description>
		<content:encoded><![CDATA[<p>If you knew how passwords were encrypted, you would realize that the password checker has no idea that your password rejection is due to a case figure. But since it sees that the caps lock key is on, it gives an advice that it may be your issue.<br />
In fact the system only know a hash of your password, that was generated when you created it. There is no way to figure out the original password from this hash.<br />
Then, everytime some program asks for your password, it in hashs your entry and compare the resulting hash with the one stored on system. And if it does not match, it is rejected.<br />
You see, at no time you original password is compared, and so no guess about case sensitive can be done.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: H Jalonen</title>
		<link>http://www.netsplit.com/2007/10/07/ui-design-mistakes/comment-page-1/#comment-239</link>
		<dc:creator>H Jalonen</dc:creator>
		<pubDate>Tue, 09 Oct 2007 23:52:35 +0000</pubDate>
		<guid isPermaLink="false">#comment-239</guid>
		<description>No, I see that the problem in UI design lies even deeper.

These comments have shown that some people seem to actually use Caps Lock key. But just like your suggestion and, overall, the need for notification about Caps Lock being on shows that for many people the Caps Lock key is totally useless and always in the way. Yes, useless! "It is too big." "It is in the wrong place." "Using shift key is much more handy." etc. 

People who need Caps Lock usually know that they need it and vice versa.

So to real solution: why there is no easy way to turn off your Caps Lock key? If I recall correctly, in Windows there is no way to adjust what your computer does when you press Caps Lock. Ubuntu is no better. Last time I checked (more than a year ago) there were seven (7) different choices for Caps Lock behaviour - none of them was "Off". None! Feel free to correct me if I am wrong. Actually, this time I would be glad if I were wrong.

OK, this is not an ultimate solution either. A screensaver program knows who is using the computer because user has logged in and user's preferences have been loaded, but what about login screen after computer startup. There the problem would still be present and a Caps Lock notification is needed. As always, if you have a problem, you will have multiple versions of the same problem.
</description>
		<content:encoded><![CDATA[<p>No, I see that the problem in UI design lies even deeper.</p>
<p>These comments have shown that some people seem to actually use Caps Lock key. But just like your suggestion and, overall, the need for notification about Caps Lock being on shows that for many people the Caps Lock key is totally useless and always in the way. Yes, useless! &#8220;It is too big.&#8221; &#8220;It is in the wrong place.&#8221; &#8220;Using shift key is much more handy.&#8221; etc. </p>
<p>People who need Caps Lock usually know that they need it and vice versa.</p>
<p>So to real solution: why there is no easy way to turn off your Caps Lock key? If I recall correctly, in Windows there is no way to adjust what your computer does when you press Caps Lock. Ubuntu is no better. Last time I checked (more than a year ago) there were seven (7) different choices for Caps Lock behaviour - none of them was &#8220;Off&#8221;. None! Feel free to correct me if I am wrong. Actually, this time I would be glad if I were wrong.</p>
<p>OK, this is not an ultimate solution either. A screensaver program knows who is using the computer because user has logged in and user&#8217;s preferences have been loaded, but what about login screen after computer startup. There the problem would still be present and a Caps Lock notification is needed. As always, if you have a problem, you will have multiple versions of the same problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robin</title>
		<link>http://www.netsplit.com/2007/10/07/ui-design-mistakes/comment-page-1/#comment-238</link>
		<dc:creator>Robin</dc:creator>
		<pubDate>Tue, 09 Oct 2007 21:53:28 +0000</pubDate>
		<guid isPermaLink="false">#comment-238</guid>
		<description>Sascha: Don't you have the umlaut "dead key"? It's located to the right of the Ã¼/Ã¨ key â€“ you can press it (and nothing will appear yet, that's why it's called dead key) and then write "U" and you'll get "Ãœ".</description>
		<content:encoded><![CDATA[<p>Sascha: Don&#8217;t you have the umlaut &#8220;dead key&#8221;? It&#8217;s located to the right of the Ã¼/Ã¨ key â€“ you can press it (and nothing will appear yet, that&#8217;s why it&#8217;s called dead key) and then write &#8220;U&#8221; and you&#8217;ll get &#8220;Ãœ&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eivind Uggedal</title>
		<link>http://www.netsplit.com/2007/10/07/ui-design-mistakes/comment-page-1/#comment-237</link>
		<dc:creator>Eivind Uggedal</dc:creator>
		<pubDate>Tue, 09 Oct 2007 01:50:52 +0000</pubDate>
		<guid isPermaLink="false">#comment-237</guid>
		<description>Like other people have mentioned before me: I've often witnessed inexperienced users (during my 1st line support duties) who use the CAPS-LOCK key for entering mixed case passwords.</description>
		<content:encoded><![CDATA[<p>Like other people have mentioned before me: I&#8217;ve often witnessed inexperienced users (during my 1st line support duties) who use the CAPS-LOCK key for entering mixed case passwords.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sascha</title>
		<link>http://www.netsplit.com/2007/10/07/ui-design-mistakes/comment-page-1/#comment-236</link>
		<dc:creator>Sascha</dc:creator>
		<pubDate>Mon, 08 Oct 2007 21:11:50 +0000</pubDate>
		<guid isPermaLink="false">#comment-236</guid>
		<description>I use a swiss german keyboard, there are some keys I simply can't enter without caps lock (for example capital umlauts), so it would be a really bad idea to simply disable it, as it would be impossible to login with a password that contains such a char.</description>
		<content:encoded><![CDATA[<p>I use a swiss german keyboard, there are some keys I simply can&#8217;t enter without caps lock (for example capital umlauts), so it would be a really bad idea to simply disable it, as it would be impossible to login with a password that contains such a char.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wolfger</title>
		<link>http://www.netsplit.com/2007/10/07/ui-design-mistakes/comment-page-1/#comment-235</link>
		<dc:creator>wolfger</dc:creator>
		<pubDate>Mon, 08 Oct 2007 17:20:18 +0000</pubDate>
		<guid isPermaLink="false">#comment-235</guid>
		<description>Another UI design mistake: a Submit button (such as the one I'm about to press) that grays out after you press it, but gives no indication as to whether or not pressing it accomplished anything.</description>
		<content:encoded><![CDATA[<p>Another UI design mistake: a Submit button (such as the one I&#8217;m about to press) that grays out after you press it, but gives no indication as to whether or not pressing it accomplished anything.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wolfger</title>
		<link>http://www.netsplit.com/2007/10/07/ui-design-mistakes/comment-page-1/#comment-234</link>
		<dc:creator>wolfger</dc:creator>
		<pubDate>Mon, 08 Oct 2007 17:15:49 +0000</pubDate>
		<guid isPermaLink="false">#comment-234</guid>
		<description>Yeah, I'm going to have to pile on and say "lousy idea". For example, one of the passwords I use is 4 capital letters followed by 4 lower-case letters and one number. I always use the caps lock for the first 4 letters, since those 4 are not all typed with the same hand. 

You are correct that notifying the user after the fact is bad design, but your solution is worse. A better solution is to notify the user when caps-lock is on, *as he is typing* (because yeah, I sometimes hit caps lock instead of shift by mistake, and I can't even see the little green light on my keyboard).</description>
		<content:encoded><![CDATA[<p>Yeah, I&#8217;m going to have to pile on and say &#8220;lousy idea&#8221;. For example, one of the passwords I use is 4 capital letters followed by 4 lower-case letters and one number. I always use the caps lock for the first 4 letters, since those 4 are not all typed with the same hand. </p>
<p>You are correct that notifying the user after the fact is bad design, but your solution is worse. A better solution is to notify the user when caps-lock is on, *as he is typing* (because yeah, I sometimes hit caps lock instead of shift by mistake, and I can&#8217;t even see the little green light on my keyboard).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wolfger</title>
		<link>http://www.netsplit.com/2007/10/07/ui-design-mistakes/comment-page-1/#comment-233</link>
		<dc:creator>wolfger</dc:creator>
		<pubDate>Mon, 08 Oct 2007 17:10:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-233</guid>
		<description>Yeah, I'm going to have to pile on and say "lousy idea". For example, one of the passwords I use is 4 capital letters followed by 4 lower-case letters and one number. I always use the caps lock for the first 4 letters, since those 4 are not all typed with the same hand. 

You are correct that notifying the user after the fact is bad design, but your solution is worse. A better solution is to notify the user when caps-lock is on, *as he is typing* (because yeah, I sometimes hit caps lock instead of shift by mistake, and I can't even see the little green light on my keyboard).</description>
		<content:encoded><![CDATA[<p>Yeah, I&#8217;m going to have to pile on and say &#8220;lousy idea&#8221;. For example, one of the passwords I use is 4 capital letters followed by 4 lower-case letters and one number. I always use the caps lock for the first 4 letters, since those 4 are not all typed with the same hand. </p>
<p>You are correct that notifying the user after the fact is bad design, but your solution is worse. A better solution is to notify the user when caps-lock is on, *as he is typing* (because yeah, I sometimes hit caps lock instead of shift by mistake, and I can&#8217;t even see the little green light on my keyboard).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philipp Kern</title>
		<link>http://www.netsplit.com/2007/10/07/ui-design-mistakes/comment-page-1/#comment-232</link>
		<dc:creator>Philipp Kern</dc:creator>
		<pubDate>Mon, 08 Oct 2007 10:05:53 +0000</pubDate>
		<guid isPermaLink="false">#comment-232</guid>
		<description>Caps lock helps when you are typing passwords one-handed (out of whatever reason).</description>
		<content:encoded><![CDATA[<p>Caps lock helps when you are typing passwords one-handed (out of whatever reason).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
