<?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:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Spam score: Spammers 1, Akisment 68</title>
	<atom:link href="http://robcottingham.ca/2006/01/spam-score-spammers-1-akisment-68/feed/" rel="self" type="application/rss+xml" />
	<link>http://robcottingham.ca/2006/01/spam-score-spammers-1-akisment-68/</link>
	<description>Social media enabler &#124; Noise to Signal cartoonist &#124; Speaker and comic</description>
	<lastBuildDate>Thu, 04 Mar 2010 04:33:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rob</title>
		<link>http://robcottingham.ca/2006/01/spam-score-spammers-1-akisment-68/comment-page-1/#comment-1851</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Sun, 29 Jan 2006 03:11:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.robcottingham.ca/20060128/spam-score-spammers-1-akisment-68/#comment-1851</guid>
		<description>Here&#039;s a dilemma that applies broadly to security concerns, not just to spam: how do you balance the transparency required for trust with the need to conceal information from potential abusers?

Akismet&#039;s FAQ asks, &quot;What stops the system from being gamed?&quot; and answers,

&lt;blockquote&gt;Well without giving too much of the secret sauce away, we can safely say that it would be pretty difficult to poison Akismet. We use dozens of factors to determine the spamminess of a submission, and we also have an identity attached to everyone using and contributing to the system, which allows us to do some interesting things with weighting and clustering activity.&lt;/blockquote&gt;

The proof will have to be in the pudding (to swap food metaphors); you won&#039;t get to read the recipe or assess the ingredients for yourself. That said, you get to see comments before they&#039;re deleted, and have the chance to flag them as &quot;not spam&quot;. The worst that can happen, at least in theory, is that some spam will slip through -- in which case human comment moderation comes into play.

Then again, with millions of dollars on the line, spammers are highly motivated to find a way around it (or, as you mention, to poison the well).

Either way, I wish Akismet could find a way to deliver a powerful electrical shock to whoever&#039;s sending me the &quot;Children love Floam!&quot; e-mail. Spam is one area where some dark part of me wants the phrase &quot;killer app&quot; to take on a lethally literal meaning.</description>
		<content:encoded><![CDATA[<p>Here&#8217;s a dilemma that applies broadly to security concerns, not just to spam: how do you balance the transparency required for trust with the need to conceal information from potential abusers?</p>
<p>Akismet&#8217;s FAQ asks, &#8220;What stops the system from being gamed?&#8221; and answers,</p>
<blockquote><p>Well without giving too much of the secret sauce away, we can safely say that it would be pretty difficult to poison Akismet. We use dozens of factors to determine the spamminess of a submission, and we also have an identity attached to everyone using and contributing to the system, which allows us to do some interesting things with weighting and clustering activity.</p></blockquote>
<p>The proof will have to be in the pudding (to swap food metaphors); you won&#8217;t get to read the recipe or assess the ingredients for yourself. That said, you get to see comments before they&#8217;re deleted, and have the chance to flag them as &#8220;not spam&#8221;. The worst that can happen, at least in theory, is that some spam will slip through &#8212; in which case human comment moderation comes into play.</p>
<p>Then again, with millions of dollars on the line, spammers are highly motivated to find a way around it (or, as you mention, to poison the well).</p>
<p>Either way, I wish Akismet could find a way to deliver a powerful electrical shock to whoever&#8217;s sending me the &#8220;Children love Floam!&#8221; e-mail. Spam is one area where some dark part of me wants the phrase &#8220;killer app&#8221; to take on a lethally literal meaning.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian King</title>
		<link>http://robcottingham.ca/2006/01/spam-score-spammers-1-akisment-68/comment-page-1/#comment-1850</link>
		<dc:creator>Ian King</dc:creator>
		<pubDate>Sun, 29 Jan 2006 01:31:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.robcottingham.ca/20060128/spam-score-spammers-1-akisment-68/#comment-1850</guid>
		<description>This is actually one of those applications where relying on the so-called wisdom of crowds is not a bad idea. The question &quot;is this comment spam?&quot; is one where there&#039;s a widely-agreed upon and widely-understood answer, and one where legitimate users are almost certainly going to answer honestly as they do not appreciate spam. 

This contrasts with some naive ideas, like asking people who they think will be elected in riding X, a question that most respondents will not be able to answer in an informed way, and where the likelihood that the question will not be answered honestly is rather high. (People will give bogus answers for malicious reasons, either to play up their party or muck with the system.) Yes, I thought that the election mashup was a poorly-conceived idea; the energy expended therein would be better spent helping Election Prediction Project, whose track record is far better thanks to the use of human-powered bullshit detection, to improve its appearace and add some features.

The big quesiton is whether Akismet itself has some defences against spam houses flooding its database with false negatives or other sorts of attacks and abuse. If they haven&#039;t sufficiently prepared, and the spammers do poison their data (and past history suggests that they will), then Akismet will become far less useful. If it&#039;s not bogus data, it&#039;s DoS attacks; if it&#039;s not that, it&#039;s something else. &lt;a href=&quot;http://diveintomark.org/archives/2003/11/15/more-spam&quot; rel=&quot;nofollow&quot;&gt;Mark Pilgrim&#039;s warnings from 2003&lt;/a&gt; are still apropos.</description>
		<content:encoded><![CDATA[<p>This is actually one of those applications where relying on the so-called wisdom of crowds is not a bad idea. The question &#8220;is this comment spam?&#8221; is one where there&#8217;s a widely-agreed upon and widely-understood answer, and one where legitimate users are almost certainly going to answer honestly as they do not appreciate spam. </p>
<p>This contrasts with some naive ideas, like asking people who they think will be elected in riding X, a question that most respondents will not be able to answer in an informed way, and where the likelihood that the question will not be answered honestly is rather high. (People will give bogus answers for malicious reasons, either to play up their party or muck with the system.) Yes, I thought that the election mashup was a poorly-conceived idea; the energy expended therein would be better spent helping Election Prediction Project, whose track record is far better thanks to the use of human-powered bullshit detection, to improve its appearace and add some features.</p>
<p>The big quesiton is whether Akismet itself has some defences against spam houses flooding its database with false negatives or other sorts of attacks and abuse. If they haven&#8217;t sufficiently prepared, and the spammers do poison their data (and past history suggests that they will), then Akismet will become far less useful. If it&#8217;s not bogus data, it&#8217;s DoS attacks; if it&#8217;s not that, it&#8217;s something else. <a href="http://diveintomark.org/archives/2003/11/15/more-spam" rel="nofollow">Mark Pilgrim&#8217;s warnings from 2003</a> are still apropos.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
