comment on

I've heard that particular spam-defense before, and it's clever. The problem is that you are stuck with the copyright holder's definition of "spam", which has a high possiblity for abuse. It's potentially a new ICANN/VeriSign in the making. Sure, you could get everyone to try using a new haiku with a different copyright holder, but once the idea is entrenched, it'll be about as easy to switch everyone to that haiku as it is to switch everyone to alternative DNS root servers.

(Meta-thought: a lot of proposed or even implemented spam solutions are as bad or worse than the problem. This is one of them.)

----
: () { :|:& };:

Note: All code is untested, unless otherwise stated

In reply to Re: Re: Re: Re: What if it were you instead of Linus? by hardburn
in thread What if it were you instead of Linus? by grantm

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Keep It Simple, Stupid
	PerlMonks