<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: spam</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/spam.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2025-07-07T19:27:51+00:00</updated><author><name>Simon Willison</name></author><entry><title>Quoting Kyle Kingsbury</title><link href="https://simonwillison.net/2025/Jul/7/aphyr/" rel="alternate"/><published>2025-07-07T19:27:51+00:00</published><updated>2025-07-07T19:27:51+00:00</updated><id>https://simonwillison.net/2025/Jul/7/aphyr/</id><summary type="html">
    &lt;blockquote cite="https://aphyr.com/posts/389-the-future-of-forums-is-lies-i-guess"&gt;&lt;p&gt;I strongly suspect that Market Research Future, or a subcontractor, is conducting an automated spam campaign which uses a Large Language Model to evaluate a Mastodon instance, submit a plausible application for an account, and to post slop which links to Market Research Future reports. [...]&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;I don’t know how to run a community forum in this future&lt;/strong&gt;. I do not have the time or emotional energy to screen out regular attacks by Large Language Models, with the knowledge that making the wrong decision costs a real human being their connection to a niche community.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="https://aphyr.com/posts/389-the-future-of-forums-is-lies-i-guess"&gt;Kyle Kingsbury&lt;/a&gt;, The Future of Forums is Lies, I Guess&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/community"&gt;community&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/moderation"&gt;moderation&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ai"&gt;ai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/generative-ai"&gt;generative-ai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/mastodon"&gt;mastodon&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/llms"&gt;llms&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/slop"&gt;slop&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ai-ethics"&gt;ai-ethics&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ai-misuse"&gt;ai-misuse&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/kyle-kingsbury"&gt;kyle-kingsbury&lt;/a&gt;&lt;/p&gt;



</summary><category term="community"/><category term="moderation"/><category term="spam"/><category term="ai"/><category term="generative-ai"/><category term="mastodon"/><category term="llms"/><category term="slop"/><category term="ai-ethics"/><category term="ai-misuse"/><category term="kyle-kingsbury"/></entry><entry><title>Quoting @deepfates</title><link href="https://simonwillison.net/2024/May/7/deepfates/" rel="alternate"/><published>2024-05-07T15:59:47+00:00</published><updated>2024-05-07T15:59:47+00:00</updated><id>https://simonwillison.net/2024/May/7/deepfates/</id><summary type="html">
    &lt;blockquote cite="https://twitter.com/deepfates/status/1787472784106639418"&gt;&lt;p&gt;Watching in real time as "slop" becomes a term of art. the way that "spam" became the term for unwanted emails, "slop" is going in the dictionary as the term for unwanted AI generated content&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="https://twitter.com/deepfates/status/1787472784106639418"&gt;@deepfates&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/definitions"&gt;definitions&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ethics"&gt;ethics&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ai"&gt;ai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/generative-ai"&gt;generative-ai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/llms"&gt;llms&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/slop"&gt;slop&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ai-ethics"&gt;ai-ethics&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ai-misuse"&gt;ai-misuse&lt;/a&gt;&lt;/p&gt;



</summary><category term="definitions"/><category term="ethics"/><category term="spam"/><category term="ai"/><category term="generative-ai"/><category term="llms"/><category term="slop"/><category term="ai-ethics"/><category term="ai-misuse"/></entry><entry><title>Quoting dang</title><link href="https://simonwillison.net/2024/Feb/19/dang/" rel="alternate"/><published>2024-02-19T15:57:50+00:00</published><updated>2024-02-19T15:57:50+00:00</updated><id>https://simonwillison.net/2024/Feb/19/dang/</id><summary type="html">
    &lt;blockquote cite="https://news.ycombinator.com/context?id=39426902"&gt;&lt;p&gt;Spam, and its cousins like content marketing, could kill HN if it became orders of magnitude greater—but from my perspective, it isn't the hardest problem on HN. [...]&lt;/p&gt;
&lt;p&gt;By far the harder problem, from my perspective, is low-quality comments, and I don't mean by bad actors—the community is pretty good about flagging and reporting those; I mean lame and/or mean comments by otherwise good users who don't intend to and don't realize they're doing that.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="https://news.ycombinator.com/context?id=39426902"&gt;dang&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/hacker-news"&gt;hacker-news&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/moderation"&gt;moderation&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/social-software"&gt;social-software&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;&lt;/p&gt;



