http://peteg.org/blog en http://peteg.org/blog/2007/01/28#2007-01-28-writeback /noise/blogging/writeback <p> I got a few doses of blog clap, and being bored and idle I put some effort into tidying up <a href="http://blosxom.ookee.com/blog/">Blosxom</a>'s venerable <code>writeback</code> plugin and adding <a href="http://captchas.net/">Captcha</a> support. (I don't believe in the centralised blacklisting epitomised by <a href="http://akismet.com/">akismet</a>, it's too readily abused.) I get the impression that somebody in <code>ee</code> land is manually spamming, so I might need a plan B. My other concern is that the <a href="http://captchas.net/">Captcha</a> times out, meaning that if you take longer than a day to go from page load to post-comment it will bugger you up. Also the interaction with the back button is less than ideal. </p> <ul> <li><a href="http://peteg.org/static/99writeback">99writeback</a> (plugin)</li> <li><a href="http://peteg.org/static/writeback">writeback</a> (flavour file for writebacks)</li> <li><a href="http://peteg.org/static/writebacksform">writebacksform</a> (flavour file for the writeback form)</li> </ul> <p> You'll need to instruct <a href="http://www.cpan.org/">CPAN</a> to <code>install Authen::Captcha</code> (or use your package manager to do it for you, or remove those bits of code). It should be easy to adapt it to use another <a href="http://captchas.net/">Captcha</a> library. I'm thinking about constructing a logic-puzzle one. </p> <p> Part way through I realised just how fragile <a href="http://blosxom.ookee.com/blog/">Blosxom</a> is (no non-word characters in directory names? &mdash; and I was going to call this <em>writeback++</em>!) and how badly coded most plugins are (let's do everything ourselves! date functions, interpolation, file-backed databases, ...). If my <a href="http://www.perl.org/">perl</a> was more fluent I'd have a shot at linting it all. </p>