<?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: URL Literacy</title>
	<atom:link href="http://rc3.org/2010/03/02/url-literacy/feed/" rel="self" type="application/rss+xml" />
	<link>http://rc3.org/2010/03/02/url-literacy/</link>
	<description>Rafe Colburn on software development (and other topics)</description>
	<lastBuildDate>Wed, 23 May 2012 22:44:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Mike</title>
		<link>http://rc3.org/2010/03/02/url-literacy/comment-page-1/#comment-8165</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Wed, 03 Mar 2010 16:22:24 +0000</pubDate>
		<guid isPermaLink="false">http://rc3.org/?p=10831#comment-8165</guid>
		<description>&lt;p&gt;While I do agree that good design benefits everyone, the problem I&#039;ve found is that when a company/developers think they have found the One True Way(TM) of doing things, they then remove all customization options. Pidgin and other projects are notorious for this.&lt;/p&gt;

&lt;p&gt;I customize my user experience extensively, up to and including DLL hacks and sometimes, if the developers are particularly dogmatic about not allowing changes and the user interface is bad enough, modifying and compiling my own version.&lt;/p&gt;

&lt;p&gt;I&#039;m a bit insane about it, but I don&#039;t understand why so often when someone thinks they have just found the perfect design, they then lock down all customization possibilities.&lt;/p&gt;

&lt;p&gt;At that point, it seems become some kind of religious feeling, rather than the more logical admission that all users are different and benefit from different approaches and designs.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>While I do agree that good design benefits everyone, the problem I&#8217;ve found is that when a company/developers think they have found the One True Way(TM) of doing things, they then remove all customization options. Pidgin and other projects are notorious for this.</p>

<p>I customize my user experience extensively, up to and including DLL hacks and sometimes, if the developers are particularly dogmatic about not allowing changes and the user interface is bad enough, modifying and compiling my own version.</p>

<p>I&#8217;m a bit insane about it, but I don&#8217;t understand why so often when someone thinks they have just found the perfect design, they then lock down all customization possibilities.</p>

<p>At that point, it seems become some kind of religious feeling, rather than the more logical admission that all users are different and benefit from different approaches and designs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rafe</title>
		<link>http://rc3.org/2010/03/02/url-literacy/comment-page-1/#comment-8164</link>
		<dc:creator>Rafe</dc:creator>
		<pubDate>Wed, 03 Mar 2010 15:02:36 +0000</pubDate>
		<guid isPermaLink="false">http://rc3.org/?p=10831#comment-8164</guid>
		<description>&lt;p&gt;I think there are a lot of things you can do to help novices that are helpful to experienced users as well. Good design benefits everybody. I also agree that it&#039;s probably time to take a good hard look at the interaction between browsers and search engines and get the two sides to work together to create something that&#039;s better for users who don&#039;t know what they&#039;re doing, and maybe for the rest of us, too.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I think there are a lot of things you can do to help novices that are helpful to experienced users as well. Good design benefits everybody. I also agree that it&#8217;s probably time to take a good hard look at the interaction between browsers and search engines and get the two sides to work together to create something that&#8217;s better for users who don&#8217;t know what they&#8217;re doing, and maybe for the rest of us, too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Brownback</title>
		<link>http://rc3.org/2010/03/02/url-literacy/comment-page-1/#comment-8159</link>
		<dc:creator>Thomas Brownback</dc:creator>
		<pubDate>Wed, 03 Mar 2010 10:07:15 +0000</pubDate>
		<guid isPermaLink="false">http://rc3.org/?p=10831#comment-8159</guid>
		<description>&lt;p&gt;My intuitions are with Mike, and with the post, that simply designing down to the novices without any attempt at education can be dangerous. But when &lt;a href=&quot;http://www.youtube.com/watch?v=o4MwTvtyrUQ&amp;feature=player_embedded&quot; rel=&quot;nofollow&quot;&gt;Google surveyed&lt;/a&gt;, only 8% of respondents knew the difference between a browser and a search engine. At this point, education is desirable, but design seems a necessary backup.&lt;/p&gt;