</summary><category term="hacker-news"/><category term="moderation"/><category term="social-software"/><category term="spam"/></entry><entry><title>Quoting Del Harvey</title><link href="https://simonwillison.net/2023/Nov/22/del-harvey/" rel="alternate"/><published>2023-11-22T04:59:47+00:00</published><updated>2023-11-22T04:59:47+00:00</updated><id>https://simonwillison.net/2023/Nov/22/del-harvey/</id><summary type="html">
    &lt;blockquote cite="https://www.wired.com/story/del-harvey-twitter-trust-and-safety-breaks-her-silence/"&gt;&lt;p&gt;I remember that they [Ev and Biz at Twitter in 2008] very firmly believed spam was a concern, but, “we don’t think it's ever going to be a real problem because you can choose who you follow.” And this was one of my first moments thinking, “Oh, you sweet summer child.” Because once you have a big enough user base, once you have enough people on a platform, once the likelihood of profit becomes high enough, you’re going to have spammers.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="https://www.wired.com/story/del-harvey-twitter-trust-and-safety-breaks-her-silence/"&gt;Del Harvey&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/moderation"&gt;moderation&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/twitter"&gt;twitter&lt;/a&gt;&lt;/p&gt;



</summary><category term="moderation"/><category term="spam"/><category term="twitter"/></entry><entry><title>Tell-a-Friend: Leverage Word of Mouth Marketing</title><link href="https://simonwillison.net/2008/Sep/20/tellafriend/" rel="alternate"/><published>2008-09-20T12:00:31+00:00</published><updated>2008-09-20T12:00:31+00:00</updated><id>https://simonwillison.net/2008/Sep/20/tellafriend/</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://tellafriend.socialtwist.com/index.jsp"&gt;Tell-a-Friend: Leverage Word of Mouth Marketing&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
I’d love to know how they intend to stop this free widget from becoming the world’s most popular spam proxy. And of course, they abuse the password anti-pattern despite the existence of safe API alternatives to address book scraping.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/tellafriend"&gt;tellafriend&lt;/a&gt;&lt;/p&gt;



</summary><category term="spam"/><category term="tellafriend"/></entry><entry><title>Using Akismet with Django's new comments framework</title><link href="https://simonwillison.net/2008/Aug/28/sciyoshi/" rel="alternate"/><published>2008-08-28T10:12:25+00:00</published><updated>2008-08-28T10:12:25+00:00</updated><id>https://simonwillison.net/2008/Aug/28/sciyoshi/</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://sciyoshi.com/blog/2008/aug/27/using-akismet-djangos-new-comments-framework/"&gt;Using Akismet with Django&amp;#x27;s new comments framework&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
A nice example that demonstrates two features that were recently rolled in to the Django 1.0 betas: the new signals library and the new comments framework.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/akismet"&gt;akismet&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/comments"&gt;comments&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/django"&gt;django&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/python"&gt;python&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/signals"&gt;signals&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;&lt;/p&gt;



</summary><category term="akismet"/><category term="comments"/><category term="django"/><category term="python"/><category term="signals"/><category term="spam"/></entry><entry><title>The law behind "tell a friend" services</title><link href="https://simonwillison.net/2008/Jul/28/viral/" rel="alternate"/><published>2008-07-28T10:49:22+00:00</published><updated>2008-07-28T10:49:22+00:00</updated><id>https://simonwillison.net/2008/Jul/28/viral/</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.out-law.com/page-6590"&gt;The law behind &amp;quot;tell a friend&amp;quot; services&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Useful guide based on UK law, updated in July 2008.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/law"&gt;law&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/marketing"&gt;marketing&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/tellafriend"&gt;tellafriend&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/uklaw"&gt;uklaw&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/viralmarketing"&gt;viralmarketing&lt;/a&gt;&lt;/p&gt;



</summary><category term="law"/><category term="marketing"/><category term="spam"/><category term="tellafriend"/><category term="uklaw"/><category term="viralmarketing"/></entry><entry><title>Quoting ator_fighting_eagle</title><link href="https://simonwillison.net/2008/Jun/20/redditcom/" rel="alternate"/><published>2008-06-20T18:55:38+00:00</published><updated>2008-06-20T18:55:38+00:00</updated><id>https://simonwillison.net/2008/Jun/20/redditcom/</id><summary type="html">
    &lt;blockquote cite="http://www.reddit.com/info/6o6gp/comments/c04f37e"&gt;&lt;p&gt;This is the new blog-spam. [...] 'web design company' takes the highest ranking comment from reddit, and posts it on the site that the original comment is based on. [...] Neat eh? They get to have links on a site that won't get blog-spam filtered, because the comment is 'relevant', since the comment originates from a comment thread about the site.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="http://www.reddit.com/info/6o6gp/comments/c04f37e"&gt;ator_fighting_eagle&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/commentspam"&gt;commentspam&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/reddit"&gt;reddit&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;&lt;/p&gt;



