<?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 on: Site update &#8211; Comment SPAM&#8230;again!</title>
	<atom:link href="http://www.thicke.org/archives/2004/12/29/site-update-comment-spamagain/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thicke.org/archives/2004/12/29/site-update-comment-spamagain/</link>
	<description>An aggregate of Marc</description>
	<lastBuildDate>Mon, 27 Apr 2009 17:24:24 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Arzel</title>
		<link>http://www.thicke.org/archives/2004/12/29/site-update-comment-spamagain/comment-page-1/#comment-134</link>
		<dc:creator>Arzel</dc:creator>
		<pubDate>Fri, 31 Dec 2004 13:40:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.thicke.org/archives/2004/12/29/site-update-comment-spamagain/#comment-134</guid>
		<description>The spammers hit me continously since last night until this afternoon. I gave up deleting their comments. I was forced to reconfigure AuthImage and dump comments until the right code is entered. 

By the way, I&#039;ve found the hack to generate a new authorization code when clicking the back button upon entering a wrong code. My only problem now is how to keep the message in the comment field.</description>
		<content:encoded><![CDATA[<p>The spammers hit me continously since last night until this afternoon. I gave up deleting their comments. I was forced to reconfigure AuthImage and dump comments until the right code is entered. </p>
<p>By the way, I&#8217;ve found the hack to generate a new authorization code when clicking the back button upon entering a wrong code. My only problem now is how to keep the message in the comment field.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arzel</title>
		<link>http://www.thicke.org/archives/2004/12/29/site-update-comment-spamagain/comment-page-1/#comment-133</link>
		<dc:creator>Arzel</dc:creator>
		<pubDate>Thu, 30 Dec 2004 19:24:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.thicke.org/archives/2004/12/29/site-update-comment-spamagain/#comment-133</guid>
		<description>I was also expecting that. Everything did shown up except for the comment and the new code.</description>
		<content:encoded><![CDATA[<p>I was also expecting that. Everything did shown up except for the comment and the new code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: thicke</title>
		<link>http://www.thicke.org/archives/2004/12/29/site-update-comment-spamagain/comment-page-1/#comment-132</link>
		<dc:creator>thicke</dc:creator>
		<pubDate>Thu, 30 Dec 2004 19:12:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.thicke.org/archives/2004/12/29/site-update-comment-spamagain/#comment-132</guid>
		<description>I thought I read about a fix to this where you can have it post a page saying the code was invalid, which then reloads the comment page with all the data (name,email, URI and comments) intact.  I&#039;ll have to look around for that.</description>
		<content:encoded><![CDATA[<p>I thought I read about a fix to this where you can have it post a page saying the code was invalid, which then reloads the comment page with all the data (name,email, URI and comments) intact.  I&#8217;ll have to look around for that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arzel</title>
		<link>http://www.thicke.org/archives/2004/12/29/site-update-comment-spamagain/comment-page-1/#comment-130</link>
		<dc:creator>Arzel</dc:creator>
		<pubDate>Thu, 30 Dec 2004 15:57:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.thicke.org/archives/2004/12/29/site-update-comment-spamagain/#comment-130</guid>
		<description>Marc, I entered the wrong code and almost didn&#039;t get my previous comment posted even if I re-entered the correct code. I had to reload the page to get another code and re-enter my comments. It doesn&#039;t seems to be a good idea for a non-WP users. Maybe you should consider passing the comments to moderation mode when a wrong code is entered.</description>
		<content:encoded><![CDATA[<p>Marc, I entered the wrong code and almost didn&#8217;t get my previous comment posted even if I re-entered the correct code. I had to reload the page to get another code and re-enter my comments. It doesn&#8217;t seems to be a good idea for a non-WP users. Maybe you should consider passing the comments to moderation mode when a wrong code is entered.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: thicke</title>
		<link>http://www.thicke.org/archives/2004/12/29/site-update-comment-spamagain/comment-page-1/#comment-125</link>
		<dc:creator>thicke</dc:creator>
		<pubDate>Wed, 29 Dec 2004 17:02:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.thicke.org/archives/2004/12/29/site-update-comment-spamagain/#comment-125</guid>
		<description>Cool.  I got the colors for Authimage changed to fit the website!</description>
		<content:encoded><![CDATA[<p>Cool.  I got the colors for Authimage changed to fit the website!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
