<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.7" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Wiki testing</title>
	<link>http://spamhuntress.com/2005/09/18/wiki-testing/</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Mon, 08 Sep 2008 07:38:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.7</generator>

	<item>
		<title>by: Spam Huntress  &#187; Blog Archive   &#187; Invisible wiki spammer hits again</title>
		<link>http://spamhuntress.com/2005/09/18/wiki-testing/#comment-1549</link>
		<pubDate>Sun, 09 Oct 2005 10:55:18 +0000</pubDate>
		<guid>http://spamhuntress.com/2005/09/18/wiki-testing/#comment-1549</guid>
					<description>[...] isible wiki spammer hits again 	 			 					My &#8220;other&#8221; wiki got a visit from our invisible wiki spammer. He uses tags that make his spam invisible on Mediawiki. And then he adds [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] isible wiki spammer hits again 	 			 					My &#8220;other&#8221; wiki got a visit from our invisible wiki spammer. He uses tags that make his spam invisible on Mediawiki. And then he adds [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: RichardP</title>
		<link>http://spamhuntress.com/2005/09/18/wiki-testing/#comment-1341</link>
		<pubDate>Tue, 27 Sep 2005 07:30:26 +0000</pubDate>
		<guid>http://spamhuntress.com/2005/09/18/wiki-testing/#comment-1341</guid>
					<description>He is experimentation is getting more sophisticated.  Now he is posting his spam from one proxy out of a large pool of proxies and then immediately replacing the spam (using another, different, proxy) with a bunch of blank lines.  I assume his goal is to thwart wiki's that support rollback and get his links into the revision history without detection.  The strategy seems rather dubious, since many wikis now mark old revisions with noindex, nofollow).</description>
		<content:encoded><![CDATA[<p>He is experimentation is getting more sophisticated.  Now he is posting his spam from one proxy out of a large pool of proxies and then immediately replacing the spam (using another, different, proxy) with a bunch of blank lines.  I assume his goal is to thwart wiki&#8217;s that support rollback and get his links into the revision history without detection.  The strategy seems rather dubious, since many wikis now mark old revisions with noindex, nofollow).
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Spam Huntress  &#187; Blog Archive   &#187; Nuke on sight</title>
		<link>http://spamhuntress.com/2005/09/18/wiki-testing/#comment-1305</link>
		<pubDate>Mon, 19 Sep 2005 17:57:59 +0000</pubDate>
		<guid>http://spamhuntress.com/2005/09/18/wiki-testing/#comment-1305</guid>
					<description>[...] ted in guestbook spamming before. 	Dyndns subdomains hosted on: 69.93.145.180 	I found the wiki testing bot active on the same wiki, before the 69.31.82.66 bot showed up. 69.31.131.178 	T [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] ted in guestbook spamming before. 	Dyndns subdomains hosted on: 69.93.145.180 	I found the wiki testing bot active on the same wiki, before the 69.31.82.66 bot showed up. 69.31.131.178 	T [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Joe</title>
		<link>http://spamhuntress.com/2005/09/18/wiki-testing/#comment-1286</link>
		<pubDate>Sun, 18 Sep 2005 22:09:44 +0000</pubDate>
		<guid>http://spamhuntress.com/2005/09/18/wiki-testing/#comment-1286</guid>
					<description>I have seen non "testing" versions of this recently.  Halz has emailed a MediaWiki developer about this.  We have known about this problem for a good while but didn't want to publisize it.   It appears it is becomming more popular now anyway.</description>
		<content:encoded><![CDATA[<p>I have seen non &#8220;testing&#8221; versions of this recently.  Halz has emailed a MediaWiki developer about this.  We have known about this problem for a good while but didn&#8217;t want to publisize it.   It appears it is becomming more popular now anyway.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