</summary><category term="commentspam"/><category term="reddit"/><category term="spam"/></entry><entry><title>Quoting John Nagle</title><link href="https://simonwillison.net/2008/May/26/techdirt/" rel="alternate"/><published>2008-05-26T08:40:05+00:00</published><updated>2008-05-26T08:40:05+00:00</updated><id>https://simonwillison.net/2008/May/26/techdirt/</id><summary type="html">
    &lt;blockquote cite="http://techdirt.com/articles/20080523/0327151211.shtml"&gt;&lt;p&gt;Craigslist is fighting back. Its latest gimmick is phone verification. Posting in some categories now requires a callback phone call, with a password sent to the user either by voice or as an SMS message. [...] Spammers tried using their own free ringtone sites to get many users to accept the Craigslist verification call, then type in the password from the voice message. Craigslist hasn't countered that trick yet.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="http://techdirt.com/articles/20080523/0327151211.shtml"&gt;John Nagle&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/callback"&gt;callback&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/craigslist"&gt;craigslist&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/phonecall"&gt;phonecall&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/sms"&gt;sms&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;&lt;/p&gt;



</summary><category term="callback"/><category term="craigslist"/><category term="phonecall"/><category term="sms"/><category term="spam"/></entry><entry><title>OpenID and Spam</title><link href="https://simonwillison.net/2008/Apr/2/matt/" rel="alternate"/><published>2008-04-02T19:33:25+00:00</published><updated>2008-04-02T19:33:25+00:00</updated><id>https://simonwillison.net/2008/Apr/2/matt/</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://ma.tt/2008/04/openid-and-spam/"&gt;OpenID and Spam&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Matt Mullenweg: “OpenID has a ton of promise for the web—let’s not hurt it by setting people up for disappointment by telling them it’s a spam blocker when it’s not.” True for the case of general registration, but I still believe whitelisting known OpenIDs could be a powerful tool for fighting spam on personal sites.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/matt-mullenweg"&gt;matt-mullenweg&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openid"&gt;openid&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/social-whitelisting"&gt;social-whitelisting&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/whitelisting"&gt;whitelisting&lt;/a&gt;&lt;/p&gt;



</summary><category term="matt-mullenweg"/><category term="openid"/><category term="social-whitelisting"/><category term="spam"/><category term="whitelisting"/></entry><entry><title>Sorry PR people: you're blocked</title><link href="https://simonwillison.net/2007/Oct/31/long/" rel="alternate"/><published>2007-10-31T17:22:29+00:00</published><updated>2007-10-31T17:22:29+00:00</updated><id>https://simonwillison.net/2007/Oct/31/long/</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.longtail.com/the_long_tail/2007/10/sorry-pr-people.html"&gt;Sorry PR people: you&amp;#x27;re blocked&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
I was added to some PR mailing lists a few months ago and they appear to be spreading my address around like a nasty disease. I’m tempted to contribute some addresses to Chris Anderson’s block list.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/chris-anderson"&gt;chris-anderson&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/email"&gt;email&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/pr"&gt;pr&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;&lt;/p&gt;



</summary><category term="chris-anderson"/><category term="email"/><category term="pr"/><category term="spam"/></entry><entry><title>Quechup: Another Social Network Enemy!</title><link href="https://simonwillison.net/2007/Sep/21/quechup/" rel="alternate"/><published>2007-09-21T23:36:15+00:00</published><updated>2007-09-21T23:36:15+00:00</updated><id>https://simonwillison.net/2007/Sep/21/quechup/</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.oreillynet.com/xml/blog/2007/09/quechup_another_social_network.html?CMP=OTC-TY3388567169&amp;amp;ATT=Quechup Another Social Network Enemy"&gt;Quechup: Another Social Network Enemy!&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
This is why we need to stop teaching users that it’s OK to give their e-mail username and password to any site that asks for it.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/oauth"&gt;oauth&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openid"&gt;openid&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/quechup"&gt;quechup&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/social-networks"&gt;social-networks&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;&lt;/p&gt;



</summary><category term="oauth"/><category term="openid"/><category term="quechup"/><category term="social-networks"/><category term="spam"/></entry><entry><title>3rd Annual Nigerian EMail Conference</title><link href="https://simonwillison.net/2007/Jun/26/nigerian/" rel="alternate"/><published>2007-06-26T01:27:21+00:00</published><updated>2007-06-26T01:27:21+00:00</updated><id>https://simonwillison.net/2007/Jun/26/nigerian/</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://j-walk.com/other/conf/"&gt;3rd Annual Nigerian EMail Conference&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
“Registration is via a confidential money transfer.”


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/funny"&gt;funny&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;&lt;/p&gt;



