<?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: Smart spam and new comment policy</title>
	<atom:link href="http://labnotes.org/2008/07/06/smart-spam-and-new-comment-policy/feed/" rel="self" type="application/rss+xml" />
	<link>http://labnotes.org/2008/07/06/smart-spam-and-new-comment-policy/</link>
	<description></description>
	<lastBuildDate>Sun, 15 Jan 2012 21:29:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Crosbie Fitch</title>
		<link>http://labnotes.org/2008/07/06/smart-spam-and-new-comment-policy/comment-page-1/#comment-140808</link>
		<dc:creator>Crosbie Fitch</dc:creator>
		<pubDate>Fri, 11 Jul 2008 09:04:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labnotes.org/?p=1085#comment-140808</guid>
		<description>Yes, but we&#039;re right back to where we started.

The original issue was the deficiency in the moderation process of GOOD/BAD(spam/nonsense). If you find this binary process is still workable, and believe that it will always be workable for you, well, excellent.

All I&#039;m saying is that if the borderlines are taking up too much of your precious time (or you starting worrying that you are deleting genuine comments and building up a backlash from newbies who haven&#039;t learnt to avoid sounding like ever more intelligent spammers) there is another process: GOOD(pass)/BAD(delete)/UNSURE(redact).

I&#039;m merely proposing that. It may have fundamental flaws, but it seems like it might be worth a try one day when some moderators have an uncertainty crisis.</description>
		<content:encoded><![CDATA[<p>Yes, but we&#8217;re right back to where we started.</p>
<p>The original issue was the deficiency in the moderation process of GOOD/BAD(spam/nonsense). If you find this binary process is still workable, and believe that it will always be workable for you, well, excellent.</p>
<p>All I&#8217;m saying is that if the borderlines are taking up too much of your precious time (or you starting worrying that you are deleting genuine comments and building up a backlash from newbies who haven&#8217;t learnt to avoid sounding like ever more intelligent spammers) there is another process: GOOD(pass)/BAD(delete)/UNSURE(redact).</p>
<p>I&#8217;m merely proposing that. It may have fundamental flaws, but it seems like it might be worth a try one day when some moderators have an uncertainty crisis.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Assaf</title>
		<link>http://labnotes.org/2008/07/06/smart-spam-and-new-comment-policy/comment-page-1/#comment-140805</link>
		<dc:creator>Assaf</dc:creator>
		<pubDate>Fri, 11 Jul 2008 03:12:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labnotes.org/?p=1085#comment-140805</guid>
		<description>I don&#039;t have time, which is why sometimes I&#039;m going to err and mark comments as spam against my best wishes. Just happened yesterday over email, I didn&#039;t recognize the name and the short message looked like boilerplate spam, so it went to my spam folder.

I moderate by email, and like Karl said so well, its a stream of spam and my time it spent picking out the ham. So if it looks like spam at quick glance, it gets nuked. If it doesn&#039;t, then I stand by my decision to publish it.

Right now I&#039;m taking the time to reflect on these comments and where I draw the line. I&#039;m still not entirely sure where it should be, but once I do, we&#039;re back to regular business. And regular business is me skimming my overflowing inbox and making flash decisions.

And making false positives.

The point is not to allow spammers in, even if their content is half decent. I don&#039;t care. I check my server logs and I know they&#039;re not just pushing content in, they&#039;re checking if it shows up. Allowing it to show up paints me as a target (yay, more spam!) and helps them improve their mechanisms.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t have time, which is why sometimes I&#8217;m going to err and mark comments as spam against my best wishes. Just happened yesterday over email, I didn&#8217;t recognize the name and the short message looked like boilerplate spam, so it went to my spam folder.</p>
<p>I moderate by email, and like Karl said so well, its a stream of spam and my time it spent picking out the ham. So if it looks like spam at quick glance, it gets nuked. If it doesn&#8217;t, then I stand by my decision to publish it.</p>
<p>Right now I&#8217;m taking the time to reflect on these comments and where I draw the line. I&#8217;m still not entirely sure where it should be, but once I do, we&#8217;re back to regular business. And regular business is me skimming my overflowing inbox and making flash decisions.</p>
<p>And making false positives.</p>
<p>The point is not to allow spammers in, even if their content is half decent. I don&#8217;t care. I check my server logs and I know they&#8217;re not just pushing content in, they&#8217;re checking if it shows up. Allowing it to show up paints me as a target (yay, more spam!) and helps them improve their mechanisms.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crosbie Fitch</title>
		<link>http://labnotes.org/2008/07/06/smart-spam-and-new-comment-policy/comment-page-1/#comment-140801</link>
		<dc:creator>Crosbie Fitch</dc:creator>
		<pubDate>Thu, 10 Jul 2008 17:17:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labnotes.org/?p=1085#comment-140801</guid>
		<description>a) Is it clearly interesting, adding to the conversation? Yes: PUBLISH.

b) Is it clearly nonsense or promotion (at best only tangentially related)? Yes: DELETE.

