<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
   <channel>
      <title>Making Light :: Google&apos;s fighting comment spam :: comments</title>
      <link>http://nielsenhayden.com/makinglight/archives/007340.html#comments </link>
      <description>Language, fraud, folly, truth, history, and knitting. Et cetera.</description>
      <language>en</language>
      <lastBuildDate>Sun, 08 Jun 2008 13:18:21 -0500</lastBuildDate>
      <generator>http://www.sixapart.com/movabletype/?v=3.33</generator>
      
      <item>
      <title>Google's fighting comment spam</title>
      <description>This isn&amp;#8217;t brand-new news, but I&amp;#8217;m finding that a lot of people haven&amp;#8217;t heard about it, and it&amp;#8217;s useful. From...</description>
      <content:encoded>This isn&#8217;t brand-new news, but I&#8217;m finding that a lot of people haven&#8217;t heard about it, and it&#8217;s useful. From...</content:encoded>
      <link>http://nielsenhayden.com/makinglight/archives/007340.html</link>
      </item>

                  <item>
         <title>Google&apos;s fighting comment spam -- comment #1 from dan</title>
         <description>comment from dan on 18.Mar.06</description>
         <content:encoded><p>Excellent news, Teresa; thank you! </p>
	 <p>Posted March 18, 2006  1:20 AM by dan</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117308</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117308</guid>
         <pubDate>Sat, 18 Mar 2006 01:20:31 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #2 from Keir</title>
         <description>comment from Keir on 18.Mar.06</description>
         <content:encoded><p> I understand that Slashdot has used this property for links posted to the comments for quite a while. Along with the moderation system, it seems to work quite well at keeping spam down. </p>

<p>Given that Slashcode is freely available, I'd imagine that it wouldn't be that hard to do it on your own blog/forum/whatever.</p>

<p>Of course, the Next Big Thing for spammers is going to be wikis. Especially Wikipedia like wikis, that aren't quite so large. </p>

<p>Highly placed on Google searches, often linked to, and easily editable. Wikimedia's wikis'll be OK, given the size of the user base, but smaller wikis'll get hit hard.</p>

