Hashcash does indeed aim to prevent it. If you don't provide a valid hash, your message is rejected. nofollow tries to work around an accept-by-default policy.

Yes, people who use Google may reap some benefit — at least, they might once the amount of abandoned but commentable blogs has sunk enough that nofollow actually makes a difference. Make no mistake, we're talking about a pretty large time scale here.

Comment spam is not useful solely because it influences rankings. Does anyone rank anything based on the content of your inbox? Yet email is flooded with spam. Sure, the fact that comment spam can be used to game search engines is a nice bonus and currently an important reason to deploy it, but if that incentive disappears, comment spam will nofollow into demise. It's here to stay.

The bottom line is: nofollow does not benefit a blog owner. Unlike other options which do. So by and large, nofollow is irrelevant on the spam front. It is only going to change the way the web works outside of spam: like the horde of bloggers who rejoiced that now they can link to the people they're deriding without improving the linkee's ranking. Sigh.

Makeshifts last the longest.


In reply to Re^6: (OT) nofollow considered harmful by Aristotle
in thread CPAN::Forum opens its virtual doors by szabgab

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.