Author: M.Prince (28 Aug 06 5:30pm)
Yeah... I know. Just hasn't been a priority to fix.
We actually removed the little button from installed honey pots a while ago. We had run tests and found that there was a statistically significant up-tick in the amount of addresses that were picked up when the button wasn't there. Initially, we thought we'd created the holy grail: a simple snippit of HTML that you could place on your website and harvesters would pass you by.
That turned out to both be true, and not so true. After playing with a bunch of the most common harvesting programs, some of them had an option to "avoid spam traps." When this option was activated, they in fact did avoid any page that contained the button.
To figure out what was going on for sure, we began to strip down the button. Turns out the "avoid spamtraps" function wasn't looking for the button itself, instead it was looking for any occurrances of the words: harvester, spamtrap, honey pot, etc....
What's interesting is that you can use this to your advantage. Including the button will work. What also works is just putting those words somewhere -- ANYWHERE -- on your page. In fact, we found that the "smart" harvesters would skip over your page if the text was contained in a tag (e.g., <harvester spamtrap honey pot />). Or even if you include them somewhere in the <head> element of the page.
So, at some point, we'll get around to fixing the button's HTML to correctly validate. (I appreciate the code you posted.) In the meantime, if you want to avoid harvesters, one great trick is just to include some text in the <head> of your page that suggests to them that maybe the page is a spamtrap.