<?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: Why do passwords appear as dots in a form?</title>
	<atom:link href="http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form/feed" rel="self" type="application/rss+xml" />
	<link>http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form</link>
	<description>Articles &#38; reviews on webdesign, user experience (ux), web usability and online applications.</description>
	<lastBuildDate>Thu, 15 Jul 2010 11:21:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Paul Olyslager</title>
		<link>http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form/comment-page-1#comment-517</link>
		<dc:creator>Paul Olyslager</dc:creator>
		<pubDate>Mon, 11 Jan 2010 11:21:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.paulolyslager.com/?p=189#comment-517</guid>
		<description>I&#039;ve found a nice solution for the Iphone-like approach on the website of &lt;a href=&quot;https://www.queridodesign.net/blog/passshark&quot; title=&quot;website of queridodesign&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;Queridodesign&lt;/a&gt;. It is using Mootools and works in Safari 3+, Firefox 3+, Opera 10+, Internet Explorer 6 and 7.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve found a nice solution for the Iphone-like approach on the website of <a href="https://www.queridodesign.net/blog/passshark" title="website of queridodesign" target="_blank" rel="nofollow">Queridodesign</a>. It is using Mootools and works in Safari 3+, Firefox 3+, Opera 10+, Internet Explorer 6 and 7.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jaime</title>
		<link>http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form/comment-page-1#comment-167</link>
		<dc:creator>Jaime</dc:creator>
		<pubDate>Wed, 18 Nov 2009 15:27:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.paulolyslager.com/?p=189#comment-167</guid>
		<description>@&lt;a href=&quot;#comment-166&quot; rel=&quot;nofollow&quot;&gt;Paul Olyslager&lt;/a&gt;:  Thanks Paul! I by no chance mean there should not be room for improvement. I do agree that if there&#039;s a chance to improve, so it shall be done in a tasteful and effective way. The thing is, a password input box that displays the letter and then transforms to a asterisk, is just a bit more safe than having the box display plaintext. A person with good visual ability and memory looking to steal your password will do so by looking at your plain text, by looking ad the changing letters, or by looking at your fingers when you type. In that same order you could say there&#039;s no protection with the first, somewhat a protection with the second and as much a protection with the last option. The main reason the iphone&#039;s password input boxes work like that is because of two reasons. First the fact that the phone is always in close proximity to your person and it&#039;s easier to &quot;protect&quot; your password entering with your body (which most people do, if only because most people use the phone in a position where people can&#039;t snoop from behind). And Second the fact that typing in an iphone is by definition harder than typing on a regular keyboard, as well as it&#039;s a lot more error prone. Add to that the fact that if I can probably type my password wrongly 2 times and get it the third time on the browser faster than typing it on an iphone (though that might be because I really don&#039;t get a lot of use from opposable thumbs). It&#039;s that much annoying to have to retype your password on the phone than on a laptop or desktop. I believe Apple decided to sacrifice a little security to make the experience easier for people. But we shouldn&#039;t do that on the web, because the security risk is a lot higher than on a mobile phone.</description>
		<content:encoded><![CDATA[<p>@<a href="#comment-166" rel="nofollow">Paul Olyslager</a>:  Thanks Paul! I by no chance mean there should not be room for improvement. I do agree that if there&#8217;s a chance to improve, so it shall be done in a tasteful and effective way. The thing is, a password input box that displays the letter and then transforms to a asterisk, is just a bit more safe than having the box display plaintext. A person with good visual ability and memory looking to steal your password will do so by looking at your plain text, by looking ad the changing letters, or by looking at your fingers when you type. In that same order you could say there&#8217;s no protection with the first, somewhat a protection with the second and as much a protection with the last option. The main reason the iphone&#8217;s password input boxes work like that is because of two reasons. First the fact that the phone is always in close proximity to your person and it&#8217;s easier to &#8220;protect&#8221; your password entering with your body (which most people do, if only because most people use the phone in a position where people can&#8217;t snoop from behind). And Second the fact that typing in an iphone is by definition harder than typing on a regular keyboard, as well as it&#8217;s a lot more error prone. Add to that the fact that if I can probably type my password wrongly 2 times and get it the third time on the browser faster than typing it on an iphone (though that might be because I really don&#8217;t get a lot of use from opposable thumbs). It&#8217;s that much annoying to have to retype your password on the phone than on a laptop or desktop. I believe Apple decided to sacrifice a little security to make the experience easier for people. But we shouldn&#8217;t do that on the web, because the security risk is a lot higher than on a mobile phone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Olyslager</title>
		<link>http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form/comment-page-1#comment-166</link>
		<dc:creator>Paul Olyslager</dc:creator>
		<pubDate>Wed, 18 Nov 2009 14:15:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.paulolyslager.com/?p=189#comment-166</guid>
		<description>@&lt;a href=&quot;#comment-157&quot; rel=&quot;nofollow&quot;&gt;Jaime&lt;/a&gt;:
First of all, thank you for your comment. It is always nice to hear someone else&#039;s opinion and takes the time to clarify it. I must say I partly agree with your comment. You shouldn&#039;t change the usability of something that is so standarized as the dots of a password field, but that doesn&#039;t mean there is no room for improvement (or at least have a look for other possibilities for that matter). Re-inventing the wheel is not necessary, but improving it to the changing external conditions without touching the basics of the wheel (it needs to roll) is. The essence of a password field are the dots itself, without these the field is not recognisable as a passform field. In all the alternatives mentioned in this article I kept the dots for consistency reasons. I do understand the solution of Apple, changing the character in a dot after you entered the next character makes sense. People still recognise it as a passform field, it is still consistent and it&#039;s more difficult to make a typo. I&#039;m not saying that this option will be the new standard, but it is nice to know that people still think about the functionality.</description>
		<content:encoded><![CDATA[<p>@<a href="#comment-157" rel="nofollow">Jaime</a>:<br />
First of all, thank you for your comment. It is always nice to hear someone else&#8217;s opinion and takes the time to clarify it. I must say I partly agree with your comment. You shouldn&#8217;t change the usability of something that is so standarized as the dots of a password field, but that doesn&#8217;t mean there is no room for improvement (or at least have a look for other possibilities for that matter). Re-inventing the wheel is not necessary, but improving it to the changing external conditions without touching the basics of the wheel (it needs to roll) is. The essence of a password field are the dots itself, without these the field is not recognisable as a passform field. In all the alternatives mentioned in this article I kept the dots for consistency reasons. I do understand the solution of Apple, changing the character in a dot after you entered the next character makes sense. People still recognise it as a passform field, it is still consistent and it&#8217;s more difficult to make a typo. I&#8217;m not saying that this option will be the new standard, but it is nice to know that people still think about the functionality.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jaime</title>
		<link>http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form/comment-page-1#comment-157</link>
		<dc:creator>Jaime</dc:creator>
		<pubDate>Mon, 16 Nov 2009 11:55:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.paulolyslager.com/?p=189#comment-157</guid>
		<description>I&#039;ve heard this a gazillion times. &quot;Why mask passwords? Give control back to the users!&quot;
There are various reasons why this is not a good idea.
1) You may think that &quot;over the shoulder&quot; password peeking doesn&#039;t occur anymore, but it&#039;s far more likely to happen now than ever. Be it your girlfriend trying to figure out your Facebook password to see if you&#039;re cheating, or the florist that brought flowers to your office who is really a corporate spy. No this is not a movie script. This stuff does happen.
2) It has worked the way it is for ages. Why change something that works? Most people authenticate many different ways. Browser&#039;s password manager, a password managing app, the leave their account logged in, or are so used to typing their password that muscle memory takes care of the rest. Is it really that hard to type a string of 8 to 13 characters correctly?
3) Users grew up with the idea that masked passwords mean security. You take that away and people will think twice about using your website. Though password masking does not equal security, it&#039;s to late to change the perception of it all.
There&#039;s a point where usability pioneering starts getting in the way. Study the effects of positioning, whitespace, simplicity and complexity in interfaces, call to action importance hierarchies, and the whole plethora of other usability issues; but really, this stuff works well already, and changing it will make you the outcast in the list of sites the user uses. If out of the 10 sites I use 9 mask passwords and 1 doesn&#039;t, I might associate that with not being safe or meaning something completely different to what it would mean otherwise.
To finish up, one of the most important concepts in user experience is consistency, and this doesn&#039;t only apply to the design of your site. It is just as important to maintain a consistency in certain elements the user interacts with throughout the whole web, and one of said components is the password field.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve heard this a gazillion times. &#8220;Why mask passwords? Give control back to the users!&#8221;</p>
<p>There are various reasons why this is not a good idea. </p>
<p>1) You may think that &#8220;over the shoulder&#8221; password peeking doesn&#8217;t occur anymore, but it&#8217;s far more likely to happen now than ever. Be it your girlfriend trying to figure out your Facebook password to see if you&#8217;re cheating, or the florist that brought flowers to your office who is really a corporate spy. No this is not a movie script. This stuff does happen.</p>
<p>2) It has worked the way it is for ages. Why change something that works? Most people authenticate many different ways. Browser&#8217;s password manager, a password managing app, the leave their account logged in, or are so used to typing their password that muscle memory takes care of the rest. Is it really that hard to type a string of 8 to 13 characters correctly? </p>
<p>3) Users grew up with the idea that masked passwords mean security. You take that away and people will think twice about using your website. Though password masking does not equal security, it&#8217;s to late to change the perception of it all. </p>
<p>There&#8217;s a point where usability pioneering starts getting in the way. Study the effects of positioning, whitespace, simplicity and complexity in interfaces, call to action importance hierarchies, and the whole plethora of other usability issues; but really, this stuff works well already, and changing it will make you the outcast in the list of sites the user uses. If out of the 10 sites I use 9 mask passwords and 1 doesn&#8217;t, I might associate that with not being safe or meaning something completely different to what it would mean otherwise. </p>
<p>To finish up, one of the most important concepts in user experience is consistency, and this doesn&#8217;t only apply to the design of your site. It is just as important to maintain a consistency in certain elements the user interacts with throughout the whole web, and one of said components is the password field.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sue</title>
		<link>http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form/comment-page-1#comment-154</link>
		<dc:creator>Sue</dc:creator>
		<pubDate>Mon, 16 Nov 2009 01:59:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.paulolyslager.com/?p=189#comment-154</guid>
		<description>The dots are there for security, so someone looking over your shoulder can&#039;t find out your password (social engineering hacks).
