...
A permanent solution to weblog spam would be one that requires the comment spammer to expend more resources to send the spam than they can gain through spamming while minimising the amount of resources that the weblog owner needs to expend. These resources include time, money and compute cycles.
Users need to feel that they can trust the solution. Two examples from the e-mail domain are blacklists such as the MAPS RBL and whitelists such as Iron{{{ Wiki Markup }}
}Port
Bonded
{{{
}}}Sender.
In the case of blacklists, listees complain that the listing is unfair. (See \[http://bruce.pennypacker.org/spamrules.html Rule #2\].) In the case of Bonded{{{}}}Sender,
some
users
incorrectly
assume
that
Iron
{{{
}}}Port is publishing a list of organisations who have paid them for the privilege of spamming.
The solution should not interfere with legitimate discussions. Delaying the posting of legitimate comments means that users can not easily engage in discussions.
...
- PHSDL http://www.phsdl.net
\[http://www.phsdl.net/project_honeypot.php PHSDL Malware and Redirect Spam Domains Live Public List\]unmigrated-wiki-markupWiki Markup - \[http://www.nabble.com/PHSDL-contribution-to-BlogSpamAssissin-to14304628.html#a14306020 BlogSpamAssassin Mailing List Contribution by PHSDL\]
\[http://www.travelinasia.net/forum/index.php PHSDL Honeypot Forum\]Wiki Markup
Project Framework Constraints
...
BlogSpamAssassin Sub Algorithm PHSDL Filter Test
...