<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: First its Digg spam now its spreaded to WORDPRESS!</title>
	<atom:link href="http://gamerzworld.wordpress.com/2005/12/30/first-its-digg-spam-now-its-spreaded-to-wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://gamerzworld.wordpress.com/2005/12/30/first-its-digg-spam-now-its-spreaded-to-wordpress/</link>
	<description>Gaming at its best (and worst).</description>
	<lastBuildDate>Wed, 03 May 2006 15:15:42 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Fantastico &#187; Blog Archive &#187; Massive Wordpress.com Spam</title>
		<link>http://gamerzworld.wordpress.com/2005/12/30/first-its-digg-spam-now-its-spreaded-to-wordpress/#comment-35</link>
		<dc:creator>Fantastico &#187; Blog Archive &#187; Massive Wordpress.com Spam</dc:creator>
		<pubDate>Fri, 30 Dec 2005 05:44:25 +0000</pubDate>
		<guid isPermaLink="false">http://gamerzworld.wordpress.com/2005/12/30/first-its-digg-spam-now-its-spreaded-to-wordpress/#comment-35</guid>
		<description>[...] You can see a screenshot here. Wordpress.com really needs to work to make sure it does not become the BlogSpot (or as some say, SplogSpot) of the new web. It&#8217;s an amazing service and hopefully will stay that way when they figure out this problem. [...]</description>
		<content:encoded><![CDATA[<p>[...] You can see a screenshot here. WordPress.com really needs to work to make sure it does not become the BlogSpot (or as some say, SplogSpot) of the new web. It&#8217;s an amazing service and hopefully will stay that way when they figure out this problem. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