</summary><category term="funny"/><category term="spam"/></entry><entry><title>Unsettling</title><link href="https://simonwillison.net/2007/Jun/5/mezzoblue/" rel="alternate"/><published>2007-06-05T21:16:58+00:00</published><updated>2007-06-05T21:16:58+00:00</updated><id>https://simonwillison.net/2007/Jun/5/mezzoblue/</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://mezzoblue.com/archives/2007/06/05/unsettling/"&gt;Unsettling&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Sounds like there might be a massive scripted hack going on against out of date WordPress installs on Dreamhost. Check your site. See also discussion in the comments attached to this post.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/dave-shea"&gt;dave-shea&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/dreamhost"&gt;dreamhost&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/hosting"&gt;hosting&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/php"&gt;php&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/security"&gt;security&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/wordpress"&gt;wordpress&lt;/a&gt;&lt;/p&gt;



</summary><category term="dave-shea"/><category term="dreamhost"/><category term="hosting"/><category term="php"/><category term="security"/><category term="spam"/><category term="wordpress"/></entry><entry><title>Introducing http:BL</title><link href="https://simonwillison.net/2007/Apr/25/httpbl/" rel="alternate"/><published>2007-04-25T23:39:55+00:00</published><updated>2007-04-25T23:39:55+00:00</updated><id>https://simonwillison.net/2007/Apr/25/httpbl/</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.projecthoneypot.org/5days_wednesday.php"&gt;Introducing http:BL&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Project Honey Pot announce a new blacklist service for blocking comment spammers and e-mail spiders using information from their network of honey pots.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="http://www.jacobian.org/reading/"&gt;Jacob Kaplan-Moss&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/blacklist"&gt;blacklist&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/commentspam"&gt;commentspam&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/honeypot"&gt;honeypot&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/security"&gt;security&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;&lt;/p&gt;



</summary><category term="blacklist"/><category term="commentspam"/><category term="honeypot"/><category term="security"/><category term="spam"/></entry><entry><title>Fading Out Nofollows?</title><link href="https://simonwillison.net/2007/Apr/15/fading/" rel="alternate"/><published>2007-04-15T20:27:16+00:00</published><updated>2007-04-15T20:27:16+00:00</updated><id>https://simonwillison.net/2007/Apr/15/fading/</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://blog.outer-court.com/archive/2007-04-15-n22.html"&gt;Fading Out Nofollows?&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Philipp Lenssen suggests automatically removing the nofollow from links in comments a few days after they have been posted, to allow administrators time to delete spam without penalising legitimate authors.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/nofollow"&gt;nofollow&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/philipp-lenssen"&gt;philipp-lenssen&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;&lt;/p&gt;



</summary><category term="nofollow"/><category term="philipp-lenssen"/><category term="spam"/></entry><entry><title>Quoting David Sifry</title><link href="https://simonwillison.net/2007/Apr/5/sifry/" rel="alternate"/><published>2007-04-05T23:39:58+00:00</published><updated>2007-04-05T23:39:58+00:00</updated><id>https://simonwillison.net/2007/Apr/5/sifry/</id><summary type="html">
    &lt;blockquote cite="http://www.sifry.com/alerts/archives/000493.html"&gt;&lt;p&gt;Thankfully, because of the accountability that is built into the web itself (the URL structure is fundamentally accountable), I believe that while the vulnerability of the live web to spam is real, it is managable.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="http://www.sifry.com/alerts/archives/000493.html"&gt;David Sifry&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/david-sifry"&gt;david-sifry&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/technorati"&gt;technorati&lt;/a&gt;&lt;/p&gt;



</summary><category term="david-sifry"/><category term="spam"/><category term="technorati"/></entry><entry><title>i'm Home</title><link href="https://simonwillison.net/2007/Mar/2/im/" rel="alternate"/><published>2007-03-02T10:43:02+00:00</published><updated>2007-03-02T10:43:02+00:00</updated><id>https://simonwillison.net/2007/Mar/2/im/</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://im.live.com/Messenger/IM/Home/"&gt;i&amp;#x27;m Home&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
“Every time you start a conversation using i’m, Microsoft shares a portion of the program’s advertising revenue with some of the world’s most effective organisations dedicated to social causes.” Microsoft are now getting their marketing ideas from spam e-mail forwards.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/funny"&gt;funny&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/im"&gt;im&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/microsoft"&gt;microsoft&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;&lt;/p&gt;