c) In all other cases redact.

In class (a) there will be some comments that promote a product, some that are boilerplate, some that are remixes of other comments from related sites, some that are FAQs submitted by spambots or Elbonians, etc. It doesn&#039;t matter. If it met your criteria for a good comment, it is a good comment.

If, surprisingly, you have enough time to analyse a commenter&#039;s motivation and objective by researching their name, e-mail and links, you can do so, but I see little point in this activity, except perhaps when the comment inspires a response from you.</description>
		<content:encoded><![CDATA[<p>a) Is it clearly interesting, adding to the conversation? Yes: PUBLISH.</p>
<p>b) Is it clearly nonsense or promotion (at best only tangentially related)? Yes: DELETE.</p>
<p>c) In all other cases redact.</p>
<p>In class (a) there will be some comments that promote a product, some that are boilerplate, some that are remixes of other comments from related sites, some that are FAQs submitted by spambots or Elbonians, etc. It doesn&#8217;t matter. If it met your criteria for a good comment, it is a good comment.</p>
<p>If, surprisingly, you have enough time to analyse a commenter&#8217;s motivation and objective by researching their name, e-mail and links, you can do so, but I see little point in this activity, except perhaps when the comment inspires a response from you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Assaf</title>
		<link>http://labnotes.org/2008/07/06/smart-spam-and-new-comment-policy/comment-page-1/#comment-140800</link>
		<dc:creator>Assaf</dc:creator>
		<pubDate>Wed, 09 Jul 2008 23:57:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labnotes.org/?p=1085#comment-140800</guid>
		<description>I can tell when a comment is spam with high certainty. Which is the same as saying &quot;I&#039;ll be wrong on occasion.&quot; So it&#039;s the borderline case I&#039;m worried about, and maybe I judged wrong, or got overzealous clearing too much spam, or didn&#039;t get enough sleep that night.

That&#039;s why I&#039;m advising people to make sure their comments don&#039;t trigger my spam finger. 


The reason I proposed this test is because it&#039;s easy for me to reason about it. It divides comments into two broad categories.

If the comment is valuable by contents alone, then it would be even more valuable if I put it in the body of the post. Not that I plan on doing it, just that most time it&#039;s easy to classify by this test alone.

So far drive-by spam comments fail that test, which brings us to the next category. It now matters who wrote the comment. Again, simple cases, &quot;I love your new theme!&quot; If it comes from a reader, that&#039;s valuable, I want my theme to appeal to readers. What if it comes from a spammer who thinks it actually stinks and hard to navigate, but decided on flattery instead because they just want a place for their ad?

You&#039;re throwing a party at your house and inviting your friends over. How would you feel if someone walked in uninvited and start handing out flyers for online-flowers-cheap, or sell knock-off designer bags, or tell everyone about Elbonia Metals &amp; Glass Inc?