&lt;p&gt;Mike articulates the worry with redesign really well. Too often we trade usability between novices and experts. But it doesn&#039;t have to be that way. Fitt&#039;s law seems to apply to everyone. The power law of practice, generally speaking, applies to all users, great and small. There might be a solution here that doesn&#039;t cripple the experience of the highly proficient user.&lt;/p&gt;

&lt;p&gt;For example, could this particular incident been avoided by tweaking Google&#039;s burstiness?&lt;/p&gt;

&lt;p&gt;Burstiness is a property of search algorithms, it basically pushes new items to the top faster. Good for aggregating breaking news, very bad for reliably getting to that site you use every day. So the solution I&#039;d propose would be to use a significantly less bursty algorithm for I&#039;m Feeling Lucky. If I&#039;m Feeling Lucky has been coopted by address bars, maybe it should be slightly more static, for experts and novices alike.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>My intuitions are with Mike, and with the post, that simply designing down to the novices without any attempt at education can be dangerous. But when <a href="http://www.youtube.com/watch?v=o4MwTvtyrUQ&amp;feature=player_embedded" rel="nofollow">Google surveyed</a>, only 8% of respondents knew the difference between a browser and a search engine. At this point, education is desirable, but design seems a necessary backup.</p>

<p>Mike articulates the worry with redesign really well. Too often we trade usability between novices and experts. But it doesn&#8217;t have to be that way. Fitt&#8217;s law seems to apply to everyone. The power law of practice, generally speaking, applies to all users, great and small. There might be a solution here that doesn&#8217;t cripple the experience of the highly proficient user.</p>

<p>For example, could this particular incident been avoided by tweaking Google&#8217;s burstiness?</p>

<p>Burstiness is a property of search algorithms, it basically pushes new items to the top faster. Good for aggregating breaking news, very bad for reliably getting to that site you use every day. So the solution I&#8217;d propose would be to use a significantly less bursty algorithm for I&#8217;m Feeling Lucky. If I&#8217;m Feeling Lucky has been coopted by address bars, maybe it should be slightly more static, for experts and novices alike.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://rc3.org/2010/03/02/url-literacy/comment-page-1/#comment-8158</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Wed, 03 Mar 2010 08:20:04 +0000</pubDate>
		<guid isPermaLink="false">http://rc3.org/?p=10831#comment-8158</guid>
		<description>&lt;p&gt;I really hate the idea of all browsers and similar tools being altered to only assist the biggest idiots among us.&lt;/p&gt;

&lt;p&gt;It makes them really difficult to use for those who know a little bit more, and extremely slow and inconvenient.&lt;/p&gt;

&lt;p&gt;I already have to mod my Firefox enough to remove all the things designed to help regular folks navigate it and the internet. Don&#039;t really want to have to do more.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I really hate the idea of all browsers and similar tools being altered to only assist the biggest idiots among us.</p>

<p>It makes them really difficult to use for those who know a little bit more, and extremely slow and inconvenient.</p>

<p>I already have to mod my Firefox enough to remove all the things designed to help regular folks navigate it and the internet. Don&#8217;t really want to have to do more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Mzyk</title>
		<link>http://rc3.org/2010/03/02/url-literacy/comment-page-1/#comment-8148</link>
		<dc:creator>Mark Mzyk</dc:creator>
		<pubDate>Tue, 02 Mar 2010 17:00:13 +0000</pubDate>
		<guid isPermaLink="false">http://rc3.org/?p=10831#comment-8148</guid>
		<description>&lt;p&gt;While of course I can&#039;t find it now, there is a Firefox plugin that changes how the url looks.  When a user is moused over the url, it looks normal, as we would expect, but when the user is not moused over it, it emphasizes the domain name much like Chrome does by highlighting it, but it also puts white space around the domain name so it stands out even more.  It was an effective way to highlight the domain name.  When people would look over my shoulder most would asked what had happened to the url.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>While of course I can&#8217;t find it now, there is a Firefox plugin that changes how the url looks.  When a user is moused over the url, it looks normal, as we would expect, but when the user is not moused over it, it emphasizes the domain name much like Chrome does by highlighting it, but it also puts white space around the domain name so it stands out even more.  It was an effective way to highlight the domain name.  When people would look over my shoulder most would asked what had happened to the url.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: room34</title>
		<link>http://rc3.org/2010/03/02/url-literacy/comment-page-1/#comment-8147</link>
		<dc:creator>room34</dc:creator>
		<pubDate>Tue, 02 Mar 2010 16:44:35 +0000</pubDate>
		<guid isPermaLink="false">http://rc3.org/?p=10831#comment-8147</guid>
		<description>&lt;p&gt;Certainly the most worrisome aspect of this issue is these users&#039; susceptibility to phishing. If you can&#039;t decipher a URL -- at least up to the slash after the domain name -- then you&#039;re at serious risk, because you never know if the site you&#039;re looking at is legitimate or not.&lt;/p&gt;

