<?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: Fixing the Woot Watcher Firefox Add-on</title>
	<atom:link href="http://www.phantom42.com/blog/index.php" rel="self" type="application/rss+xml" />
	<link>http://www.phantom42.com/blog/index.php/2010/05/fixing-the-woot-watcher-firefox-add-on/</link>
	<description>inane ramblings</description>
	<lastBuildDate>Tue, 27 Dec 2011 17:08:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Fix Your Woot Watcher &#124; Robot.Floss</title>
		<link>http://www.phantom42.com/blog/index.php/2010/05/fixing-the-woot-watcher-firefox-add-on/comment-page-1/#comment-951</link>
		<dc:creator>Fix Your Woot Watcher &#124; Robot.Floss</dc:creator>
		<pubDate>Thu, 24 Jun 2010 17:49:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.phantom42.com/blog/?p=394#comment-951</guid>
		<description>[...] can find directions on how to fix the Woot Watchter yourself or you can download it here at [...]</description>
		<content:encoded><![CDATA[<p>[...] can find directions on how to fix the Woot Watchter yourself or you can download it here at [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Coleman</title>
		<link>http://www.phantom42.com/blog/index.php/2010/05/fixing-the-woot-watcher-firefox-add-on/comment-page-1/#comment-769</link>
		<dc:creator>Joe Coleman</dc:creator>
		<pubDate>Tue, 01 Jun 2010 13:54:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.phantom42.com/blog/?p=394#comment-769</guid>
		<description>Rodney, you&#039;re correct - but that how useful that data is depends on the Woot writers. Some days, it&#039;s more specific than others. That said, I&#039;ve updated the post to offer another option you can pull data from that is sometimes a little more useful. 

I&#039;ll have to boot up the other Windows machines I have and check the extension locations. Thanks for the heads up.</description>
		<content:encoded><![CDATA[<p>Rodney, you&#8217;re correct &#8211; but that how useful that data is depends on the Woot writers. Some days, it&#8217;s more specific than others. That said, I&#8217;ve updated the post to offer another option you can pull data from that is sometimes a little more useful. </p>
<p>I&#8217;ll have to boot up the other Windows machines I have and check the extension locations. Thanks for the heads up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rodney Atkins</title>
		<link>http://www.phantom42.com/blog/index.php/2010/05/fixing-the-woot-watcher-firefox-add-on/comment-page-1/#comment-756</link>
		<dc:creator>Rodney Atkins</dc:creator>
		<pubDate>Mon, 31 May 2010 18:23:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.phantom42.com/blog/?p=394#comment-756</guid>
		<description>That partially fixes it, but it provides only the product name. For example, today&#039;s product is a laptop, but Woot Watcher says: &quot;MSI X600-096US,&quot; which doesn&#039;t really provide too much information.

Also, the path for &quot;PC users&quot; above should be &quot;Windows 7 PC users.&quot; The majority of PC users are still using XP.</description>
		<content:encoded><![CDATA[<p>That partially fixes it, but it provides only the product name. For example, today&#8217;s product is a laptop, but Woot Watcher says: &#8220;MSI X600-096US,&#8221; which doesn&#8217;t really provide too much information.</p>
<p>Also, the path for &#8220;PC users&#8221; above should be &#8220;Windows 7 PC users.&#8221; The majority of PC users are still using XP.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

