<?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"
	>
<channel>
	<title>Comments on: New comment spam technique</title>
	<atom:link href="http://blog.xcski.com/2006/08/04/new-comment-spam-technique/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.xcski.com/2006/08/04/new-comment-spam-technique</link>
	<description>Everything I used to bore people on newsgroups and mailing lists with, now in one inconvenient place.</description>
	<pubDate>Sat, 30 Aug 2008 11:12:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Information Echo &#187; Have I mentioned&#8230;</title>
		<link>http://blog.xcski.com/2006/08/04/new-comment-spam-technique#comment-11705</link>
		<dc:creator>Information Echo &#187; Have I mentioned&#8230;</dc:creator>
		<pubDate>Sat, 30 Sep 2006 03:42:20 +0000</pubDate>
		<guid isPermaLink="false">http://xcski.com/blogs/pt/2006/08/04/new-comment-spam-technique#comment-11705</guid>
		<description>[...] Seems that I&#8217;ve become the subject of a new blog spam technique recently, similar to (or likely the same) as what Paul was experiencing a few weeks back. [...]</description>
		<content:encoded><![CDATA[<p>[...] Seems that I&#8217;ve become the subject of a new blog spam technique recently, similar to (or likely the same) as what Paul was experiencing a few weeks back. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gordon</title>
		<link>http://blog.xcski.com/2006/08/04/new-comment-spam-technique#comment-9692</link>
		<dc:creator>Gordon</dc:creator>
		<pubDate>Mon, 07 Aug 2006 14:53:06 +0000</pubDate>
		<guid isPermaLink="false">http://xcski.com/blogs/pt/2006/08/04/new-comment-spam-technique#comment-9692</guid>
		<description>I was actually thinking there might be a way to prevent your content from being wrapped up in someone else's site.  Once upon a time I saw a snippet for Javascript that would forcibly close a window if it was wrapped up by someone else.</description>
		<content:encoded><![CDATA[<p>I was actually thinking there might be a way to prevent your content from being wrapped up in someone else&#8217;s site.  Once upon a time I saw a snippet for Javascript that would forcibly close a window if it was wrapped up by someone else.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barry Price</title>
		<link>http://blog.xcski.com/2006/08/04/new-comment-spam-technique#comment-9574</link>
		<dc:creator>Barry Price</dc:creator>
		<pubDate>Sat, 05 Aug 2006 06:01:01 +0000</pubDate>
		<guid isPermaLink="false">http://xcski.com/blogs/pt/2006/08/04/new-comment-spam-technique#comment-9574</guid>
		<description>I had exactly the same thing happen to me recently - only the one copy though.  I told Spam Karma 2 that it was a spammy trackback, I wonder how it will cope.</description>
		<content:encoded><![CDATA[<p>I had exactly the same thing happen to me recently - only the one copy though.  I told Spam Karma 2 that it was a spammy trackback, I wonder how it will cope.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Tomblin</title>
		<link>http://blog.xcski.com/2006/08/04/new-comment-spam-technique#comment-9565</link>
		<dc:creator>Paul Tomblin</dc:creator>
		<pubDate>Fri, 04 Aug 2006 23:06:44 +0000</pubDate>
		<guid isPermaLink="false">http://xcski.com/blogs/pt/2006/08/04/new-comment-spam-technique#comment-9565</guid>
		<description>Gordon, regarding your "creative Apache rules": it appears that each of the 4 trackback spam attempts came from different IPs, but each time, 7 seconds before the spam, there was a read of that page from 205.218.67.174.  I've used iptables to block access from that particular IP.  We'll see if it helps.</description>
		<content:encoded><![CDATA[<p>Gordon, regarding your &#8220;creative Apache rules&#8221;: it appears that each of the 4 trackback spam attempts came from different IPs, but each time, 7 seconds before the spam, there was a read of that page from 205.218.67.174.  I&#8217;ve used iptables to block access from that particular IP.  We&#8217;ll see if it helps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gordon</title>
		<link>http://blog.xcski.com/2006/08/04/new-comment-spam-technique#comment-9564</link>
		<dc:creator>Gordon</dc:creator>
		<pubDate>Fri, 04 Aug 2006 22:45:47 +0000</pubDate>
		<guid isPermaLink="false">http://xcski.com/blogs/pt/2006/08/04/new-comment-spam-technique#comment-9564</guid>
		<description>Oh, and I'm sure some creative Apache rules could sort this out. :)</description>
		<content:encoded><![CDATA[<p>Oh, and I&#8217;m sure some creative Apache rules could sort this out. <img src='http://blog.xcski.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gordon</title>
		<link>http://blog.xcski.com/2006/08/04/new-comment-spam-technique#comment-9563</link>
		<dc:creator>Gordon</dc:creator>
		<pubDate>Fri, 04 Aug 2006 22:45:13 +0000</pubDate>
		<guid isPermaLink="false">http://xcski.com/blogs/pt/2006/08/04/new-comment-spam-technique#comment-9563</guid>
		<description>I wonder if you can get them for copyright violation on something like this?</description>
		<content:encoded><![CDATA[<p>I wonder if you can get them for copyright violation on something like this?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