</summary><category term="funny"/><category term="im"/><category term="microsoft"/><category term="spam"/></entry><entry><title>Quoting Rick Skrenta</title><link href="https://simonwillison.net/2007/Feb/15/spam/" rel="alternate"/><published>2007-02-15T11:15:33+00:00</published><updated>2007-02-15T11:15:33+00:00</updated><id>https://simonwillison.net/2007/Feb/15/spam/</id><summary type="html">
    &lt;blockquote cite="http://www.skrenta.com/2007/02/98_spam.html"&gt;&lt;p&gt;The bright side: web spam is an evolutionary force that pushes relevance innovations such as trustrank forward. Spam created the market opportunity for Google, when Altavista succumbed in 97-98. Search startups should be praying to the spam gods for a second opportunity.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="http://www.skrenta.com/2007/02/98_spam.html"&gt;Rick Skrenta&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/google"&gt;google&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/search-engines"&gt;search-engines&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/startups"&gt;startups&lt;/a&gt;&lt;/p&gt;



</summary><category term="google"/><category term="search-engines"/><category term="spam"/><category term="startups"/></entry><entry><title>Fake bloggers soon to be "named and shamed"</title><link href="https://simonwillison.net/2007/Feb/12/fake/" rel="alternate"/><published>2007-02-12T09:35:48+00:00</published><updated>2007-02-12T09:35:48+00:00</updated><id>https://simonwillison.net/2007/Feb/12/fake/</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.timesonline.co.uk/tol/news/politics/article1361968.ece"&gt;Fake bloggers soon to be &amp;quot;named and shamed&amp;quot;&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Apparently due to a new EU directive banning companies from “falsely representing oneself as a consumer”.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="http://politics.slashdot.org/politics/07/02/12/022226.shtml"&gt;Slashdot&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/astroturfing"&gt;astroturfing&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;&lt;/p&gt;



</summary><category term="astroturfing"/><category term="spam"/></entry><entry><title>Why people hate SEO... (and why SMO is bulls$%t)</title><link href="https://simonwillison.net/2007/Feb/8/smo/" rel="alternate"/><published>2007-02-08T07:47:19+00:00</published><updated>2007-02-08T07:47:19+00:00</updated><id>https://simonwillison.net/2007/Feb/8/smo/</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.calacanis.com/2007/02/07/why-people-hate-seo-and-why-smo-is-bulls-t/"&gt;Why people hate SEO... (and why SMO is bulls$%t)&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Jason Calacanis explains SMO, or “Social Media Optimisation”—digg spamming now has its own TLA.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/jason-calacanis"&gt;jason-calacanis&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/seo"&gt;seo&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/smo"&gt;smo&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/tla"&gt;tla&lt;/a&gt;&lt;/p&gt;



</summary><category term="jason-calacanis"/><category term="seo"/><category term="smo"/><category term="spam"/><category term="tla"/></entry><entry><title>Social whitelisting with OpenID... (plasticbag.org)</title><link href="https://simonwillison.net/2007/Jan/26/social/" rel="alternate"/><published>2007-01-26T01:00:50+00:00</published><updated>2007-01-26T01:00:50+00:00</updated><id>https://simonwillison.net/2007/Jan/26/social/</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.plasticbag.org/archives/2007/01/social_whitelisting_w/#comments"&gt;Social whitelisting with OpenID... (plasticbag.org)&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Tom’s write-up of the social whitelisting idea. Lots of sceptics in the comments.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="None"&gt;plasticbag.org - a weblog by Tom Coates&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/openid"&gt;openid&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/social-whitelisting"&gt;social-whitelisting&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/tom-coates"&gt;tom-coates&lt;/a&gt;&lt;/p&gt;



</summary><category term="openid"/><category term="social-whitelisting"/><category term="spam"/><category term="tom-coates"/></entry><entry><title>Stopping spambots with hashes and honeypots</title><link href="https://simonwillison.net/2007/Jan/23/spambots/" rel="alternate"/><published>2007-01-23T13:39:15+00:00</published><updated>2007-01-23T13:39:15+00:00</updated><id>https://simonwillison.net/2007/Jan/23/spambots/</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.nedbatchelder.com/text/stopbots.html"&gt;Stopping spambots with hashes and honeypots&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Ned’s analysis of how spambots work, along with some relatively simple tricks that should fool most of them.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/commentspam"&gt;commentspam&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/hashing"&gt;hashing&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ned-batchelder"&gt;ned-batchelder&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spambots"&gt;spambots&lt;/a&gt;&lt;/p&gt;



