Well, I’m not writing yet (as was my intention on getting up) but after eating breakfast and having some cola, I found the ambition to perform a couple of administrative tasks on my network.
One of them turned out to be incredibly simple. I complained the other day about comment spam. I decided to do some looking around and found a way nifty solution by Chrissy LeMaire. She created a wonderful SQL script that you copy, paste, and run. It creates a trigger, which in database terminology means a process that the server runs automatically when a pre-set condition happens. In this case, when someone submits a comment or trackback link, her script gets run to analyze it and determine if it is spam or not.
You can get Chrissy’s code here, if you’re a .Text user. Thank you, Chrissy!
This is an extremely elegant method of handling the problem, because the solution lies entirely in the database, not in the .Text code. It doesn’t change any of the existing data tables, so the data that is there will be the way CS expects to see it when it’s time to upgrade. And it’s not one of those dumb-ass “captcha” solutions that displaysa distored graphic and requires you to enter in the code. As it turns out, captcha solutions aren’t being as useful as people hoped, since .Text exposes the MetablogAPI so that other web programs and web services can submit posts and comments and the captcha solutions don’t protect this method.