<?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: Blogging with Style	</title>
	<atom:link href="https://nerdvittles.com/blogging-with-style/feed/" rel="self" type="application/rss+xml" />
	<link>https://nerdvittles.com/blogging-with-style/</link>
	<description>Ward Mundy&#039;s Technobabblelog</description>
	<lastBuildDate>Thu, 03 Feb 2005 14:47:35 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Hank		</title>
		<link>https://nerdvittles.com/blogging-with-style/comment-page-1/#comment-47</link>

		<dc:creator><![CDATA[Hank]]></dc:creator>
		<pubDate>Thu, 03 Feb 2005 14:47:35 +0000</pubDate>
		<guid isPermaLink="false">http://nerdvittles.com/?p=18#comment-47</guid>

					<description><![CDATA[As far as I can tell from reading (as opposed to testing), Hashcash doesn&#039;t do anything to block trackback spam. As I understand the trackback protocol the only way to block it (if it&#039;s accepted at all) is by moderation or automated filtering on the source or content, by blacklist for example. Hashcash works by sticking a magic number in the comment form and checking it (by MD5 hash code generated in a Javascript function) when the form is submitted; adding an extra hurdle that comment spammers would have to jump in order to successfully litter a Hashcash protected site. There is no form required for sending a trackback ping, so Hashcash isn&#039;t invoked. &lt;i&gt;[WM: More great news. I guess I&#039;ll just sit back and wait for the firestorm ... and then turn it off. Thx.]&lt;/i&gt;]]></description>
			<content:encoded><![CDATA[<p>As far as I can tell from reading (as opposed to testing), Hashcash doesn&#8217;t do anything to block trackback spam. As I understand the trackback protocol the only way to block it (if it&#8217;s accepted at all) is by moderation or automated filtering on the source or content, by blacklist for example. Hashcash works by sticking a magic number in the comment form and checking it (by MD5 hash code generated in a Javascript function) when the form is submitted; adding an extra hurdle that comment spammers would have to jump in order to successfully litter a Hashcash protected site. There is no form required for sending a trackback ping, so Hashcash isn&#8217;t invoked. <i>[WM: More great news. I guess I&#8217;ll just sit back and wait for the firestorm &#8230; and then turn it off. Thx.]</i></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Hank		</title>
		<link>https://nerdvittles.com/blogging-with-style/comment-page-1/#comment-44</link>

		<dc:creator><![CDATA[Hank]]></dc:creator>
		<pubDate>Thu, 03 Feb 2005 13:13:47 +0000</pubDate>
		<guid isPermaLink="false">http://nerdvittles.com/?p=18#comment-44</guid>

					<description><![CDATA[I see that your entries have trackback URIs but don&#039;t see any trackbacks. What are you using to block trackback spam?
[WM: Hashcash seems to do the trick. There&#039;s a link to the download in my article.]]]></description>
			<content:encoded><![CDATA[<p>I see that your entries have trackback URIs but don&#8217;t see any trackbacks. What are you using to block trackback spam?<br />
[WM: Hashcash seems to do the trick. There&#8217;s a link to the download in my article.]</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