</summary><category term="commentspam"/><category term="hashing"/><category term="ned-batchelder"/><category term="spam"/><category term="spambots"/></entry><entry><title>The Spam Farms of the Social Web</title><link href="https://simonwillison.net/2006/Nov/22/spam/" rel="alternate"/><published>2006-11-22T10:41:23+00:00</published><updated>2006-11-22T10:41:23+00:00</updated><id>https://simonwillison.net/2006/Nov/22/spam/</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.niallkennedy.com/blog/archives/2006/11/spam-farms-social-web.html"&gt;The Spam Farms of the Social Web&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Really interesting exposé by Niall Kennedy.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/niall-kennedy"&gt;niall-kennedy&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;&lt;/p&gt;



</summary><category term="niall-kennedy"/><category term="spam"/></entry><entry><title>Hacked for Spam</title><link href="https://simonwillison.net/2003/Dec/9/hackedForSpam/" rel="alternate"/><published>2003-12-09T02:56:42+00:00</published><updated>2003-12-09T02:56:42+00:00</updated><id>https://simonwillison.net/2003/Dec/9/hackedForSpam/</id><summary type="html">
    &lt;p&gt;From the &lt;a href="http://www.nytimes.com/2003/12/08/technology/08trojan.html?ex=1386219600&amp;amp;en=fc2a920c196b88ca&amp;amp;ei=5007&amp;amp;partner=USERLAND" title="Hackers Steal From Pirates, to No Good End"&gt;New York Times&lt;/a&gt;:&lt;/p&gt;

&lt;blockquote cite="http://www.nytimes.com/2003/12/08/technology/08trojan.html?ex=1386219600&amp;amp;en=fc2a920c196b88ca&amp;amp;ei=5007&amp;amp;partner=USERLAND"&gt;
&lt;p&gt;Computer security researchers have been watching the evolution of remote-access rogue programs as they have become more common and have put more machines under the control of hackers. Programs like Sinit infect target machines and surreptitiously open back doors that allow outsiders to control the PC's. The rings of infected computers have been used to send spam, to present online advertisements for pornographic Web sites or to trick people into giving up information like credit card numbers.&lt;/p&gt;

&lt;p&gt;In fact, &lt;em&gt;at least a third of all spam circulating on the Internet is now sent from or relayed by personal home computers that have been taken over&lt;/em&gt;, said Jesse Dougherty, director of development at Sophos, an antivirus and antispam company. &lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Emphasis mine. Of course, whether or not you want to believe a director from a company that directly profits from people's fear of security attacks is up to you. That said, I've seen plenty of supporting evidence in the past few months that indicates that spamming is now the number one reason that a cracker would want to take over a &lt;acronym title="Personal Computer"&gt;PC&lt;/acronym&gt;, not least &lt;a href="http://www.wired.com/news/business/0,1367,60747,00.html" title="Cloaking Device Made for Spammers"&gt;this Wired article&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Continuing on the same theme, &lt;a href="http://www.securityfocus.com/guest/24043"&gt;The Rise of the Spammers&lt;/a&gt; is a fascinating article by David Barroso Berrueta describing how one of his servers was turned in to a spam relay after being compromised through a vulnerability in a &lt;acronym title="PHP: Hypertext Preprocessor"&gt;PHP&lt;/acronym&gt; script. The technical details are intriguing; the attacker downloaded and uncompressed a daemon which then communicated with another host using an extended version of the &lt;acronym title="Simple Mail Transfer Protocol"&gt;SMTP&lt;/acronym&gt; protocol, receiving spam email bodies along with lists of addresses to send the spam on to.&lt;/p&gt;