<p>(The above isn't my idea; but I think that it is very likely.)</p>
	 <p>Posted March 18, 2006  1:57 AM by Keir</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117314</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117314</guid>
         <pubDate>Sat, 18 Mar 2006 01:57:36 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #3 from Christopher</title>
         <description>comment from Christopher on 18.Mar.06</description>
         <content:encoded><p>It happened to a Lovecraft wiki I spent some time working on. Very irritating.</p>
	 <p>Posted March 18, 2006  2:09 AM by Christopher</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117317</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117317</guid>
         <pubDate>Sat, 18 Mar 2006 02:09:54 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #4 from Reinder</title>
         <description>comment from Reinder on 18.Mar.06</description>
         <content:encoded><p>It's happened, a lot, to comixpedia.org, which had to disallow editing for unregistered users (and a few months later got spammed by bots that registered themselves).</p>
	 <p>Posted March 18, 2006  4:15 AM by Reinder</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117325</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117325</guid>
         <pubDate>Sat, 18 Mar 2006 04:15:32 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #5 from Cory Doctorow</title>
         <description>comment from Cory Doctorow on 18.Mar.06</description>
         <content:encoded><p>I don't like this solution, because it  assumes that there's never any pagerank data to be gleaned from a message-board on a blog-post. I think Making Light is the best counter-example: if you folks are discussing subject X and one or more of the comments link to page Y, I think there's a good chance that page Y is relevant to subject X and it's silly for Google to throw it away.</p>
	 <p>Posted March 18, 2006  6:39 AM by Cory Doctorow</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117336</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117336</guid>
         <pubDate>Sat, 18 Mar 2006 06:39:34 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #6 from rhandir</title>
         <description>comment from rhandir on 18.Mar.06</description>
         <content:encoded><p>Cory's right. Making Light is a <i>high value target</i> both to spammers and to google. If I want to find a non-obvious connection between two pieces of data, this is the place to come.</p>

<p>Relnofollow is a band-aid. In the long term, being an anti-search engine is going to be more helpful to  us. What I mean is that there are a certain percentage of sites I <i>never</i> want to go to: malware/phishing sites, and a larger percentage of sites that are just plain useless, such as splogs. </p>

<p>There is a kind of <i>mirror mirror universe</i> of a web that no one would want to visit. (Perhaps where the usual characters wear goatees?) </p>

<p>I'm not talking about the usual filtering stuff. I'm thinking of something more elaborate than a blacklist, or the usual bayesian filtering stuff. Exactly how you could distinguish anti-search behavior (visit once, never want to go to again) from low-interest, but useful sites (I only needed something there once) I'm not sure.</p>

<p>*sigh* I had a better-formed thought on all of this that I was going to share. I'll try again later today.</p>

<p>-r.<br />
</p>
	 <p>Posted March 18, 2006  7:11 AM by rhandir</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117338</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117338</guid>
         <pubDate>Sat, 18 Mar 2006 07:11:12 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #7 from Serge</title>
         <description>comment from Serge on 18.Mar.06</description>
         <content:encoded><p>Always make sure your agonizer is fully charged, rhandir. </p>
	 <p>Posted March 18, 2006  7:45 AM by Serge</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117342</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117342</guid>
         <pubDate>Sat, 18 Mar 2006 07:45:19 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #8 from Kate Nepveu</title>
         <description>comment from Kate Nepveu on 18.Mar.06</description>
         <content:encoded><p>This is a good place to throw news of two new MT 3.2 plugins to:</p>

<p><a href="http://projects.heavymeta.org/HMPassphrase/wiki/Description" rel="nofollow">HM Passphrase</a>, which appears to ask the commentor a text question ("What's Brad's first name?") and require a text passphrase ("Brad") before posting the comment. It's a prove-you're-human test that sounds really good to me since it doesn't require images or sound.</p>

<p><a href="http://mt-hacks.com/blacklist32.html" rel="nofollow">MT Hacks Blacklist 3.2</a>: for people who want to use MT Blacklist *in addition* to the built-in Spam Lookup of MT 3.2.</p>

<p>I also don't like nofollow for the reasons Cory states.</p>
	 <p>Posted March 18, 2006  8:48 AM by Kate Nepveu</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117343</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117343</guid>
         <pubDate>Sat, 18 Mar 2006 08:48:16 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #9 from James D. Macdonald</title>
         <description>comment from James D. Macdonald on 18.Mar.06</description>
         <content:encoded><p>Trackback spam and comment spam are all over the place.  Even though we have extensive blacklists here, twelve of the last twenty comments posted to Making Light were spam -- for Texas Holdem Poker, as it happens -- leading back to various pages on blogspot.com.  Because blogspot can have good content I haven't just blacklisted all of blogspot, but ... it's tempting.</p>

<p>We've turned off showing trackbacks entirely.  But because they're necessary for the "other posts by" functionality, they're still listed internally. We get around fifty trackback spams per day.</p>

<p>In my unending quest to find Things To Do About Comment Spam, I found this:  <a href="http://www.linksleeve.org/" rel="nofollow">http://www.linksleeve.org/</a></p>

<p>It's an interesting idea ... an identical link posted to some threshhold level of different blogs would be automatically removed.  But I have a couple of concerns.  One is that half the links on that site are themselves broken.  Another is that if there were some hard-hitting, fast moving news that suddenly struck bloggerdom (Bush Shoots Cheney, Rumsfeld, Self in Tense White House Standoff) with lots of folks linking to the news story all at once, would it be deleted?</p>

<p>And ... big objection ... the way it seems to work is the author of the software <a href="http://www.linksleeve.org/blogger.php" rel="nofollow">wants me to type in my email address, username, <i>and password</i> to a webform.</a>  To which all I can say is riiiiiiight.</p>

<p>So.  Right now we have a lot of fiddly hand-work.  And a Band-aid.   If what I'm looking at is arterial bleeding, a Band-aid isn't much good, but if that's all I've got I'm going to use it.</p>
	 <p>Posted March 18, 2006  9:05 AM by James D. Macdonald</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117345</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117345</guid>
         <pubDate>Sat, 18 Mar 2006 09:05:30 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #10 from James D. Macdonald</title>
         <description>comment from James D. Macdonald on 18.Mar.06</description>
         <content:encoded><p>Between my last comment and this came yet another comment spam for Texas Holdem, leading back to yet another blogspot.com page.</p>

<p>Some days I'm tempted to blacklist the entire *.info  domain.  The only reason I don't is that trilobites.info is a useful and interesting site. Think of it as the one just man in Sodom who's allowing all the rest to live.</p>

<p>We have Blacklist 3.2 running here.  We'll have to see about Passphrase.</p>
	 <p>Posted March 18, 2006  9:17 AM by James D. Macdonald</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117346</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117346</guid>
         <pubDate>Sat, 18 Mar 2006 09:17:22 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #11 from Serge</title>
         <description>comment from Serge on 18.Mar.06</description>
         <content:encoded><p>For the longest time, my employer's email service blocked everything that came from the ***.videotron.ca domain. Why? Videotron is apparently used a lot by spammers. That meant being unable to write to my friend Nicole up in Quebec City. Unfortunately, when I used my alternate less-frequently-checked-upon Comcast address, HER filter flagged my email as spam. </p>

<p>America vs Canada... The World at War...</p>
	 <p>Posted March 18, 2006 10:12 AM by Serge</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117351</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117351</guid>
         <pubDate>Sat, 18 Mar 2006 10:12:51 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #12 from JohnD</title>
         <description>comment from JohnD on 18.Mar.06</description>
         <content:encoded><p>I'm no fan of comment spam, but I have to agree with Cory that rel="nofollow" is a less than ideal solution when applied unilaterally.  Some blogging software now imposes it automatically, meaning that relevant links and meaningful commentary are discarded along with the trash.  This discounts what bloggers and their commenters add to the 'Net.</p>

<p>I'm not comfortable with the fact that bloggers' opinions don't always count toward Google pageranking, particularly now that so much breaking political news spreads via the blogosphere.</p>
	 <p>Posted March 18, 2006 10:25 AM by JohnD</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117354</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117354</guid>
         <pubDate>Sat, 18 Mar 2006 10:25:58 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #13 from TomB</title>
         <description>comment from TomB on 18.Mar.06</description>
         <content:encoded><p>I think it's the search engine's job to explore the <i>mirror, mirror universe</i>, the dark side of the web. I don't even see what's so hard about it. Just follow the links. If they lead to malware or known shady businesses or scams, apply a large negative to the page rank. </p>
	 <p>Posted March 18, 2006 11:18 AM by TomB</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117358</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117358</guid>
         <pubDate>Sat, 18 Mar 2006 11:18:14 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #14 from James D. Macdonald</title>
         <description>comment from James D. Macdonald on 18.Mar.06</description>
         <content:encoded><p>Making Light occassionally links to known shady businesses and scams (see the "fraud" listed right on the top of the page as one of the subjects we explore).</p>

<p>Should Making Light have a large negative attached to its pagerank?</p>
	 <p>Posted March 18, 2006 11:59 AM by James D. Macdonald</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117364</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117364</guid>
         <pubDate>Sat, 18 Mar 2006 11:59:14 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #15 from Hob</title>
         <description>comment from Hob on 18.Mar.06</description>
         <content:encoded><p>JohnD: When you talk about "what <i>bloggers and their commenters</i> add to the Net", that little phrase equates two things that aren't the same for this purpose. Bloggers are the publishers/editors of the site; their words and links reflect what they want the site to be, and in most cases they only have that power on one site. Commenters are graffiti artists (or, in some cases, graffiti-stenciling robots) and they can post the same thing to dozens or hundreds of blogs. That's not to devalue their opinions - lots of us read blogs for the comments. But it makes sense for a search engine to prioritize unique content from authors who have some stake in their venue.</p>
	 <p>Posted March 18, 2006 12:00 PM by Hob</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117365</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117365</guid>
         <pubDate>Sat, 18 Mar 2006 12:00:59 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #16 from Teresa Nielsen Hayden</title>
         <description>comment from Teresa Nielsen Hayden on 18.Mar.06</description>
         <content:encoded><p>Cory, I don't intend to code "nofollow" into links from my comment threads. I do think that might be appropriate for venues that get a few comments per thread at most, and I'd definitely recommend it for seldom-used or abandoned weblogs where <a href="http://www.rossino.net/cgi-bin/blog/mt-comments.cgi?entry_id=64" rel="nofollow">the</a> <a href="http://www.opaquelucidity.com/movabletype/mt-comments.cgi?entry_id=272" rel="nofollow">accumulated</a> <a href="http://www.classicsnetwork.com/forums/showthread.php?t=251&page=3&pp=15" rel="nofollow">comment</a> <a href="http://blog.vanillabones.net/archives/000032.html" rel="nofollow">spam</a> <a href="http://gibbs.teacherhosting.com/archives/000657.html" rel="nofollow">never</a> <a href="http://larry.fifthfloor.org/blog/archives/000093.html" rel="nofollow">gets</a> <a href="http://kenmunds.com/praisereport/archives/000221.html" rel="nofollow">cleared</a> <a href="http://blog.tilos.hu/roadmovie/archives/001899.html" rel="nofollow">out</a>.</p>
	 <p>Posted March 18, 2006 12:26 PM by Teresa Nielsen Hayden</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117374</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117374</guid>
         <pubDate>Sat, 18 Mar 2006 12:26:52 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #17 from Xopher (Christopher Hatton)</title>
         <description>comment from Xopher (Christopher Hatton) on 18.Mar.06</description>
         <content:encoded><p><i>sites that are just plain useless, such as splogs</i></p>

<p>[*]?</p>
	 <p>Posted March 18, 2006 12:56 PM by Xopher (Christopher Hatton)</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117378</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117378</guid>
         <pubDate>Sat, 18 Mar 2006 12:56:43 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #18 from rhandir</title>
         <description>comment from rhandir on 18.Mar.06</description>
         <content:encoded><p>Two technical suggestions re: spam supression. </p>

<p>1. Automatically rate all posts by known good users 1, and unknown users 0. 1's are displayed, 0's only have the first 26 characters displayed (using dynamic css tricks), and the html is neutered. Possibly a number of clicks on the 0's topic lines by known good users acts as a voting system; when a threshold is reached, the full comment is displayed. Known good users might be simply identified by a randomly assigned serial number in a cookie. (No userid info needed.)</p>

<p>Not ideal, but for this stuff, inconvenice / delaying tactics / increased complexity for the autospammer seems to be a better solution than endless blackist maintainance. [See greymilter, greylisting in discussions on email spam elswhere on the net.]</p>

<p>2. Use gpg encryption/decryption plus autodisemvowling:<br />
Assign a gpg key to a poster (using a cookie?). Encrypt each post, using the stored key value when the post is written on the "write post" page.</p>

<p>On the server side, decrypt the written post using the other half of the key. Legit posts don't get their keys revolked and can be read as usual, Illegit posts get their keys revolked, and are disemvowled after decryption.* Forged keys don't work. Revoke keys as needed using traditional anti spam tricks.</p>

<p>The advantage? Not having to mess with a database of userlogins, but still being able to retroactively cancel a set of posts. Regular users would be able to post without more than one moderation review as long as their cookies lasted.</p>

<p>-r.</p>

<p>*or rot-13. Or give the client a universal decrypt key so you can read the "unfiltered" page at anytime. This is cryptographically weaker, but prevents any data from being lost.<br />
</p>
	 <p>Posted March 18, 2006  1:33 PM by rhandir</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117387</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117387</guid>
         <pubDate>Sat, 18 Mar 2006 13:33:47 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #19 from TomB</title>
         <description>comment from TomB on 18.Mar.06</description>
         <content:encoded><p><i>Should Making Light have a large negative attached to its pagerank?</i></p>

<p>Not for links with rel="nofollow". Or maybe even rel="scam". </p>
	 <p>Posted March 18, 2006  5:05 PM by TomB</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117417</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117417</guid>
         <pubDate>Sat, 18 Mar 2006 17:05:50 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #20 from Clifton Royston</title>
         <description>comment from Clifton Royston on 18.Mar.06</description>
         <content:encoded><p>The problem with Google's answer as a solution, is that it presumes that comment spammers will be just smart enough to perceive that this makes their efforts less useful and will simply give up posting to blogs that use nofollow.  Based on the last 10 years of struggle with email spam, I'd say the more likely reaction will be to post 10 times as many comment spams to 10 times as many blogs and hope some of them are on sites that don't use it.</p>

<p>On one of the anti-spam mailing lists I'm on, we're just discussing comment spam and whether there's any relevance to email spam techniques.  There is a lot of wheel re-invention going on in the anti-blog-spam world.</p>

<p>One of the problems with bringing email people into it is that there are a large chunk of people who simply don't get the blog idea and so don't see why this is a problem.  "Why would you want to let random strangers post on your web site? Isn't that just inviting trouble?"  Well, of course it's for much the same reason that one wants to accept mail from random strangers, in principle.  But I digress.</p>

<p>At any rate, from the people who do grok both issues, two important techniques you can reuse from email spam prevention:<br />
<ul><li>URI block lists: check all posted URIs (both in text or as hyperlinks) with a DNS lookup against the more reliable URI blocklists, such as those at <a href="http://www.surbl.org" rel="nofollow">www.surbl.org</a>(QV)  If I recall correctly, you can also use the <a href="http://www.spamhaus.org" rel="nofollow">Spamhaus</a> list as a URI blocklist.</li><br />
<li>If possible block even web-server connections,  and definitely block all post attempts, from IP addresses listed in the botnet- and trojaned PC-oriented DNS BLs.  In many cases, these same networks of PCs are being used to send email spam and post comment spam.  The CBL blocklist would be a good one to look at using.</li><br />
<li>Bayesian software seems to work for some, too.</li></ul>Perhaps you're already doing all of this; if so, good for you.  Unfortunately I don't know enough about blog software configuration to help you with wiring this all in to your webserver.<br />
</p>
	 <p>Posted March 18, 2006  7:05 PM by Clifton Royston</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117432</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117432</guid>
         <pubDate>Sat, 18 Mar 2006 19:05:32 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #21 from Clifton Royston</title>
         <description>comment from Clifton Royston on 18.Mar.06</description>
         <content:encoded><p>Xopher: splogs = "spam blogs" - sites that are supposed to look to a search engine like blogs, but contain nothing but incestuous messes of links to each other, random text, and search keywords which they want someone to enter and stumble onto their site.  Maddening hateful stuff when you are actually looking for information.  Sepending on how well Google is doing in tweaking their algorithms, sometimes you'll wind up with several pages of these as the top results when you search for some popular keyword, but lately Google seems to have been doing pretty well at dumping them.</p>
	 <p>Posted March 18, 2006  8:24 PM by Clifton Royston</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117435</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117435</guid>
         <pubDate>Sat, 18 Mar 2006 20:24:11 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #22 from Clifton Royston</title>
         <description>comment from Clifton Royston on 18.Mar.06</description>
         <content:encoded><p>BTW, Teresa:  You currently are putting "nofollow" automatically into links posted in the comments.  Take a look at the HTML source for this comment thread, for instance.  I see nothing wrong with this, but your comment just upstream suggests that's not intentional.</p>
	 <p>Posted March 18, 2006  8:27 PM by Clifton Royston</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117436</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117436</guid>
         <pubDate>Sat, 18 Mar 2006 20:27:53 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #23 from James D. Macdonald</title>
         <description>comment from James D. Macdonald on 18.Mar.06</description>
         <content:encoded><p>rel="nofollow" in intentional, and has been in the comment threads here since about fifteen minutes after it became available as a MT plugin.</p>

<p>rel="nofollow" doesn't appear in the main posts except by deliberate design.</p>
	 <p>Posted March 18, 2006  8:36 PM by James D. Macdonald</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117437</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117437</guid>
         <pubDate>Sat, 18 Mar 2006 20:36:25 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #24 from Karen Funk Blocher</title>
         <description>comment from Karen Funk Blocher on 18.Mar.06</description>
         <content:encoded><p>As a non-spamming Blogspot blogger, I hope you'll continue to resist the tempation to block that domain.</p>

<p>AOL Journals have had rel=no follow for many months, perhaps years. That hasn't prevented several massive  comment spam attacks there.</p>

<p>Question:  does no follow affect Technorati functions?</p>
	 <p>Posted March 18, 2006  8:59 PM by Karen Funk Blocher</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117442</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117442</guid>
         <pubDate>Sat, 18 Mar 2006 20:59:09 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #25 from Epacris</title>
         <description>comment from Epacris on 18.Mar.06</description>
         <content:encoded><p>As another blogspotter, I know that it is having problems with many spamblogs of assorted kinds, as well as having to institute comment spam blocking, <strong>but</strong> it's also the better in quite a few ways of the (free) blogging spots I've tried.  Hence my main blog is there, as you can see from the link here &mdash; though there is a backup LJ.</p>

<p>I had been considering looking at a paid site, but another serious medical problem has arisen, so funds are going to be short again.</p>
	 <p>Posted March 18, 2006  9:52 PM by Epacris</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117450</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117450</guid>
         <pubDate>Sat, 18 Mar 2006 21:52:17 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #26 from Vicki</title>
         <description>comment from Vicki on 18.Mar.06</description>
         <content:encoded><p>Also in .info, two transit systems whose sites I find useful: mta.info is the NYC-area transit system (including MTA's commuter rail and bridges and tunnels) and mtr.info is the Montreal metro and commuter rail. </p>
	 <p>Posted March 18, 2006 11:32 PM by Vicki</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117468</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117468</guid>
         <pubDate>Sat, 18 Mar 2006 23:32:41 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #27 from Terry Karney</title>
         <description>comment from Terry Karney on 19.Mar.06</description>
         <content:encoded><p>I am of a mixed mind. There are a lot of things in the comments that I go back to.  I find them using Google.</p>

<p>From a purely selfish standpoint, I never got around to bookmarking the description of interrogation, and my venting on torture in Electrolite.  I can still find them, but only by hitting from secondary links,</p>

<p>It's not so much my ego (though having my name be a high ranking hit is nice) but that I like that piece of writing, and I want it to be read as often as torture is praised.</p>

<p>But, on the flip side, comment spam is nasty stuff, and killing it matters.  I just hope a better band-aid comes along.</p>

<p>TK</p>
	 <p>Posted March 19, 2006  5:35 AM by Terry Karney</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117510</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117510</guid>
         <pubDate>Sun, 19 Mar 2006 05:35:21 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #28 from winna</title>
         <description>comment from winna on 19.Mar.06</description>
         <content:encoded><p>I just installed Scode for MT 3.2 and I'm pretty happy about it, especially since typekey was keeping a lot of people from posting. Now they just enter an automatically generated code along with their comment et voila!</p>

<p>Some comment spam mysteriously gets through, but it's one or two a day, not hundreds.</p>
	 <p>Posted March 19, 2006 10:22 AM by winna</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117544</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117544</guid>
         <pubDate>Sun, 19 Mar 2006 10:22:54 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #29 from Ceri</title>
         <description>comment from Ceri on 19.Mar.06</description>
         <content:encoded><p>Vicki:  Did you mean stm.info for the Montreal transit site?  Mtr.info redirects me to a .de site, but I use the stm.info site all the time (Tous Azimuts is your friend).</p>
	 <p>Posted March 19, 2006 11:36 AM by Ceri</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117554</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117554</guid>
         <pubDate>Sun, 19 Mar 2006 11:36:57 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #30 from Kevin Marks</title>
         <description>comment from Kevin Marks on 19.Mar.06</description>
         <content:encoded><p>Yes, <a href="http://epeus.blogspot.com/2005_01_01_epeus_archive.html#110622107470551279" rel="nofollow">Technorati pays attention to rel="nofollow"</a> (Heck, I wrote it's <a href="http://microformats.org/wiki/rel-nofollow" rel="nofollow">formal spec</a>). In fact, there is a more general way to express your approval or disapproval called <a href="http://microformats.org/wiki/vote-links" rel="nofollow">Vote Links</a> which we supported before that.<br />
At Technorati, rel="nofollow" is treated the save as rev="vote-against", ie the link is included in our searches for the linked-to URL, but it is not counted towards the Authority of the linked-to page (where Authority is our metric based on links from distinct blogs over the last 6 months, used for ranking and filtering).</p>
	 <p>Posted March 19, 2006  4:43 PM by Kevin Marks</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117603</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117603</guid>
         <pubDate>Sun, 19 Mar 2006 16:43:40 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #31 from Eve</title>
         <description>comment from Eve on 19.Mar.06</description>
         <content:encoded><p><i>Google’s fighting comment spam</i></p>

<p>Doo-dah, doo-dah!</p>
	 <p>Posted March 19, 2006  4:56 PM by Eve</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117606</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117606</guid>
         <pubDate>Sun, 19 Mar 2006 16:56:08 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #32 from Mike Kozlowski</title>
         <description>comment from Mike Kozlowski on 19.Mar.06</description>
         <content:encoded><p>It's not an observation original with me, but it's worth noting that rel="nofollow" solves Google's problem (spam links making search results less useful), but not bloggers' problems (spam comments making comment sections less readable and/or time taken to clean up comment spam).</p>

<p>I've been using nofollow for a while now, and haven't noticed any decrease in the amount of comment spam I get.</p>
	 <p>Posted March 19, 2006 11:01 PM by Mike Kozlowski</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117664</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117664</guid>
         <pubDate>Sun, 19 Mar 2006 23:01:32 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #33 from Kevin Marks</title>
         <description>comment from Kevin Marks on 20.Mar.06</description>
         <content:encoded><p>Oops, what I meant to say was rel="nofollow" is treated as rev-"vote-abstain".</p>
	 <p>Posted March 20, 2006 12:04 AM by Kevin Marks</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117670</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117670</guid>
         <pubDate>Mon, 20 Mar 2006 00:04:23 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #34 from Skwid</title>
         <description>comment from Skwid on 20.Mar.06</description>
         <content:encoded><p>Jim, <a href="http://www.thehumblest.net/" rel="nofollow">The Humblest Blog</a> has been getting hammered by (presumably) the same blogspot spammers over the last few days.  These arseholes are vicious.  They're using an IP randomizer, so I can't block them that way.  They cycle to a different blogspot "splog" every 6 to 8 posts or so, so blacklisting them only lasts a couple of hours at best.  They put in only one link per comment, so I can't filter them that way.  I don't want to block any comments related to poker and casinos, especially since I'm about to review Last Call, and I can envision several other circumstances in which those might be legit comment topics...</p>

<p>Whatever script they're using is persistent, and runs frequently, so much so that I'd say I've gotten 3 to 5 times my usual volume of comment spam in the past few days, and deleting them is a <i>major</i> pain in Greymatter (each comment takes 3 or 5 clicks to delete, depending on circumstances).  If it keeps up through the end of the week, I'm going to have to blacklist blogspot just to stay sane, and apologize to my commenters up-front.</p>
	 <p>Posted March 20, 2006  2:12 PM by Skwid</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117784</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117784</guid>
         <pubDate>Mon, 20 Mar 2006 14:12:41 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #35 from Christopher Davis</title>
         <description>comment from Christopher Davis on 20.Mar.06</description>
         <content:encoded><p>I was getting hit by blogspot linkers, but the regexp -[a-z][a-z][a-z][a-z].blogspot.com caught 'em all. I hope it stays that way for a while.</p>
	 <p>Posted March 20, 2006  8:23 PM by Christopher Davis</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#117848</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#117848</guid>
         <pubDate>Mon, 20 Mar 2006 20:23:32 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #36 from nickk</title>
         <description>comment from nickk on  5.Feb.07</description>
         <content:encoded><p>one thing that I see for your site is that it reveal the email address on the comment poster, do you think spam bot will be able to pick those emial address up and spam the user??</p>
	 <p>Posted February  5, 2007 11:31 AM by nickk</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#170504</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#170504</guid>
         <pubDate>Mon, 05 Feb 2007 11:31:30 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #37 from Xopher sees arrogant, ironic spambot spam</title>
         <description>comment from Xopher sees arrogant, ironic spambot spam on  5.Feb.07</description>
         <content:encoded><p>Some noive.</p>
	 <p>Posted February  5, 2007 11:33 AM by Xopher sees arrogant, ironic spambot spam</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#170506</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#170506</guid>
         <pubDate>Mon, 05 Feb 2007 11:33:12 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #38 from Teresa Nielsen Hayden</title>
         <description>comment from Teresa Nielsen Hayden on  6.Feb.07</description>
         <content:encoded><p>Might, might not. Never wrong to point them out.</p>

<p>Yo, Nickk: are you real?</p>
	 <p>Posted February  6, 2007 12:10 PM by Teresa Nielsen Hayden</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#170713</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#170713</guid>
         <pubDate>Tue, 06 Feb 2007 12:10:38 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #39 from Xopher</title>
         <description>comment from Xopher on  6.Feb.07</description>
         <content:encoded><p>It was the url "dubdubdub dot eight coupons dot calm" that made me think it.</p>
	 <p>Posted February  6, 2007 12:22 PM by Xopher</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#170718</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#170718</guid>
         <pubDate>Tue, 06 Feb 2007 12:22:01 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #40 from James D. Macdonald</title>
         <description>comment from James D. Macdonald on  6.Feb.07</description>
         <content:encoded><p>People who worry about that munge their addresses, or don't give them.</p>

<p>The URL is definitely spammish.</p>
	 <p>Posted February  6, 2007  2:03 PM by James D. Macdonald</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#170731</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#170731</guid>
         <pubDate>Tue, 06 Feb 2007 14:03:12 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #41 from Spam deleted</title>
         <description>comment from Spam deleted on  6.Jun.08</description>
         <content:encoded><p>Spam from 89.113.78.6<br />
</p>
	 <p>Posted June  6, 2008 11:16 PM by Spam deleted</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#272612</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#272612</guid>
         <pubDate>Fri, 06 Jun 2008 23:16:02 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #42 from P J Evans sees another</title>
         <description>comment from P J Evans sees another on  6.Jun.08</description>
         <content:encoded><p>I'd like some. Better yet, give it to the spambot.</p>
	 <p>Posted June  6, 2008 11:44 PM by P J Evans sees another</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#272614</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#272614</guid>
         <pubDate>Fri, 06 Jun 2008 23:44:50 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #43 from Spam deleted</title>
         <description>comment from Spam deleted on  7.Jun.08</description>
         <content:encoded><p>Spam from 89.113.78.6</p>
	 <p>Posted June  7, 2008  4:35 PM by Spam deleted</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#272708</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#272708</guid>
         <pubDate>Sat, 07 Jun 2008 16:35:48 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #44 from Serge sees valium spam</title>
         <description>comment from Serge sees valium spam on  7.Jun.08</description>
         <content:encoded><p>What a bitter pill to swallow.</p>
	 <p>Posted June  7, 2008  4:40 PM by Serge sees valium spam</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#272710</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#272710</guid>
         <pubDate>Sat, 07 Jun 2008 16:40:46 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #45 from Spam deleted</title>
         <description>comment from Spam deleted on  8.Jun.08</description>
         <content:encoded><p>Spam from 89.113.78.6<br />
</p>
	 <p>Posted June  8, 2008  3:55 AM by Spam deleted</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#272802</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#272802</guid>
         <pubDate>Sun, 08 Jun 2008 03:55:08 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #46 from Rob Rusick reports percocet spam</title>
         <description>comment from Rob Rusick reports percocet spam on  8.Jun.08</description>
         <content:encoded><p>Valium...</p>

<p>Hello?</p>

<p>Valium...</p>

<p>Who's there?</p>

<p>Percocet...</p>

<p>You can't fool me, you're the Land Shark!</p>
	 <p>Posted June  8, 2008  6:54 AM by Rob Rusick reports percocet spam</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#272808</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#272808</guid>
         <pubDate>Sun, 08 Jun 2008 06:54:37 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #47 from Spam deleted</title>
         <description>comment from Spam deleted on  8.Jun.08</description>
         <content:encoded><p>Spam from 89.113.78.6<br />
</p>
	 <p>Posted June  8, 2008 12:21 PM by Spam deleted</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#272843</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#272843</guid>
         <pubDate>Sun, 08 Jun 2008 12:21:03 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #48 from Spam deleted</title>
         <description>comment from Spam deleted on  8.Jun.08</description>
         <content:encoded><p>Spam from 89.113.78.6<br />
</p>
	 <p>Posted June  8, 2008 12:24 PM by Spam deleted</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#272844</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#272844</guid>
         <pubDate>Sun, 08 Jun 2008 12:24:55 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #49 from Spam deleted</title>
         <description>comment from Spam deleted on  8.Jun.08</description>
         <content:encoded><p>Spam from 89.113.78.6 </p>
	 <p>Posted June  8, 2008 12:41 PM by Spam deleted</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#272846</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#272846</guid>
         <pubDate>Sun, 08 Jun 2008 12:41:54 -0500</pubDate>
      </item>
      
                  <item>
         <title>Google&apos;s fighting comment spam -- comment #50 from Joel Polowin sees spam</title>
         <description>comment from Joel Polowin sees spam on  8.Jun.08</description>
         <content:encoded><p>I'm afraid that with all of the recent crap on this thread, its title is making me think of "Someone-or-other's Fighting 46th", or something to that effect.</p>
	 <p>Posted June  8, 2008  1:18 PM by Joel Polowin sees spam</p></content:encoded>
         <link>http://nielsenhayden.com/makinglight/archives/007340.html#272854</link>
         <guid isPermaLink="true">http://nielsenhayden.com/makinglight/archives/007340.html#272854</guid>
         <pubDate>Sun, 08 Jun 2008 13:18:21 -0500</pubDate>
      </item>
      
      
   </channel>
</rss>