<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Noel Schutt &#187; technology</title>
	<atom:link href="http://schutt.org/blog/category/technology/feed/" rel="self" type="application/rss+xml" />
	<link>http://schutt.org/blog</link>
	<description></description>
	<lastBuildDate>Fri, 03 Feb 2012 15:07:49 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>The Capacitor Plague strikes again</title>
		<link>http://schutt.org/blog/2011/10/the-capacitor-plague-strikes-again/</link>
		<comments>http://schutt.org/blog/2011/10/the-capacitor-plague-strikes-again/#comments</comments>
		<pubDate>Fri, 28 Oct 2011 13:46:07 +0000</pubDate>
		<dc:creator>Noel</dc:creator>
				<category><![CDATA[computers]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[capacitor blight]]></category>
		<category><![CDATA[capacitor plague]]></category>
		<category><![CDATA[electronics repair]]></category>

		<guid isPermaLink="false">http://schutt.org/blog/?p=1556</guid>
		<description><![CDATA[I just had another run-in with the dreaded capacitor plague. The first case was the power supply in a G5 iMac. This time it was a Samsung SyncMaster 22.5 inch Display. After two years of working well, the monitor started acting up by flickering and taking a while to turn on. Eventually, it completely stopped [...]]]></description>
			<content:encoded><![CDATA[<p>I just had another run-in with the dreaded <a href="http://en.wikipedia.org/wiki/Capacitor_plague">capacitor plague</a>. The first case was the power supply in a G5 iMac. This time it was a Samsung SyncMaster 22.5 inch Display. After two years of working well, the monitor started acting up by flickering and taking a while to turn on. Eventually, it completely stopped working. After spending a few minutes ruling out bad cables, I suspected the problem was bad capacitors.</p>
<p>The capacitor plague was a common problem in recent years, causing failures in all brands of electronics, including brands usually known for higher quality components. The problem occurs in electrolytic capacitors (the little ‘cans’ on circuit boards) produced using the wrong electrolyte. The improper electrolyte degrades over time, causing the capacitors to bulge and even rupture. As far as I can tell, this blight was caused because circuit manufacturers trying to save a few cents per board. They did this by buying capacitors that were made using a stolen electrolyte formula that was missing key ingredients. Some of the faulty capacitors were counterfeits of name brands, others were less reputable off-brands. Many of the problems didn&#8217;t become apparent until after the one-year warranty period. Some manufacturers slightly extended their warranty for this problem. But the extended warranties were not long enough to catch all the faulty components, as seen in the iMac G5. Even with the short warranties, the counterfeit components cost manufacturers $100 million to repair as of the middle of 2006, when the problem was still ongoing.</p>
<p>Since I&#8217;ve seen the capacitor plague before, it was immediately obvious after dissecting the monitor. The capacitors on the power supply board were clearly bulging, though they weren&#8217;t leaking goop as the caps in the iMac were. After spending some time browsing the <a href="http://www.digikey.com/">Digi-Key</a> catalog to choose parts, I ordered the highest quality available replacement components. Capacitors are much more expensive when you are ordering one or two of each instead of 2500 or 10000 of each, but the total was still only $3.77.</p>
<div id="attachment_1558" class="wp-caption aligncenter" style="width: 410px"><a href="http://schutt.org/blog/wp-content/uploads/2011/10/power_supply-400.jpg"><img src="http://schutt.org/blog/wp-content/uploads/2011/10/power_supply-400.jpg" alt="" title="Samsung 225BW power supply" width="400" height="273" class="size-full wp-image-1558" /></a><p class="wp-caption-text">Samsung 225BW power supply</p></div>
<p>Once I had the components, it only took a few minutes with a desoldering iron to remove the blighted capacitors, then a few more minutes to install the new caps. I was pleasantly surprised at the quality of the power supply&#8217;s layout and printing, which made the repair unusually easy. After the easiest repair I&#8217;ve done in a long time, I popped the monitor back together, and it worked better than I remembered it working. I guess the plagued capacitors were causing problems before I realised they were.</p>
<div id="attachment_1560" class="wp-caption aligncenter" style="width: 410px"><a href="http://schutt.org/blog/wp-content/uploads/2011/10/bulging_capacitors.jpg"><img src="http://schutt.org/blog/wp-content/uploads/2011/10/bulging_capacitors.jpg" alt="" title="Bulging capacitors" width="400" height="206" class="size-full wp-image-1560" /></a><p class="wp-caption-text">Bulging capacitors. Note the pressure-relief scores beginning to open.</p></div>
<p>After removing the bad capacitors, I measured their values. They all have a similar error, averaging 62% less than their nominal value.</p>
<hr />
<h3 id="monitor-details">Monitor Details</h3>
<p>Samsung SyncMaster 22.5 inch LCD <br />Model: 225BW <br />Type Number: DP22WS</p>
<h3 id="sources">Sources</h3>
<ul>
<li><a href="http://spectrum.ieee.org/computing/hardware/leaking-capacitors-muck-up-motherboards/0">Leaking Capacitors Muck up Motherboards</a></li>
<li><a href="http://spectrum.ieee.org/computing/hardware/bogus/0">Bogus!</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://schutt.org/blog/2011/10/the-capacitor-plague-strikes-again/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>More on the definition of &#8216;hack&#8217;</title>
		<link>http://schutt.org/blog/2011/07/more-on-the-definition-of-hack/</link>
		<comments>http://schutt.org/blog/2011/07/more-on-the-definition-of-hack/#comments</comments>
		<pubDate>Thu, 28 Jul 2011 15:39:46 +0000</pubDate>
		<dc:creator>Noel</dc:creator>
				<category><![CDATA[technology]]></category>
		<category><![CDATA[crack]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[hack reporter]]></category>
		<category><![CDATA[journalism]]></category>
		<category><![CDATA[phreak]]></category>

		<guid isPermaLink="false">http://schutt.org/blog/?p=1346</guid>
		<description><![CDATA[To go along with yesterday&#8217;s post, here are two stories that were shared with me: First, Ben Popper of Betabeat realized that he had been using the term hack incorrectly, and mostly fixed his usage in his article &#8220;Hacked to Death: A Brief History of Tech’s Most Two-Sided Term&#8221;. Second, David Goldman of CNN demonstrates [...]]]></description>
			<content:encoded><![CDATA[<p>To go along with <a href="/blog/2011/07/the-news-of-the-world-scandal/" title="The News of the World Scandal">yesterday&#8217;s post</a>, here are two stories that were shared with me:</p>
<p>First, Ben Popper of Betabeat realized that he had been using the term <em>hack</em> incorrectly, and mostly fixed his usage in his article &ldquo;<a href="http://www.betabeat.com/2011/07/26/hacked-to-death-how-journalists-are-ruining-the-word-hacker/">Hacked to Death: A Brief History of Tech’s Most Two-Sided Term</a>&rdquo;.</p>
<p>Second, David Goldman of CNN demonstrates the common incorrect usage in his article &ldquo;<a href="http://money.cnn.com/2011/07/27/technology/organized_cybercrime/index.htm">The cyber Mafia has already hacked you</a>&rdquo;. Showing their ignorance, CNN even includes the incorrect usage in the headline.</p>
<p>As I have been telling people for years, the proper usage of the word <em>hack</em> is an important shibboleth separating those with competence in computers and technology from posers. Remember, <em>hacking</em> is not the same as <em>cracking</em>, <em>phreaking</em>, or any of their script kiddie relatives.</p>
]]></content:encoded>
			<wfw:commentRss>http://schutt.org/blog/2011/07/more-on-the-definition-of-hack/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The News of the World Scandal</title>
		<link>http://schutt.org/blog/2011/07/the-news-of-the-world-scandal/</link>
		<comments>http://schutt.org/blog/2011/07/the-news-of-the-world-scandal/#comments</comments>
		<pubDate>Wed, 27 Jul 2011 14:46:25 +0000</pubDate>
		<dc:creator>Noel</dc:creator>
				<category><![CDATA[technology]]></category>
		<category><![CDATA[crack]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[hack reporter]]></category>
		<category><![CDATA[journalism]]></category>
		<category><![CDATA[phreak]]></category>

		<guid isPermaLink="false">http://schutt.org/blog/?p=1322</guid>
		<description><![CDATA[I can&#8217;t take it anymore! Nearly every time I have listened to or read the news few weeks I have heard the term &#8220;hacking&#8221; abused, usually in reference to News of the World. The constant references to &#8220;The News of the World phone hacking scandal&#8220; show that these reporters are hopelessly clueless in technical matters, [...]]]></description>
			<content:encoded><![CDATA[<p>I can&#8217;t take it anymore! Nearly every time I have listened to or read the news few weeks I have heard the term &ldquo;hacking&rdquo; abused, usually in reference to <em>News of the World</em>. The constant references to &ldquo;The <em>News of the World</em> phone hacking scandal&ldquo; show that these reporters are hopelessly clueless in technical matters, and should not report on anything technology related until they do some research. According to the reports, all that was involved was voicemail PIN guessing and a little social engineering, neither of which fit under the definition of <a href="http://www.catb.org/jargon/html/H/hacker.html">hacking</a>. Guessing default passwords is easy, and in no way can be considered <em>hacking</em>, though it can be considered <a href="http://www.catb.org/jargon/html/C/cracking.html"><em>cracking</em></a>. Since the PINs were guessed to gain access to voicemail, it could fit under a loose definition of <a href="http://www.catb.org/jargon/html/P/phreaking.html"><em>phreaking</em></a>, but not hacking. The other part of gaining access to the PINs involved talking to the phone companies. This is called <a href="http://www.catb.org/jargon/html/S/social-engineering.html"><em>social engineering</em></a>, though apparently those involved called it &ldquo;blagging&rdquo;. This is also not a form of hacking.</p>
<p>Since no hacking was involved in the scandal, it would be more proper to call it &ldquo;The <em>News of the World</em> voicemail scandal&rdquo;, or &ldquo;The latest News Corp scandal&rdquo;. Since this hasn&#8217;t been common, it is clear that these are hack reporters and their stories should be treated with greater than usual skepticism. This is unfortunate, since these reports came from usually reliable sources such as <em><a href="http://www.nytimes.com/2011/07/07/world/europe/07phone.html">The New York Times</a></em>, <a href="http://www.propublica.org/article/our-readers-guide-to-the-phone-hacking-scandal">ProPublica</a>, <a href="http://www.mcclatchydc.com/2011/07/14/117619/news-corps-widening-scandal.html">McClatchy</a>, and <a href="http://www.npr.org/2011/07/18/138484220/a-look-at-the-relationship-between-britains-police-and-press">NPR</a>. Heck, on NPR there have even been a number of non-Murdoch related stories where <em>hack</em> has been <a href="http://www.npr.org/2011/07/25/138683226/how-to-protect-yourself-from-hacking">abused</a>. Remember, misusing the word <em>hack</em> is <a href="/writing/tech/choose/#hack">one of the signs</a> that someone doesn&#8217;t have basic competence in technology. This is also a good time to mention Steven Levy&#8217;s book <em>Hackers</em>. If you don&#8217;t understand the definition of <em>hack</em>, you should read this book.</p>
<hr />
<p>BibTex:</p>
<pre>@book{levy,
  title={Hackers: heroes of the computer revolution},
  author={Steven Levy},
  isbn={9780385312103},
  url={http://www.stevenlevy.com/index.php/books/hackers},
  year={1984},
}</pre>
<p>While I&#8217;m at it, here&#8217;s an <a href="https://freedom-to-tinker.com/blog/harlanyu/retiring-fedthread">article</a> posted today that uses <em>hacking</em> correctly.</p>
]]></content:encoded>
			<wfw:commentRss>http://schutt.org/blog/2011/07/the-news-of-the-world-scandal/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Not opening windows</title>
		<link>http://schutt.org/blog/2011/01/not-opening-windows/</link>
		<comments>http://schutt.org/blog/2011/01/not-opening-windows/#comments</comments>
		<pubDate>Fri, 21 Jan 2011 17:16:05 +0000</pubDate>
		<dc:creator>Noel</dc:creator>
				<category><![CDATA[design]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[new window]]></category>
		<category><![CDATA[target]]></category>
		<category><![CDATA[TinyMCE]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://schutt.org/blog/?p=1124</guid>
		<description><![CDATA[For some mysterious reason, some people make external links from their website open in a new window. This is a user unfriendly feature that good websites stopped using over ten years ago. But some clueless people still think forcing a new window is a good idea. I believe they think it is a way to [...]]]></description>
			<content:encoded><![CDATA[<p> For some mysterious reason, some people make external links from their website open in a new window. This is a user unfriendly feature that good websites stopped using over ten years ago. But some clueless people still think forcing a new window is a good idea. I believe they think it is a way to keep people on their site to generate more sales or display more ads. What it does is annoy users. They may see the site for longer, but will have a less favorable opinion of it. If someone  has a reason for opening a new window they&#8217;ll do it themselves, without a webmaster forcing it on them. It isn&#8217;t necessary to use a new window to keep people on your site, this is 2011, and everyone has figured out how to use the browser&#8217;s &lsquo;back&rsquo; feature. Since web design moved past the frames stage a decade ago, it isn&#8217;t necessary to continue using the <code>target</code> tag. Remember, using <code>target="_blank"</code> or a JavaScript equivalent is a bad idea.</p>
<p>Unfortunately, I just realized that one of the sites that I host was using lots of <code>target="_blank"</code> tags. This particular site uses a CMS with TinyMCE for editing. TinyMCE allows the user to choose the target for a link, and a large portion of the links had this turned on. The choice of target wasn&#8217;t consistant, so it was probably a case of the user randomly choosing an option. So I decided to remove the option.</p>
<p>I searched the source, and found where the target was being added. I also looked online for on official setting to remove this feature, but didn&#8217;t find one. I don&#8217;t know the canonical way to do this, but deleting a few lines from two files works well.</p>
<p>From <code>tinymce/jscripts/tiny_mce/themes/advanced/link.htm</code> delete the lines:</p>
<pre>&lt;tr&gt;
	&lt;td&gt;&lt;label id="targetlistlabel" for="targetlist"&gt;{#advanced_dlg.link_target}&lt;/label&gt;&lt;/td&gt;
	&lt;td&gt;&lt;select id="target_list" name="target_list"&gt;&lt;/select&gt;&lt;/td&gt;
&lt;/tr&gt;</pre>
<p>From <code>tinymce/jscripts/tiny_mce/themes/advanced/js/link.js</code> delete the lines that include <code>target_list</code>.</p>
<p>The only problem I see is that these changes will have to be repeated every time you update the software. I suppose I could write a <code>sed</code> script to do this, but the TinyMCE code could change, and there has to be a cleaner official way get rid of the target.</p>
<hr />
<p>Update: I ended up searching the entire database to remove all the target tags. The site with the target problem uses MySQL, so I just ran this command through MySQL:</p>
<pre>UPDATE table_name SET column_name = REPLACE(column_name, 'target=\"_blank\"', '')</pre>
<hr />
<p>Caveat: I will occasionally use <code>target="_top"</code> on some links because there are still some sites that try to surround another site with ads.</p>
<p>Note: If you think you need to open a new window, I have a <a href="http://cheat.schuttdesign.net/hint/opening-links-new-window/">hint for that</a> on my <a href="http://cheat.schuttdesign.net/">Cheat Sheet</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://schutt.org/blog/2011/01/not-opening-windows/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Insanity and trying again</title>
		<link>http://schutt.org/blog/2010/12/insanity-and-trying-again/</link>
		<comments>http://schutt.org/blog/2010/12/insanity-and-trying-again/#comments</comments>
		<pubDate>Tue, 28 Dec 2010 12:10:59 +0000</pubDate>
		<dc:creator>Noel</dc:creator>
				<category><![CDATA[philosophy]]></category>
		<category><![CDATA[science]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[Brown]]></category>
		<category><![CDATA[Einstein]]></category>
		<category><![CDATA[insanity]]></category>
		<category><![CDATA[Mustek]]></category>
		<category><![CDATA[Sony]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://schutt.org/blog/?p=1070</guid>
		<description><![CDATA[I&#8217;ve seen this quote a number of times recently: The definition of insanity is doing the same thing over and over and expecting different results. It is typically misattributed to Albert Einstein, but is probably from Rita Mae Brown. The quote is often true, but is misleading. Sometimes you do the same thing several times [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve seen this quote a number of times recently:</p>
<blockquote><p>
The definition of insanity is doing the same thing over and over and expecting different results.
</p></blockquote>
<p>It is typically misattributed to <a href="http://en.wikiquote.org/wiki/Einstein">Albert Einstein</a>, but is probably from <a href="http://en.wikiquote.org/wiki/Rita_Mae_Brown">Rita Mae Brown</a>.</p>
<p>The quote is often true, but is misleading. Sometimes you do the same thing several times and get different results. For example, in the lab I did my thesis research in, there are two experiments that I have run multiple times, producing different results from different runs. According to the available measurements the experiments were identical. That doesn&#8217;t mean I couldn&#8217;t detect differences with better resources (eg doi:<a href="http://dx.doi.org/10.1038/nnano.2006.95">10.1038/nnano.2006.95</a>), but as far as I can tell, they were the same.</p>
<p>Another common case is using computers running Windows. Trying the same thing several times when it didn&#8217;t work the first may be insanity, but it is necessary. One problem last week is a good example: I helped get a Sony VAIO laptop working with a Mustek A3 scanner. The software would seem to install properly, but the scanner would give an error message. The scanner worked first try on a ThinkPad running Windows 7, but wouldn&#8217;t run on the VAIO with XP, even after updating and cleaning the system. Before returning the computer and scanner, I decided to do one more thing: I plugged the scanner into a different USB port and ran Mustek installer then the Microsoft Scanner and Camera Wizard. It worked. I plugged it into the third USB port and repeated the process. It worked. I tried the first port again. The scanner still worked. Repeating the installation steps had fixed the problem. It can be convincingly argued that using an OS where performing the same steps multiple times leads to different results is insanity, but that isn&#8217;t the point of the quote.</p>
<p>Not that there aren&#8217;t many times when Brown&#8217;s quote is accurate. If you want examples of trying the same thing over and over expecting different results, when everyone knows what will happen, just read the newspaper.</p>
]]></content:encoded>
			<wfw:commentRss>http://schutt.org/blog/2010/12/insanity-and-trying-again/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Webcams</title>
		<link>http://schutt.org/blog/2010/12/webcams/</link>
		<comments>http://schutt.org/blog/2010/12/webcams/#comments</comments>
		<pubDate>Wed, 08 Dec 2010 23:02:34 +0000</pubDate>
		<dc:creator>Noel</dc:creator>
				<category><![CDATA[technology]]></category>
		<category><![CDATA[1984]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[webcam]]></category>

		<guid isPermaLink="false">http://schutt.org/blog/?p=1034</guid>
		<description><![CDATA[I&#8217;m still freaked out by webcams. It is nice having a camera on my computer for the occasional video-chat, but I&#8217;m still reminded of 1984. Since most notebook computers and many desktops now include webcams, it&#8217;s nice to see that some now have lens caps built in. Although, this still leaves the problem of the [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m still freaked out by webcams. It is nice having a camera on my computer for the occasional video-chat, but I&#8217;m still reminded of <em>1984</em>.</p>
<p>Since most notebook computers and many desktops now include webcams, it&#8217;s nice to see that <a href="http://lenovoblogs.com/lenovofiles/2010/07/22/watch-that-webcam/">some</a> now have <a href="http://lenovoblogs.com/designmatters/?p=4795<br />
">lens caps built in</a>. Although, this still leaves the problem of the internal microphone; and we still need to get everyone to stop adding gratuitous cameras to computers and cell phones. When I want to use a camera, I&#8217;ll use a good one, not an integrated toy that wastes space and battery life in another tool. If I could replace my MacBook with one without iSight, I would.</p>
<hr />
<p>I may as well mention that the webcam can be used for security; for example <a href="http://cheat.schuttdesign.net/hint/wakelog-pictures/">Wakelog Pictures</a>. But something like this should only be used if you have a good reason. In general, the proliferation of integrated cameras is a bad idea, but at least we haven&#8217;t reached the CCTV big brother problem that England has a reputation for.</p>
]]></content:encoded>
			<wfw:commentRss>http://schutt.org/blog/2010/12/webcams/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The missing search engine</title>
		<link>http://schutt.org/blog/2010/11/missing-search-engine/</link>
		<comments>http://schutt.org/blog/2010/11/missing-search-engine/#comments</comments>
		<pubDate>Fri, 26 Nov 2010 22:53:19 +0000</pubDate>
		<dc:creator>Noel</dc:creator>
				<category><![CDATA[technology]]></category>
		<category><![CDATA[advertising]]></category>
		<category><![CDATA[AJAX]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[paywall]]></category>
		<category><![CDATA[search]]></category>
		<category><![CDATA[search engine]]></category>
		<category><![CDATA[spam]]></category>

		<guid isPermaLink="false">http://schutt.org/blog/?p=427</guid>
		<description><![CDATA[The internet needs an editor, but that is against the spirit of the &#8216;net.1 The next best thing would be a search engine that is better at eliminating spam sites from search results. Google is wonderful, but the number of spam sites seems to be overwhelming them. There are many sites that scrape contents2 from [...]]]></description>
			<content:encoded><![CDATA[<p>The internet needs an editor, but that is against the spirit of the &#8216;net.<sup><a href="#mse1">1</a></sup> The next best thing would be a search engine that is better at eliminating spam sites from search results. Google is wonderful, but the number of spam sites seems to be overwhelming them. There are many sites that scrape contents<sup><a href="#mse2">2</a></sup> from other sites or simply mirror mailing lists. Over the past few months these sites have often filled the first page of my Google searches. This wastes time. The recent increase can probably be attributed to decreases in the cost of web hosting, the fact that modern programming languages and libraries make site scraping easy, and the proliferation newly underemployed techies of the past two years.<sup><a href="#mse3">3</a></sup></p>
<p>A related category of sites that is often showing up high in search results are sites abusing AJAX to create a popup window that covers the content, but since the content is on the page, it still shows up in searches. Unfortunately some of these sites rank high in Google searches. But I&#8217;d never consider actually paying to login. If I really want the info, I could just look at the source, or (locally) hack the code to disable the popup, but why waste time with that? It would be better to have these sites not show up in the first few pages of results.</p>
<p>It will be impressive if someone manages to come up with an algorithm that solves this problem without hiding legitimate sites. One problem to solve is to find the earliest post that all the others link to, and make it rank well in the search results. This can be hard, because sites often plagiarize without citing sources. Getting around this would require a fair amount of processing power. For all the link sites and scraper sites that just copy the text, checking a simple hash of the first paragraph would be a good start toward eliminating the cruft. This is a bit too simple to work well and or for long. Simply pulling part of a paragraph would defeat a hash. Another way to defeat it would be to replace a few words with synonyms, which is easy to automate. One way to deal with this is to use a thesaurus based index instead of indexing individual words. This would have the advantage of lowering the number of words that must be indexed. Based on some search results, I suspect Google already does this.</p>
<p>This would be an interesting problem to work on, but it isn&#8217;t one that I&#8217;ll ever get around to. I hope this post will help encourage someone else to work on it. So please, write a search engine that can show the earliest sources and has the option to not include ad sites! Until someone does, I&#8217;m using the partial solution of adding some of the worst offenders to the exclude list of a Google custom search.</p>
<hr />
<p>Notes:</p>
<ol>
<li><a name="mse1"></a>The founding principle of the World Wide Web: anyone from from anywhere can post anything useful to be freely shared. Paywalls and sites that exist to show ads are clearly against this principle.</li>
<li><a name="mse2"></a>Scraping content means writing a program to automatically copy parts of someone else&#8217;s site. It has legitimate uses, but is often abused.</li>
<li><a name="mse3"></a>I originally wrote this post in September 2009. It is still hard for educated people to find a decent job.</li>
</ol>
<hr />
<p>Postscript (2010-11-30): The NYTimes posted a <a href="http://www.nytimes.com/2010/11/28/business/28borker.html?_r=1&#038;pagewanted=all">story</a> that is a good example of why search engines that are more spam-proof are needed.</p>
]]></content:encoded>
			<wfw:commentRss>http://schutt.org/blog/2010/11/missing-search-engine/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ovens and self-driving cars</title>
		<link>http://schutt.org/blog/2010/11/ovens-and-self-driving-cars/</link>
		<comments>http://schutt.org/blog/2010/11/ovens-and-self-driving-cars/#comments</comments>
		<pubDate>Wed, 24 Nov 2010 05:09:49 +0000</pubDate>
		<dc:creator>Noel</dc:creator>
				<category><![CDATA[cars]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[ai]]></category>
		<category><![CDATA[driverless]]></category>
		<category><![CDATA[embedded processor]]></category>
		<category><![CDATA[oven]]></category>
		<category><![CDATA[safety]]></category>
		<category><![CDATA[self-driving]]></category>
		<category><![CDATA[software]]></category>

		<guid isPermaLink="false">http://schutt.org/blog/?p=1027</guid>
		<description><![CDATA[Yesterday I was talking with another grad student, and the topic of self-driving cars came up. He thinks they are a good idea, I don&#8217;t. In high school and college, I would have thought they are an interesting project that I would like to work on. I still think the research is interesting, but I [...]]]></description>
			<content:encoded><![CDATA[<p>Yesterday I was talking with another grad student, and the topic of self-driving cars came up. He thinks they are a good idea, I don&#8217;t. In high school and college, I would have thought they are an interesting project that I would like to work on. I still think the research is interesting, but I now think driverless cars are a bad idea. I&#8217;ll even go further and say that fly-by-wire cars are a bad idea. I simply don&#8217;t trust the quality of the hardware and especially the software that will likely be used in self-driving cars. Whenever I work on a car, I am amazed by some poor design choice; then there is the problem that the onboard computers in cars aren&#8217;t exactly known for reliable software. Even if the manufacturer&#8217;s firmware is well written, car owners will modify it, likely compromising safety to gain a little performance. But intentional modifications aren&#8217;t needed to cause problems. I&#8217;ve worked with electronics and software enough to think <a href="http://www.frontiernet.net/~wmooney1/Fixed_files/murphy.pdf">Edward Murphy was an optimist</a>. Even the higher quality sensors used in cars die all the time. A driverless car would require enough redundancy that the inevitable failures wouldn&#8217;t allow the car to injure a pedestrian. But given the way the market works, it is much more realistic to expect Wal-Mart quality than NASA quality. But cheap junk isn&#8217;t an acceptable option for something as dangerous as a car.</p>
<p>Today I found another example why my mistrust of embedded systems is justified. We have a gas convection oven with a fairly sophisticated electronic control. It has a processor that does a good job of keeping the temperature stable and that can do useful things like automatically turn the oven off when the cooking time is complete. After using the oven today, I hit the off button. The gas turned off, then the oven locked up. It was receiving power, and the LED panel was lit, but it was completely unresponsive. I had to use the circuit breaker to reboot the oven. I hope it is designed so that a failure causes the gas valve to close, but it may not.</p>
<p>The crashing oven is relevant to self-driving cars because they are both ubiquitous and potentially deadly systems controlled by embedded processors. If I can&#8217;t trust an oven, how much less should I trust a car?</p>
<p>Unfortunately, I would be completely unsurprised if we are eventually forced into self-driving cars. Besides the common unjustified technological optimism, there are the problems of well-meaning safety campaigners and of lawyers. Because the ideal driverless car is perfectly safe, as more cars begin to incorporate more bits of automated driving (<em>eg</em> automatic distance controls), it is likely that there will be campaigns and lawsuits to mandate these features. These will likely add up until we are forced into driverless cars.</p>
<p>While self-driving cars are an interesting research project with some beneficial uses, my experience in maintaining cars and in computer engineering makes me think they are a bad idea for general use. A better solution is to expand the rail system to lower the use of interstate highways, and to design cities where driving is less needed.</p>
]]></content:encoded>
			<wfw:commentRss>http://schutt.org/blog/2010/11/ovens-and-self-driving-cars/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Customizing Mac OS X PDF Services</title>
		<link>http://schutt.org/blog/2009/08/osx-pdf-services/</link>
		<comments>http://schutt.org/blog/2009/08/osx-pdf-services/#comments</comments>
		<pubDate>Tue, 18 Aug 2009 22:46:06 +0000</pubDate>
		<dc:creator>Noel</dc:creator>
				<category><![CDATA[technology]]></category>
		<category><![CDATA[computers]]></category>
		<category><![CDATA[Mac]]></category>
		<category><![CDATA[OS X]]></category>

		<guid isPermaLink="false">http://schutt.org/blog/?p=360</guid>
		<description><![CDATA[One useful feature of OS X is the built in PDF handling. It is always easy to export a file as a PDF, and to do some basic editing of PDF files. A post on Mac OS X Hints today got me looking at some customizations. The hint is that creating an alias in the [...]]]></description>
			<content:encoded><![CDATA[<p>One useful feature of OS X is the built in PDF handling. It is always easy to export a file as a PDF, and to do some basic editing of PDF files. A <a href="http://www.macosxhints.com/article.php?story=20090817002247614" title="Add a Save to PDF directory to your Print options">post</a> on Mac OS X Hints today got me looking at some customizations. The hint is that creating an alias in the proper directory adds an item to the PDF menu. This can be done through Finder, or through the command line:</p>
<p><code>cd ~/Libary/PDF\ Services<br />
ln -s ~/path/ "descriptive_alias"</code></p>
<p>You may have to create the directory <code>~/Libary/PDF Services</code>. Some people recommend using the directory <code>/Libary/PDF Services</code>, but this is bad style unless you <em>really</em> want the change to be universal. Even if you are the only user on the computer, it is safer to use the <code>Library</code> folder under your user account.</p>
<p>When looking in the <code>/Libary/PDF Services</code> directory, I noticed that the contents are just Automator workflows. This means it is easy for non-programmers to customize the behavior. One option that I somehow hadn&#8217;t noticed before today is <code>Save PDF to Web Receipts Folder.pdfworkflow</code>. With online billing this is incredibly useful. I typically use the &#8220;Save PDF as&#8221; option, saving the PDF in this year&#8217;s receipts directory, with the date as a prefix. This makes receipts for monthly bills easy to find. I looked at &#8220;Save PDF to Web Receipts Folder&#8221; to see how easy it would be to alter to my preferred style. Instead of being an Automator workflow, this is actually a Python script and a few property lists. Great! Python is my favorite language. I copied the files to <code>~/Libary/PDF Services</code> and edited them. The Python script is in a file named <code>tool</code>. This script is well written, making it easy to modify. Here are the basic changes:</p>
<ul>
<li>Because I want to use timestamps, I added <code>import time</code> after the other import statements.</li>
<li>I changed the <code>destDirectory</code> to my preferred directory. The script already creates the destination directory if it doesn&#8217;t exist, so altering the directory by date is easy, I added <code>destDirectory = os.path.join(destDirectory, time.strftime("%Y"))</code> to automatically append the subdirectory for the year.</li>
<li>The file uses the title of the webpage as the filename. To add the date as a prefix, add the line <code>title = "%s-%s" % (time.strftime( "%Y%m%d"), title)</code> to the build path section. You can easily customize the date format.</li>
<li>I  prefer lowercase filenames, so I added <code>filename = filename.lower()</code> to the <code>safeFilename</code> function.</li>
<li>If a file with this name already exists, the script appends a number to the name. I prefer different character than the default, so I changed it.</li>
</ul>
<p>The final step was to I update the property list files so that the PDF menu shows the name I gave the command, instead of the original name from Apple.</p>
<p>I now have an even quicker way to save my receipts. Because the program is automatically generating the filenames using my preferences, I don&#8217;t have to change the name every time, and can avoid some typos and incorrect dates.</p>
]]></content:encoded>
			<wfw:commentRss>http://schutt.org/blog/2009/08/osx-pdf-services/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Voicemail</title>
		<link>http://schutt.org/blog/2009/07/voicemail/</link>
		<comments>http://schutt.org/blog/2009/07/voicemail/#comments</comments>
		<pubDate>Thu, 30 Jul 2009 00:33:56 +0000</pubDate>
		<dc:creator>Noel</dc:creator>
				<category><![CDATA[design]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[phone]]></category>
		<category><![CDATA[telephone]]></category>
		<category><![CDATA[voicemail]]></category>

		<guid isPermaLink="false">http://schutt.org/blog/?p=287</guid>
		<description><![CDATA[One of the many modern &#8216;conveniences&#8217; that actually take more time than they save is voicemail. Answering machines and voicemail are occasionally useful, but more often than not, someone just leaves a rambling message with details they end up repeating when you call them back. Fortunately, Caller ID has mostly eliminated the need for voicemail: [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://schutt.org/blog/wp-content/uploads/2009/07/20090705-162111-edited-88x150.jpg" alt="Motofone F3" title="Motofone F3" width="88" height="150" class="alignright size-thumbnail wp-image-289" /></p>
<p>One of the many modern &lsquo;conveniences&rsquo; that actually take more time than they save is voicemail. Answering machines and voicemail are occasionally useful, but more often than not, someone just leaves a rambling message with details they end up repeating when you call them back. Fortunately, Caller ID has mostly eliminated the need for voicemail: if you need to leave a message, I probably need to return your call. Since visual voicemail hasn&#8217;t yet been universally adopted&#8212;and some people still leave voicemails&#8212;I sometimes have to check my voicemail account. This has allowed phone companies to waste tons of customer time by forcing us to listen to long instructions describing voicemail. There are no obvious ways to avoid this wasted time. Thanks to <a href="http://pogue.blogs.nytimes.com/2009/07/29/how-to-bypass-stupid-voicemail-instructions/" title="How to Bypass Stupid Voicemail Instructions">David Pogue</a>, I learned the non-obvious way, &ldquo;1 * #&rdquo;. If you are leaving a voice mail, one of those will probably get you out of listening to the pointless 30 second message.</p>
<p>You can look in the voicemail help for your carrier to find the correct code for your own voicemail.</p>
<ul>
<li>T-Mobile: <a href="http://support.t-mobile.com/knowbase/root/public/tm30112.pdf" title="T-Mobile VoiceMail shortucts">VoiceMail Shortcuts</a></li>
<li>Verizon: <a href="http://wirelesssupport.verizon.com/how_to_use/basic_voice_mail.html" title="Verizon voicemail instructions">Voice Mail Instructions</a>; different instructions depending on your region</li>
<li>AT&amp;T: <a href="http://www.wireless.att.com/learn/en_US/pdf/3961_Lucent_VM_QuickGuide.pdf" title="voicemail quickguide">Voicemail Quickguide</a></li>
<li>Sprint: gave up on search; different instructions by phone</li>
</ul>
<p>Source: <a href="http://www.livedigitally.com/2007/03/16/skipping-voicemail-greetings-one-star-pound/" title="LIVEdigitally: skip voicemail greeting">LIVEdigitally</a> through <a href="http://pogue.blogs.nytimes.com/2009/07/29/how-to-bypass-stupid-voicemail-instructions/" title="How to Bypass Stupid Voicemail Instructions">Pogue&#8217;s Posts</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://schutt.org/blog/2009/07/voicemail/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

