<?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>Pluginology</title>
	<atom:link href="http://pluginology.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://pluginology.com</link>
	<description>The Art and Science of Plugins</description>
	<lastBuildDate>Sun, 04 Mar 2012 22:39:40 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="http://superfeedr.com/hubbub"/>		<item>
		<title>Comments Revenge</title>
		<link>http://pluginology.com/519/comments-revenge/</link>
		<comments>http://pluginology.com/519/comments-revenge/#comments</comments>
		<pubDate>Tue, 21 Feb 2012 01:19:06 +0000</pubDate>
		<dc:creator>Wally Day</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://pluginology.com/?p=519</guid>
		<description><![CDATA[I&#8217;ll get straight to the point. You hate always having to monitor your WordPress comments queue, and trying to determine which spammer&#8217;s comment gets the axe today and which one you might let slide by because there&#8217;s the possibility of &#8220;some&#8221; SEO benefit from the comment. (Whew). So do I. And, I decided to do [...]]]></description>
		<wfw:commentRss>http://pluginology.com/519/comments-revenge/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Social Sidekick</title>
		<link>http://pluginology.com/6/social-sidekick/</link>
		<comments>http://pluginology.com/6/social-sidekick/#comments</comments>
		<pubDate>Thu, 15 Dec 2011 08:21:11 +0000</pubDate>
		<dc:creator>Wally Day</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[back links]]></category>
		<category><![CDATA[couple of minutes]]></category>
		<category><![CDATA[facebook]]></category>
		<category><![CDATA[focus groups]]></category>
		<category><![CDATA[network buttons]]></category>
		<category><![CDATA[sidekick]]></category>
		<category><![CDATA[that attracts visitors]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[visual element]]></category>
		<category><![CDATA[web pages]]></category>

		<guid isPermaLink="false">http://pluginology.com/?p=6</guid>
		<description><![CDATA[Get social with the Social Sidekick plugin! Panda Update: I&#8217;ll get straight to the point. Things have changed. Google now requires web pages to adhere to certain guidelines to be considered &#8220;worthy&#8221; of its attention. Three important guidelines (I think of these as the &#8220;Panda Trilogy&#8221;). Engaging content. This includes content that attracts visitors to [...]]]></description>
		<wfw:commentRss>http://pluginology.com/6/social-sidekick/feed/</wfw:commentRss>
		<slash:comments>18</slash:comments>
		</item>
	</channel>
</rss>