What if they started each sales peach with an insightful quote from the Book of Wisdom, or just told every person to reboot the Windows box regularly?</description>
		<content:encoded><![CDATA[<p>I can tell when a comment is spam with high certainty. Which is the same as saying &#8220;I&#8217;ll be wrong on occasion.&#8221; So it&#8217;s the borderline case I&#8217;m worried about, and maybe I judged wrong, or got overzealous clearing too much spam, or didn&#8217;t get enough sleep that night.</p>
<p>That&#8217;s why I&#8217;m advising people to make sure their comments don&#8217;t trigger my spam finger. </p>
<p>The reason I proposed this test is because it&#8217;s easy for me to reason about it. It divides comments into two broad categories.</p>
<p>If the comment is valuable by contents alone, then it would be even more valuable if I put it in the body of the post. Not that I plan on doing it, just that most time it&#8217;s easy to classify by this test alone.</p>
<p>So far drive-by spam comments fail that test, which brings us to the next category. It now matters who wrote the comment. Again, simple cases, &#8220;I love your new theme!&#8221; If it comes from a reader, that&#8217;s valuable, I want my theme to appeal to readers. What if it comes from a spammer who thinks it actually stinks and hard to navigate, but decided on flattery instead because they just want a place for their ad?</p>
<p>You&#8217;re throwing a party at your house and inviting your friends over. How would you feel if someone walked in uninvited and start handing out flyers for online-flowers-cheap, or sell knock-off designer bags, or tell everyone about Elbonia Metals &#038; Glass Inc?</p>
<p>What if they started each sales peach with an insightful quote from the Book of Wisdom, or just told every person to reboot the Windows box regularly?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crosbie Fitch</title>
		<link>http://labnotes.org/2008/07/06/smart-spam-and-new-comment-policy/comment-page-1/#comment-140797</link>
		<dc:creator>Crosbie Fitch</dc:creator>
		<pubDate>Wed, 09 Jul 2008 10:33:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labnotes.org/?p=1085#comment-140797</guid>
		<description>Let&#039;s not forget you will have a moderation policy that becomes clear to regular readers, e.g. a) publish all comments, b) weed out spam after publication, c) no comment is published without having been scrutinised, d) other.

I am only considering that peculiar case in which you are not sure if a comment is spam.

In the situation you describe you appear to be quite able to recognise the spam nature of these &#039;drive-by&#039; comments. So I&#039;m not sure what analysis you&#039;re expecting from me.

Anyway, I don&#039;t think you make commenters or their comments more authoritative by publishing/not removing coincidentally valid drive-by comments (you may however indicate their comment is indeed valid, apposite, sufficiently interesting, contributes to the discussion, etc.). Readers recognise that commenters&#039; knowledge and intelligence greatly varies, from bearded experts down to newbie code monkeys - and now down to Elbonian undercover SEO operatives.

Does it matter if a comment is a FAQ asked by someone who seeks only vacuous nofollow-free dialogue rather than enlightenment? If you think it&#039;s worth answering, go for it. What can you lose? Do you feel dirty come the day you realise you&#039;ve been talking to an Elizabot/Moron/Elbonian/Replicant? It doesn&#039;t matter. You are the one who is valued, as is what you say - and this isn&#039;t reduced by being seen to talk to imbeciles or spammers - as long as what you say is valuable. You don&#039;t have to go back and delete the conversation once you&#039;ve found out the skin colour of the person you were talking to, their IQ, or their motivation.

Of course, you may be on a mission to engage in counter-SEO measures because you simply hate the thought your blog might give a tadette more prominence to a spammer in Google&#039;s analysis.

What is your purpose in moderating commments? To deny spammers link love? Or to ensure discussion isn&#039;t distracted by advertising or nonsense?</description>
		<content:encoded><![CDATA[<p>Let&#8217;s not forget you will have a moderation policy that becomes clear to regular readers, e.g. a) publish all comments, b) weed out spam after publication, c) no comment is published without having been scrutinised, d) other.</p>
<p>I am only considering that peculiar case in which you are not sure if a comment is spam.</p>
<p>In the situation you describe you appear to be quite able to recognise the spam nature of these &#8216;drive-by&#8217; comments. So I&#8217;m not sure what analysis you&#8217;re expecting from me.</p>
<p>Anyway, I don&#8217;t think you make commenters or their comments more authoritative by publishing/not removing coincidentally valid drive-by comments (you may however indicate their comment is indeed valid, apposite, sufficiently interesting, contributes to the discussion, etc.). Readers recognise that commenters&#8217; knowledge and intelligence greatly varies, from bearded experts down to newbie code monkeys &#8211; and now down to Elbonian undercover SEO operatives.</p>
<p>Does it matter if a comment is a FAQ asked by someone who seeks only vacuous nofollow-free dialogue rather than enlightenment? If you think it&#8217;s worth answering, go for it. What can you lose? Do you feel dirty come the day you realise you&#8217;ve been talking to an Elizabot/Moron/Elbonian/Replicant? It doesn&#8217;t matter. You are the one who is valued, as is what you say &#8211; and this isn&#8217;t reduced by being seen to talk to imbeciles or spammers &#8211; as long as what you say is valuable. You don&#8217;t have to go back and delete the conversation once you&#8217;ve found out the skin colour of the person you were talking to, their IQ, or their motivation.</p>
<p>Of course, you may be on a mission to engage in counter-SEO measures because you simply hate the thought your blog might give a tadette more prominence to a spammer in Google&#8217;s analysis.</p>
<p>What is your purpose in moderating commments? To deny spammers link love? Or to ensure discussion isn&#8217;t distracted by advertising or nonsense?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Assaf</title>
		<link>http://labnotes.org/2008/07/06/smart-spam-and-new-comment-policy/comment-page-1/#comment-140793</link>
		<dc:creator>Assaf</dc:creator>
		<pubDate>Tue, 08 Jul 2008 23:10:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labnotes.org/?p=1085#comment-140793</guid>
		<description>Let&#039;s do something else and see if we can apply a test to it. Because essentially, that&#039;s something I run in my head before deciding whether to junk a comment that&#039;s likely spam.

Let&#039;s assume I can predict what the drive-by comment would say on a given post. Most people read the post but don&#039;t come back to check on comments. If the comment has value, then I can amplify that value tremendously by slapping it to the end of the post. That way, it becomes visible to everyone, and some people will even take it as more authoritative.

So look at the sample comment above, about clearing the cache. That one is a good reflection of most of the drive-by comment I get. It&#039;s not a hypothetical what if, but an actual spam catch. And I already have a couple of cases where, because of multiple drive-bys, I can predict the comment from the post.

So given the benefit of the doubt that it has value, I&#039;m going to amplify that value by adding this piece of text to the next post that I predict will attract a comment like this. Good or bad?</description>
		<content:encoded><![CDATA[<p>Let&#8217;s do something else and see if we can apply a test to it. Because essentially, that&#8217;s something I run in my head before deciding whether to junk a comment that&#8217;s likely spam.</p>
<p>Let&#8217;s assume I can predict what the drive-by comment would say on a given post. Most people read the post but don&#8217;t come back to check on comments. If the comment has value, then I can amplify that value tremendously by slapping it to the end of the post. That way, it becomes visible to everyone, and some people will even take it as more authoritative.</p>
<p>So look at the sample comment above, about clearing the cache. That one is a good reflection of most of the drive-by comment I get. It&#8217;s not a hypothetical what if, but an actual spam catch. And I already have a couple of cases where, because of multiple drive-bys, I can predict the comment from the post.</p>
<p>So given the benefit of the doubt that it has value, I&#8217;m going to amplify that value by adding this piece of text to the next post that I predict will attract a comment like this. Good or bad?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crosbie Fitch</title>
		<link>http://labnotes.org/2008/07/06/smart-spam-and-new-comment-policy/comment-page-1/#comment-140791</link>
		<dc:creator>Crosbie Fitch</dc:creator>
		<pubDate>Tue, 08 Jul 2008 17:41:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labnotes.org/?p=1085#comment-140791</guid>
		<description>If in doubt, don&#039;t nuke it, redact it. If it&#039;s fluff and links to a poker site, well, you will develop your own heuristics to select between nuking and redacting.

For boilerplate comments that through chance are apposite, we need another plug-in, a Google search showing the moderator how likely it is to be boilerplate (used elsewhere). However, boilerplate comments aren&#039;t really a problem. The value you add is how you respond to them. You don&#039;t remove value from your blog by unwittingly publishing boilerplate. If the boilerplate prompts an interesting response from you then that&#039;s great. If however, your response is to criticise the boilerplate for not making sense or to ask its author to provide a little more evidence then the ball&#039;s in their court. The boilerplater is already losing value through their unthinking behaviour - even if no-one sees the misses because they&#039;re deleted, the duplication of the boilerplate comment will eventually surface and indicate the comment is spam and reduce the reputation of anything it&#039;s trying to promote. This still won&#039;t negate the value of any comments in response, nor make readers think less of you for being &#039;caught out&#039; by a boilerplate comment.

Even if we became overrun with Elizabots that submit querying comments to bloggers (without otherwise tipping the blogger off that it is a bot), the bloggers&#039; responses are still valuable (because they&#039;ll only be given in response to apparently good comments). A comment that is good by accident is still a good comment.

Everyone still has to verify comments anyway (before acting upon them). The blogger doesn&#039;t lend their reputation to commenters, they only pass comments that may reflect the views of real people and may be interesting to others. It&#039;s not like you&#039;re publishing a peer reviewed journal in which the academic credentials of each commenter must be ascertained to demonstrate they are true peers.

One thing that&#039;s currently different between intellispammers and Elizabots, and is that unlike the latter, the former do not yet have an energy budget sufficient to engage in any resulting dialogue. Even when they do, or when even &lt;a href=&quot;http://en.wikipedia.org/wiki/Elbonia&quot;&gt;Elbonians&lt;/a&gt; start getting paid pennies for having jejune repartee with bloggers simply to slip in some promotional links or keywords, the blogger still has an energy budget that dictates how many comments are worthy of their consideration or worth replying to.

A far trickier problem is what a human commenter is to do when a blogger specifically rejects their further comments, or even erases their historical comments.

I fancy a far more peer-to-peer+reputation metric based means of blogging - and trackbacks still don&#039;t cut it. Then somewhat like Slashdot, all participants can decide if certain other participants are spammers, religiously/politically unpalatable (subjective), or by default worthy of being considered their peers. Perhaps this is a job for Google? Maybe they&#039;re already working on it?</description>
		<content:encoded><![CDATA[<p>If in doubt, don&#8217;t nuke it, redact it. If it&#8217;s fluff and links to a poker site, well, you will develop your own heuristics to select between nuking and redacting.</p>
<p>For boilerplate comments that through chance are apposite, we need another plug-in, a Google search showing the moderator how likely it is to be boilerplate (used elsewhere). However, boilerplate comments aren&#8217;t really a problem. The value you add is how you respond to them. You don&#8217;t remove value from your blog by unwittingly publishing boilerplate. If the boilerplate prompts an interesting response from you then that&#8217;s great. If however, your response is to criticise the boilerplate for not making sense or to ask its author to provide a little more evidence then the ball&#8217;s in their court. The boilerplater is already losing value through their unthinking behaviour &#8211; even if no-one sees the misses because they&#8217;re deleted, the duplication of the boilerplate comment will eventually surface and indicate the comment is spam and reduce the reputation of anything it&#8217;s trying to promote. This still won&#8217;t negate the value of any comments in response, nor make readers think less of you for being &#8216;caught out&#8217; by a boilerplate comment.</p>
<p>Even if we became overrun with Elizabots that submit querying comments to bloggers (without otherwise tipping the blogger off that it is a bot), the bloggers&#8217; responses are still valuable (because they&#8217;ll only be given in response to apparently good comments). A comment that is good by accident is still a good comment.</p>
<p>Everyone still has to verify comments anyway (before acting upon them). The blogger doesn&#8217;t lend their reputation to commenters, they only pass comments that may reflect the views of real people and may be interesting to others. It&#8217;s not like you&#8217;re publishing a peer reviewed journal in which the academic credentials of each commenter must be ascertained to demonstrate they are true peers.</p>
<p>One thing that&#8217;s currently different between intellispammers and Elizabots, and is that unlike the latter, the former do not yet have an energy budget sufficient to engage in any resulting dialogue. Even when they do, or when even <a href="http://en.wikipedia.org/wiki/Elbonia">Elbonians</a> start getting paid pennies for having jejune repartee with bloggers simply to slip in some promotional links or keywords, the blogger still has an energy budget that dictates how many comments are worthy of their consideration or worth replying to.</p>
<p>A far trickier problem is what a human commenter is to do when a blogger specifically rejects their further comments, or even erases their historical comments.</p>
<p>I fancy a far more peer-to-peer+reputation metric based means of blogging &#8211; and trackbacks still don&#8217;t cut it. Then somewhat like Slashdot, all participants can decide if certain other participants are spammers, religiously/politically unpalatable (subjective), or by default worthy of being considered their peers. Perhaps this is a job for Google? Maybe they&#8217;re already working on it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Assaf</title>
		<link>http://labnotes.org/2008/07/06/smart-spam-and-new-comment-policy/comment-page-1/#comment-140790</link>
		<dc:creator>Assaf</dc:creator>
		<pubDate>Tue, 08 Jul 2008 16:46:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labnotes.org/?p=1085#comment-140790</guid>
		<description>Did I mention not hypothetical?

Here&#039;s a comment I just got on a blog post discussing login issues (not on Labnotes):

&quot;I too had faced this problem initially then one of my friends suggested me that before setting the password I must clear the browser. And after that every thing was fine&quot;

They left name, email address and URL linking to the Bangalore Management Academy.

Real comment, drive-by comment or automated spam?</description>
		<content:encoded><![CDATA[<p>Did I mention not hypothetical?</p>
<p>Here&#8217;s a comment I just got on a blog post discussing login issues (not on Labnotes):</p>
<p>&#8220;I too had faced this problem initially then one of my friends suggested me that before setting the password I must clear the browser. And after that every thing was fine&#8221;</p>
<p>They left name, email address and URL linking to the Bangalore Management Academy.</p>
<p>Real comment, drive-by comment or automated spam?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Assaf</title>
		<link>http://labnotes.org/2008/07/06/smart-spam-and-new-comment-policy/comment-page-1/#comment-140789</link>
		<dc:creator>Assaf</dc:creator>
		<pubDate>Tue, 08 Jul 2008 16:40:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labnotes.org/?p=1085#comment-140789</guid>
		<description>I picked that example to isolate the case where you clearly can&#039;t tell a spam by the content of the comment, without getting into the specific of a post. Don&#039;t get caught into the fluff/trite part of it. A drive-by comment could read &quot;this seems to not work well on PHP 4 with MySQL 5&quot;, which is adding value if someone actually used that configuration, and wasting everybody&#039;s time if they just made it up.

Eventually I have to make a judgement call. I sometimes sit on a comment for a day or two until I decide (say the target site is down), I can just leave it as moderated. New information may change that decision, but that hasn&#039;t happened yet, so it&#039;s hypothetical. 

So what&#039;s bothering me now is not the mechanism, but the decision which will eventually be made.

Say the comment is by Joe and Joe&#039;s URL goes to an online poker site. Obviously spam that deserves to be nuked, right?

What if Joe, real person, real name, actually reads my blog but always links back to their employee, since Joe is reading my blog on company time? How is that different from someone working for IBM or their own startup commenting with a company link?

I worked on a few WordPress plugins. Splogs are still blogs, and blogs use plugins, so what happens when I get a splog commenting on a plugin they might actually be using? (That&#039;s not a hypothetical question)</description>
		<content:encoded><![CDATA[<p>I picked that example to isolate the case where you clearly can&#8217;t tell a spam by the content of the comment, without getting into the specific of a post. Don&#8217;t get caught into the fluff/trite part of it. A drive-by comment could read &#8220;this seems to not work well on PHP 4 with MySQL 5&#8243;, which is adding value if someone actually used that configuration, and wasting everybody&#8217;s time if they just made it up.</p>
<p>Eventually I have to make a judgement call. I sometimes sit on a comment for a day or two until I decide (say the target site is down), I can just leave it as moderated. New information may change that decision, but that hasn&#8217;t happened yet, so it&#8217;s hypothetical. </p>
<p>So what&#8217;s bothering me now is not the mechanism, but the decision which will eventually be made.</p>
<p>Say the comment is by Joe and Joe&#8217;s URL goes to an online poker site. Obviously spam that deserves to be nuked, right?</p>
<p>What if Joe, real person, real name, actually reads my blog but always links back to their employee, since Joe is reading my blog on company time? How is that different from someone working for IBM or their own startup commenting with a company link?</p>
<p>I worked on a few WordPress plugins. Splogs are still blogs, and blogs use plugins, so what happens when I get a splog commenting on a plugin they might actually be using? (That&#8217;s not a hypothetical question)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crosbie Fitch</title>
		<link>http://labnotes.org/2008/07/06/smart-spam-and-new-comment-policy/comment-page-1/#comment-140785</link>
		<dc:creator>Crosbie Fitch</dc:creator>
		<pubDate>Tue, 08 Jul 2008 07:50:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labnotes.org/?p=1085#comment-140785</guid>
		<description>As I said, if it is impossible to determine whether a comment is genuine or spam then it doesn&#039;t matter.

If, perversely, you explicitly invite fluff/trite comments, as in &quot;What say you good people? Yay or Nay?&quot;, then you do indeed have to count the yays of fluff spammers. It&#039;s a bit of a contrived example of yours. Your unwritten editorial policy is probably to deprecate &quot;I agree&quot; fluff - newbie commenters that indulge in it soon learn that it&#039;s of little worth (until such time as reputation metrics reveal the true import of &#039;I agree&#039;).

For those who moderate comments, I&#039;d imagine a redaction button/option would only be used in the situation where you aren&#039;t sure and would rather not waste time angsting about whether the potential offence and backlash caused by deletion of an off-topic/trite/fluff/possibly spam comment outweighs the irritation of its presence to other readers. Redaction would convert it to a weeny icon, with alt-text hover excerpt, and with javascript onclick popup for the entire comment (links auto converted to text).

I think you recognise that you are going to have to deal with this problem (even though you don&#039;t want to). I&#039;m just trying to suggest that the quickest way of dealing with it is to avoid it, and simply redact the borderline cases. The other cases take a moment anyway. Redaction is a way of also only taking a moment.

A) Fair comment (publish)
B) Spam, abuse, obscene, etc. (unpublish/delete)
C) Hmmm. Not sure... (redact)

Then, because the redacted comment retains its integrity (links despite being in text form can be reconstituted), it&#039;s also an easy thing to have an Unredact option, e.g. when you discover that it was an important dignitary who left an apparently off-topic comment under what they thought you&#039;d recognise was a well known alias. Perhaps George Clooney might submit a vaguely relevant comment about styling his new online casino website [link] under the alias Clooney Tunes?</description>
		<content:encoded><![CDATA[<p>As I said, if it is impossible to determine whether a comment is genuine or spam then it doesn&#8217;t matter.</p>
<p>If, perversely, you explicitly invite fluff/trite comments, as in &#8220;What say you good people? Yay or Nay?&#8221;, then you do indeed have to count the yays of fluff spammers. It&#8217;s a bit of a contrived example of yours. Your unwritten editorial policy is probably to deprecate &#8220;I agree&#8221; fluff &#8211; newbie commenters that indulge in it soon learn that it&#8217;s of little worth (until such time as reputation metrics reveal the true import of &#8216;I agree&#8217;).</p>
<p>For those who moderate comments, I&#8217;d imagine a redaction button/option would only be used in the situation where you aren&#8217;t sure and would rather not waste time angsting about whether the potential offence and backlash caused by deletion of an off-topic/trite/fluff/possibly spam comment outweighs the irritation of its presence to other readers. Redaction would convert it to a weeny icon, with alt-text hover excerpt, and with javascript onclick popup for the entire comment (links auto converted to text).</p>
<p>I think you recognise that you are going to have to deal with this problem (even though you don&#8217;t want to). I&#8217;m just trying to suggest that the quickest way of dealing with it is to avoid it, and simply redact the borderline cases. The other cases take a moment anyway. Redaction is a way of also only taking a moment.</p>
<p>A) Fair comment (publish)<br />
B) Spam, abuse, obscene, etc. (unpublish/delete)<br />
C) Hmmm. Not sure&#8230; (redact)</p>
<p>Then, because the redacted comment retains its integrity (links despite being in text form can be reconstituted), it&#8217;s also an easy thing to have an Unredact option, e.g. when you discover that it was an important dignitary who left an apparently off-topic comment under what they thought you&#8217;d recognise was a well known alias. Perhaps George Clooney might submit a vaguely relevant comment about styling his new online casino website [link] under the alias Clooney Tunes?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