&lt;p&gt;I spend about 95% of my browsing time in Firefox and the rest in Safari, but I think this might be a strong argument for web novices to use either Chrome or IE8, since their designs highlight the domain name in the address bar. Sure, if you&#039;ve learned to completely ignore the address bar then it won&#039;t be much help, but it&#039;s better than nothing.&lt;/p&gt;

&lt;p&gt;On the other hand, Firefox (and maybe the other browsers too) does a nice job of emphasizing the certificate owner when you go to an SSL page. But that&#039;s a narrow slice of the web, and if you&#039;re likely to fall for a phishing attack, you probably won&#039;t notice that anyway -- and the scammers might as well not even use SSL, bypassing this feature altogether.&lt;/p&gt;

&lt;p&gt;Here&#039;s a possible solution: browsers could have a &quot;WHOIS&quot; (though I wouldn&#039;t call it that) bar just below the address bar, and do a whois lookup on every site you visit, SSL or not, with the name of the domain owner highlighted.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Certainly the most worrisome aspect of this issue is these users&#8217; susceptibility to phishing. If you can&#8217;t decipher a URL &#8212; at least up to the slash after the domain name &#8212; then you&#8217;re at serious risk, because you never know if the site you&#8217;re looking at is legitimate or not.</p>

<p>I spend about 95% of my browsing time in Firefox and the rest in Safari, but I think this might be a strong argument for web novices to use either Chrome or IE8, since their designs highlight the domain name in the address bar. Sure, if you&#8217;ve learned to completely ignore the address bar then it won&#8217;t be much help, but it&#8217;s better than nothing.</p>

<p>On the other hand, Firefox (and maybe the other browsers too) does a nice job of emphasizing the certificate owner when you go to an SSL page. But that&#8217;s a narrow slice of the web, and if you&#8217;re likely to fall for a phishing attack, you probably won&#8217;t notice that anyway &#8212; and the scammers might as well not even use SSL, bypassing this feature altogether.</p>

<p>Here&#8217;s a possible solution: browsers could have a &#8220;WHOIS&#8221; (though I wouldn&#8217;t call it that) bar just below the address bar, and do a whois lookup on every site you visit, SSL or not, with the name of the domain owner highlighted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bofe</title>
		<link>http://rc3.org/2010/03/02/url-literacy/comment-page-1/#comment-8146</link>
		<dc:creator>bofe</dc:creator>
		<pubDate>Tue, 02 Mar 2010 16:43:19 +0000</pubDate>
		<guid isPermaLink="false">http://rc3.org/?p=10831#comment-8146</guid>
		<description>&lt;p&gt;Rafe,&lt;/p&gt;

&lt;p&gt;Dan Grover has also written a good piece on this subject.&lt;/p&gt;

&lt;p&gt;http://dangrover.com/?action=view&amp;url=toward-a-grand-unified-theory-of-n00bs&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Rafe,</p>

<p>Dan Grover has also written a good piece on this subject.</p>

<p><a href="http://dangrover.com/?action=view&#038;url=toward-a-grand-unified-theory-of-n00bs" rel="nofollow">http://dangrover.com/?action=view&#038;url=toward-a-grand-unified-theory-of-n00bs</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

