<?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 for One Ear Productions, Inc.</title>
	<atom:link href="http://oneearproductions.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://oneearproductions.com</link>
	<description></description>
	<lastBuildDate>Fri, 20 May 2011 13:51:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>Comment on WordPress and .htaccess by Anonymous</title>
		<link>http://oneearproductions.com/blog/2010/08/wordpress-and-htaccess/#comment-371</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Fri, 20 May 2011 13:51:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oneearproductions.com/?p=437#comment-371</guid>
		<description>Good job! </description>
		<content:encoded><![CDATA[<p>Good job!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SEO, Part III: What Comes First? by SEO, Part IV: More on Links &#8211; One Ear Productions</title>
		<link>http://oneearproductions.com/blog/2010/06/seo-part-iii-what-comes-first/#comment-22</link>
		<dc:creator>SEO, Part IV: More on Links &#8211; One Ear Productions</dc:creator>
		<pubDate>Mon, 28 Jun 2010 17:29:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oneearproductions.com/?p=278#comment-22</guid>
		<description>[...] than one of thousands, so as to get the largest possible share of link juice. Also, remember that Google considers content closer to the top of the page to be more important; thus, it&#8217;s good if your link shows up close to the beginning of the HTML file (which is not [...] </description>
		<content:encoded><![CDATA[<p>[...] than one of thousands, so as to get the largest possible share of link juice. Also, remember that Google considers content closer to the top of the page to be more important; thus, it&#8217;s good if your link shows up close to the beginning of the HTML file (which is not [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SEO, Part II: Links by SEO, Part IV: More on Links &#8211; One Ear Productions</title>
		<link>http://oneearproductions.com/blog/2010/06/seo-part-ii-links/#comment-18</link>
		<dc:creator>SEO, Part IV: More on Links &#8211; One Ear Productions</dc:creator>
		<pubDate>Mon, 28 Jun 2010 17:28:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oneearproductions.com/?p=269#comment-18</guid>
		<description>[...] SEO Part II: Links, we discussed the importance of incoming links from high-ranking sites in the same area as yours. [...] </description>
		<content:encoded><![CDATA[<p>[...] SEO Part II: Links, we discussed the importance of incoming links from high-ranking sites in the same area as yours. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SEO, Part I: White Hat vs Black Hat by SEO, Part III: What Comes First? &#8211; One Ear Productions</title>
		<link>http://oneearproductions.com/blog/2010/06/seo-part-i-white-hat-vs-black-hat/#comment-15</link>
		<dc:creator>SEO, Part III: What Comes First? &#8211; One Ear Productions</dc:creator>
		<pubDate>Fri, 25 Jun 2010 14:42:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oneearproductions.com/?p=252#comment-15</guid>
		<description>[...] when I said that your site generally shouldn&#8217;t look different to users and search engines? One exception is when you&#8217;re displaying the same content, but they read that content [...] </description>
		<content:encoded><![CDATA[<p>[...] when I said that your site generally shouldn&#8217;t look different to users and search engines? One exception is when you&#8217;re displaying the same content, but they read that content [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on HTML5, Part III: Local Storage by HTML5, Part II: What Features Does My Browser Support? &#8211; One Ear Productions</title>
		<link>http://oneearproductions.com/blog/2010/06/html5-part-iii-local-storage/#comment-14</link>
		<dc:creator>HTML5, Part II: What Features Does My Browser Support? &#8211; One Ear Productions</dc:creator>
		<pubDate>Wed, 23 Jun 2010 18:29:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oneearproductions.com/?p=235#comment-14</guid>
		<description>[...] Now that we&#8217;ve seen how to figure out what features the user&#8217;s browser supports, let&#8217;s get back to things that most browsers do. Next up, something every modern browser (even IE 8) supports: local storage!  [...] </description>
		<content:encoded><![CDATA[<p>[...] Now that we&#8217;ve seen how to figure out what features the user&#8217;s browser supports, let&#8217;s get back to things that most browsers do. Next up, something every modern browser (even IE <img src='http://oneearproductions.com/wp-includes/images/smilies/icon_cool.gif' alt='8)' class='wp-smiley' /> supports: local storage!  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Building a Blog, Part I: Setting up WordPress by Web 2.0, Part II: Wik, Wik, Wiki! &#8211; One Ear Productions</title>
		<link>http://oneearproductions.com/blog/2010/06/building-a-blog-part-i-setting-up-wordpress/#comment-5</link>
		<dc:creator>Web 2.0, Part II: Wik, Wik, Wiki! &#8211; One Ear Productions</dc:creator>
		<pubDate>Tue, 15 Jun 2010 16:40:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oneearproductions.com/?p=68#comment-5</guid>
		<description>[...] to download the software, then unpack it and set up a MySQL database as you did in the building a blog articles. Like Wordpress, the wiki software has a web-based configuration utility; at the time of [...] </description>
		<content:encoded><![CDATA[<p>[...] to download the software, then unpack it and set up a MySQL database as you did in the building a blog articles. Like WordPress, the wiki software has a web-based configuration utility; at the time of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on History of One Ear&#8230; by Tweets that mention History of One Ear… – One Ear Productions -- Topsy.com</title>
		<link>http://oneearproductions.com/blog/2010/05/history-of-one-ear/#comment-4</link>
		<dc:creator>Tweets that mention History of One Ear… – One Ear Productions -- Topsy.com</dc:creator>
		<pubDate>Sat, 08 May 2010 07:12:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oneearproductions.com/?p=48#comment-4</guid>
		<description>[...] This post was mentioned on Twitter by One Ear Productions. One Ear Productions said: http://blog.oneearproductions.com/?p=48 http://bit.ly/cIMMFs [...] </description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by One Ear Productions. One Ear Productions said: <a href="http://blog.oneearproductions.com/?p=48" rel="nofollow">http://blog.oneearproductions.com/?p=48</a> <a href="http://bit.ly/cIMMFs" rel="nofollow">http://bit.ly/cIMMFs</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Beginning… by Tweets that mention The Beginning… – One Ear Productions -- Topsy.com</title>
		<link>http://oneearproductions.com/blog/2010/05/the-beginning%e2%80%a6/#comment-3</link>
		<dc:creator>Tweets that mention The Beginning… – One Ear Productions -- Topsy.com</dc:creator>
		<pubDate>Fri, 07 May 2010 22:36:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oneearproductions.com/?p=24#comment-3</guid>
		<description>[...] This post was mentioned on Twitter by One Ear Productions. One Ear Productions said: http://blog.oneearproductions.com/?p=24 http://bit.ly/aWivQl [...] </description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by One Ear Productions. One Ear Productions said: <a href="http://blog.oneearproductions.com/?p=24" rel="nofollow">http://blog.oneearproductions.com/?p=24</a> <a href="http://bit.ly/aWivQl" rel="nofollow">http://bit.ly/aWivQl</a> [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