&lt;p&gt;Let's talk about the &lt;acronym title="PHP: Hypertext Preprocessor"&gt;PHP&lt;/acronym&gt; vulnerability in question: yet again, it was the classic problem where an attacker can instruct &lt;acronym title="PHP: Hypertext Preprocessor"&gt;PHP&lt;/acronym&gt; to download and execute code from their own server by feeding in a query string parameter that is passed un-checked to an &lt;code class="php"&gt;include()&lt;/code&gt; function call. While there are a number of steps that can be taken to deny this kind of attack, it unveils a fundamental problem with &lt;acronym title="PHP: Hypertext Preprocessor"&gt;PHP&lt;/acronym&gt; itself - that it will execute code retrieved from a &lt;acronym title="Uniform Republic of Love"&gt;URL&lt;/acronym&gt; in the first place! This feature should be removed from &lt;acronym title="PHP: Hypertext Preprocessor"&gt;PHP&lt;/acronym&gt; - it has almost no purpose in the real world aside from allowing servers to be cracked in to. The feature exists because &lt;acronym title="PHP: Hypertext Preprocessor"&gt;PHP&lt;/acronym&gt; has the extremely useful ability to &lt;a href="http://www.php.net/manual/en/features.remote-files.php"&gt;open remote files over HTTP&lt;/a&gt;. Unfortunately, this feature extends to the &lt;code class="php"&gt;include()&lt;/code&gt; and &lt;code class="php"&gt;require()&lt;/code&gt; functions which will execute any &lt;acronym title="PHP: Hypertext Preprocessor"&gt;PHP&lt;/acronym&gt; code in the file passed to the functions. The most obvious solution to my mind would be for these functions to refuse to execute &lt;acronym title="PHP: Hypertext Preprocessor"&gt;PHP&lt;/acronym&gt; in files that were opened via &lt;acronym title="HyperText Transfer Protocol"&gt;HTTP&lt;/acronym&gt;. I have no doubt that this would involve an ugly hack on behalf of &lt;acronym title="PHP: Hypertext Preprocessor"&gt;PHP&lt;/acronym&gt;'s maintainers, but I believe the number of security problems it would solve would be well worth the trade-off.&lt;/p&gt;

&lt;p&gt;Incidentally, I &lt;em&gt;know&lt;/em&gt; you can &lt;a href="http://us4.php.net/manual/en/install.configure.php#install.configure.disable-url-fopen-wrapper"&gt;disable opening files over HTTP&lt;/a&gt; and I &lt;em&gt;know&lt;/em&gt; you shouldnt allow the direct creation of variables from the query string in the first place. The problems here are two-fold: firstly, opening files over &lt;acronym title="HyperText Transfer Protocol"&gt;HTTP&lt;/acronym&gt; is actually a very useful feature, one that would be all the more useful if it didn't carry the risk of executing arbitrary code. Secondly, the problem is mainly down to third party software which often requires insecure &lt;acronym title="PHP: Hypertext Preprocessor"&gt;PHP&lt;/acronym&gt; settings (such as register_globals) in order to work.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/security"&gt;security&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="security"/><category term="spam"/></entry><entry><title>New anti-comment-spam measure</title><link href="https://simonwillison.net/2003/Oct/13/linkRedirects/" rel="alternate"/><published>2003-10-13T08:22:09+00:00</published><updated>2003-10-13T08:22:09+00:00</updated><id>https://simonwillison.net/2003/Oct/13/linkRedirects/</id><summary type="html">
    &lt;p&gt;I've added a new anti-comment-spam measure to this site. The majority of comment spam exists for one reason and one reason only to increase the Google PageRank of the site linked from the spam and specifically to increase its ranking for the term used in the link. This is why so many comment spams include links like this: &lt;a href="http://jeremy.zawodny.com/blog/archives/001002.html"&gt;Cheap Viagra&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Cut off the PageRank boost and you cut off the advantage of spamming, simple as that. I've altered my comments system to redirect ALL outgoing links through a simple redirect script, and added that script to &lt;a href="/robots.txt"&gt;my robots.txt file&lt;/a&gt;. Links still work fine (even the referral information persists across the redirect) but Google will ignore them completely when calculating PageRank.&lt;/p&gt;