In our software program, when you enter a password, such as for your key, it&#039;s in all dots. But there&#039;s a check box you can select that allows you to &quot;Show keystrokes.&quot; If you know no one is at your back, you can select this to verify you&#039;ve typed the correct password. In our case, it&#039;s a simple usability fix. :)</description>
		<content:encoded><![CDATA[<p>The dots are there for security, so someone looking over your shoulder can&#8217;t find out your password (social engineering hacks).</p>
<p>In our software program, when you enter a password, such as for your key, it&#8217;s in all dots. But there&#8217;s a check box you can select that allows you to &#8220;Show keystrokes.&#8221; If you know no one is at your back, you can select this to verify you&#8217;ve typed the correct password. In our case, it&#8217;s a simple usability fix. <img src='http://www.paulolyslager.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: linkzdirect.com</title>
		<link>http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form/comment-page-1#comment-97</link>
		<dc:creator>linkzdirect.com</dc:creator>
		<pubDate>Sun, 01 Nov 2009 13:36:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.paulolyslager.com/?p=189#comment-97</guid>
		<description>&lt;strong&gt;Why do passwords appear as dots in a form? &#124; paul olyslager...&lt;/strong&gt;
Ever wondered why passwords appear as dots in a form?A system which is not userfriendly because you can&#039;t see the character you just typed. Solution is simple....</description>
		<content:encoded><![CDATA[<p><strong>Why do passwords appear as dots in a form? | paul olyslager&#8230;</strong></p>
<p>Ever wondered why passwords appear as dots in a form?A system which is not userfriendly because you can&#8217;t see the character you just typed. Solution is simple&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: zabox.net</title>
		<link>http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form/comment-page-1#comment-76</link>
		<dc:creator>zabox.net</dc:creator>
		<pubDate>Sun, 25 Oct 2009 13:13:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.paulolyslager.com/?p=189#comment-76</guid>
		<description>&lt;strong&gt;Why do passwords appear as dots in a form? &#124; paul olyslager...&lt;/strong&gt;
When I want to subscribe myself for a newsletter, website, online application or want to sign in, I need to put in my password. This is the easiest way to protect websites/applications and it works, but what I really don’t understand is why a password ...</description>
		<content:encoded><![CDATA[<p><strong>Why do passwords appear as dots in a form? | paul olyslager&#8230;</strong></p>
<p>When I want to subscribe myself for a newsletter, website, online application or want to sign in, I need to put in my password. This is the easiest way to protect websites/applications and it works, but what I really don’t understand is why a password &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: clippingimages</title>
		<link>http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form/comment-page-1#comment-54</link>
		<dc:creator>clippingimages</dc:creator>
		<pubDate>Sun, 18 Oct 2009 10:36:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.paulolyslager.com/?p=189#comment-54</guid>
		<description>Very interesting article. Very informative also. This question also slipped my mind. Thanks to share this awesome article. Really now i got some clear idea now. :)</description>
		<content:encoded><![CDATA[<p>Very interesting article. Very informative also. This question also slipped my mind. Thanks to share this awesome article. Really now i got some clear idea now. <img src='http://www.paulolyslager.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: favSHARE</title>
		<link>http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form/comment-page-1#comment-33</link>
		<dc:creator>favSHARE</dc:creator>
		<pubDate>Tue, 06 Oct 2009 19:37:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.paulolyslager.com/?p=189#comment-33</guid>
		<description>This article has been shared on &lt;a href=&quot;http://www.favshare.net&quot; rel=&quot;nofollow&quot;&gt;&lt;b&gt;favSHARE.net&lt;/b&gt;&lt;/a&gt;. Go and vote it!</description>
		<content:encoded><![CDATA[<p>This article has been shared on <a href="http://www.favshare.net" rel="nofollow"><b>favSHARE.net</b></a>. Go and vote it!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Olyslager</title>
		<link>http://www.paulolyslager.com/why-do-passwords-appear-as-dots-in-a-form/comment-page-1#comment-25</link>
		<dc:creator>Paul Olyslager</dc:creator>
		<pubDate>Tue, 29 Sep 2009 10:40:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.paulolyslager.com/?p=189#comment-25</guid>
		<description>Interesting point on the auto-complete dmitry, didn&#039;t think of that one. I think that the solution, which was shown to us by Kristof, improves the usability but also upholds the safety of the entire operation (be it for a quick login or filling in a long form), this without an extra click.
I&#039;ve found a working example, written by &lt;a href=&quot;http://experienceinternet.co.uk/blog/archive/an-alternative-approach-to-password-confirmation/.&quot; title=&quot;website of stephen lewis&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;Stephen Lewis&lt;/a&gt;. Although it works in FF, it seems to fail in IE7. With every keystroke, the amount of digits is doubled. I&#039;m still on the lookout for a perfectly working example.</description>
		<content:encoded><![CDATA[<p>Interesting point on the auto-complete dmitry, didn&#8217;t think of that one. I think that the solution, which was shown to us by Kristof, improves the usability but also upholds the safety of the entire operation (be it for a quick login or filling in a long form), this without an extra click.<br />
I&#8217;ve found a working example, written by <a href="http://experienceinternet.co.uk/blog/archive/an-alternative-approach-to-password-confirmation/." title="website of stephen lewis" target="_blank" rel="nofollow">Stephen Lewis</a>. Although it works in FF, it seems to fail in IE7. With every keystroke, the amount of digits is doubled. I&#8217;m still on the lookout for a perfectly working example.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