&lt;p&gt;Will this reduce the floods of comment spam my site receives? Probably not; I've added a note about the restriction to my 'add comment' form but I doubt many spammers bother to read much about the sites they are targetting. What's really needed is for this technique to become widespread by being integrated in to existing blogging tools - are you listening Moveable Type hackers?&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Update:&lt;/strong&gt; Sencer has &lt;a href="http://www.sencer.de/index.php?p=81" title="Google Comment Spammers, Redirects and PR"&gt;pointed out&lt;/a&gt; in the comments that PageRank persists over redirects, and Google appears to ignore robots.txt when used to hide a redirecting page. I've updated my redirection script to use javascript to power the redirect (with a link for people with javascript disabled) and an extra meta tag to remind Google not to follow the link. This has the unfortunate side effect that referral information no longer persists across the redirect.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/projects"&gt;projects&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/robots-txt"&gt;robots-txt&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/site-upgrades"&gt;site-upgrades&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="projects"/><category term="robots-txt"/><category term="spam"/><category term="site-upgrades"/></entry><entry><title>Battling comment spam</title><link href="https://simonwillison.net/2003/Sep/30/moreCommentSpam/" rel="alternate"/><published>2003-09-30T13:34:15+00:00</published><updated>2003-09-30T13:34:15+00:00</updated><id>https://simonwillison.net/2003/Sep/30/moreCommentSpam/</id><summary type="html">
    &lt;p&gt;It's a sad state of affairs when you come back to your blog after a week elsewhere and have to add another 56 domains to your &lt;a href="http://simon.incutio.com/blacklist.txt"&gt;blacklist&lt;/a&gt;. I'm actually getting more comment spam than legitimate comments now - this is becoming more than just a minor nuisance. I'm considering a number of improvements, including adding a moderation queue to comments on entries posted more than a month ago, disabling the comment form if the referral is a search engine (as per &lt;a href="/2003/Aug/28/googleComments/"&gt;Russell Beattie's suggestion&lt;/a&gt;) and adding some kind of wildcard support to the blacklist file.&lt;/p&gt;

&lt;p&gt;I'd really rather not do any of this, but the problem looks like it's going to escalate.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/moderation"&gt;moderation&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="moderation"/><category term="spam"/></entry><entry><title>Fighting Filters and DDoS</title><link href="https://simonwillison.net/2003/Sep/2/fightingFilters/" rel="alternate"/><published>2003-09-02T00:55:15+00:00</published><updated>2003-09-02T00:55:15+00:00</updated><id>https://simonwillison.net/2003/Sep/2/fightingFilters/</id><summary type="html">
    &lt;p&gt;Paul Graham's essays on fighting spam are generally excellent; it was Paul who sparked the recent flurry of activity surrounding Bayesian statistical filters and inspired the creation of some of the best tools for fighting spam yet. Paul's latest suggestion, &lt;a href="http://www.paulgraham.com/ffb.html"&gt;Filters that fight back&lt;/a&gt;, seems to me to miss the mark in a &lt;em&gt;big&lt;/em&gt; way. Paul suggests email servers should "follow" links in any email received. This would turn the tables on spam, as suddenly sending out a million spams would result in a million useless hits to the site being promoted, quickly brining it to its knees. It's a great concept, until some malicious script kiddie realises that they've been handed a tool to run massive distributed denial-of-service attacks on any domain they care to target. Not to mention that such a feature would make many legitimate mass email tools prohibitively expensive to run.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Update:&lt;/strong&gt; It turns out that this issue has already been discussed in the &lt;a href="http://www.paulgraham.com/ffbfaq.html"&gt;FAQ&lt;/a&gt; attached to the essay. The suggested solution is to use a blacklist, with servers only hitting sites that are linked to from an email &lt;em&gt;and&lt;/em&gt; listed on the blacklist.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/denial-of-service"&gt;denial-of-service&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/paul-graham"&gt;paul-graham&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="denial-of-service"/><category term="paul-graham"/><category term="spam"/></entry><entry><title>Spam proof email</title><link href="https://simonwillison.net/2002/Jul/4/spamProofEmail/" rel="alternate"/><published>2002-07-04T15:58:01+00:00</published><updated>2002-07-04T15:58:01+00:00</updated><id>https://simonwillison.net/2002/Jul/4/spamProofEmail/</id><summary type="html">
    &lt;p&gt;Today saw a useful thread on &lt;a href="http://www.webdesign-l.com/"&gt;Webdesign-L&lt;/a&gt; about hiding email addresses from spambots. Some of the points raised:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Javascript encryption makes addresses inacessible to anyoen with javascript disabled, not just spambots.&lt;/li&gt;
&lt;li&gt;Form based solutions help avoid ever exposing your address to the open web.&lt;/li&gt;
&lt;li&gt;An english description (mail cs1spw at bath dot ac dot uk) is a good solution, but may eventually be parsed by spambots as well.&lt;/li&gt;
&lt;li&gt;If you go down the javascript encryption route, adding an english description in &amp;lt;noscript&amp;gt; tags can make your address more accessible.&lt;/li&gt;
&lt;li&gt;An image showing your email address is spambot proof, but does not solve the problem of how to hide addresses that can be clicked on.&lt;/li&gt;
&lt;li&gt;A lot of users with webmail do not benefit from mailto: addresses anyway, and would prefer a form.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I have restructured my &lt;a href="/~cs1spw/blog/contact/"&gt;contact page&lt;/a&gt; to take these in to account.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/spam"&gt;spam&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="spam"/></entry></feed>