Obviously things have happened to this site. Let me just mention the most important here — the rest you can figure out for yourselves.

First of all, there’s a new kid on the blog. Allow me to introduce Steffen (his profile will return 404 until he publishes something), whom many of you already know. I’ve been hoping to have him join this blog for a long time now, but my old blogging software wasn’t rigged for it. I’ve finally gotten over myself and installed a standard platform, which I’ll get into in a second, but first: Welcome to the blog Steffen, I hope you’ll like it here.

Now, this new standard platform I mentioned, is (as you may have guessed) WordPress. At first I was a bit hesitant to move to such a platform, but with the ability to easily write plugins, widgets, modify templates and stuff, there’s really no reason not to. Setting up WP was a breeze and the migration from my old system to the new was a matter of 2 really simple PHP scripts — one for converting the old entries and one for the comments. A million thumbs up to the WP developers for making something so accessible, simple and easy.

Apart from a new blogger and a new platform, other things have changed a bit around here. When migrating to WP, there were some decisions to be made. One of those were whether or not to move stuff like phpCF and DynDNSupdate to the new site and I ended up deciding that DynDNSupdate wasn’t worth moving, since I haven’t coded on it for years (and I don’t intend to ever again) and it didn’t appear to be all that popular anyways. So DynDNSupdate is gone. phpCF survived though, mainly because I still code on it every now and then (and I have some huge improvements planned) and because it actually has a future (where DynDNSupdate only had a past — not even a present).

Now, no migration of this sort is without problems and I’ve tried my best to make sure that no old links are broken and stuff, but should you encounter any problems, let me know.

On a side note, the site isn’t the only thing that has had an overhaul (1 and 2).

I was just looking through my logfiles (I tend to do that whenever I get a bit tired, but don’t go to sleep) and I realized that the number of spam attempts has decreased heavilly. From blocking more than 30 attempts a day, all the way down to 52 attempts throughout June and no attempts at all in August or September. Same goes for blacklist redirects (ie. blacklisted hosts being redirected to a customized 404 page saying that they’ve been blacklisted.)

I’m not quite sure what to make of this, because there are a couple of things involved and the decrease started just as I made some big changes to my anti-spam system. The following are some possible factors in the decrease and there may very well be some I’m overlooking.

I started returning 404 Not Found on blacklist redirects instead of 200 OK

Are the spammers running some kind of automated learning, so once they receive a 404, they stop trying? That would be weird, because in order to even see the before mentioned 404, they have to make at least 3 attempts at spamming. So automated learning would be indicated by a vast amount of blocked attempts compared to the number of blacklist redirects, which is not the case here - both numbers have decreased heavilly, though the number of blacklist redirects varies from zero to 5-6 a day.

phpCF is working great

If the spammers are in some way measuring their success-rate, then it must mean that phpCF is working great, because no spam has gotten through in a long time. But this would also be strange, because how would they measure the success-rate? Googling? I think not.

The blacklist is complete

I’ve finally blacklisted each and every spam-bot on the planet! Yay, for me! :-p
Actually, this would explain the small number of blocked attempts compared to the larger amount of blacklist redirects. But still, somehow I don’t believe that this is the reason.

More options

Last, but not least, there may be outside factors causing the decrease (even though I’d like to think that I came up with the “cure for the cancer”). Maybe Google-bombing has gotten harder, or the spammers are getting more cautious - or maybe blog-spamming just isn’t profitable enough…

… and then there is all the stuff I can’t think up right now because it’s 8:46 AM and I haven’t slept yet. If you have any ideas, experiences, thoughts … anything! Please, post a comment or drop me a mail. I’d be more than happy to know what you think.

… and then I pulled myself together and released phpCF 0.2 into the wild. You may be wondering why you never saw a 0.1 release, but that’s because it was never released. But tonight I gave it the final work-over, wrote some documentation for it and - thanks to Steffie - decided NOT to write a DB configuration backend for it anyway, so now it runs with a single, very simple configuration file. Way better than a big, clumsy and useless configuration in a database. (There are more reasons, but I won’t get into them now.)

In case you’re wondering what phpCF is, then you’ve chosen the right paragraph to read. phpCF is a PHP class designed for scanning of e.g. blog-comments to determine whether they’re spam or not. phpCF only does the checking, assigns a score and compares it to the configured threshold. What to do if it’s spam is up to the one implementing it. Apart from doing a simple job in a simple way it’s also simple to implement. Simple, simple, simple… SIMPLE! Look at this example…

Also, I created a Freshmeat entry for phpCF and I hope that the server can stand the extra traffic, when phpCF hits the Freshmeat front page. If not, let me know.

Creativity both on the coding front and the artistic front.

First of all, I’ve been receiving a lot of comment spam lately - so I thought I’d revamp my spam checking system (I just counted the number of links before; if it was > 5, then the comment was blocked and the IP logged for potential blacklisting). The new system I’ve been hacking a little on is way more flexible and extensible - so it’ll be a lot easier to fight off spam later, if they find yet another way to spam me. If this turns out to be a success I might release it under the GPL, but I want to test it a little before deciding on it.

Secondly, I’ve been playing more with my tablet and now it works perfectly with Linux. Turned out that kernels 2.6.4 through 2.6.8 had some issues, so after upgrading to kernel 2.6.11 and recompiling mousedev.ko, evdev.ko and wacom.ko I finally got it working. (Thanks to the docs at the Linux Wacom Project and furrywolf from #debian.) So if you’re considering buying a tablet I can recommend the Wacom Volito (if you’re a beginner) - it’s cheap and it’s relatively easy to get working with Linux - just like the other Wacom tablets. Look them up on eBay - you can probably get a used one very cheap.

Oh yeah, bumped into this sign here in Århus - I can’t remember whether it was a hair dresser or some kind of shop. Also, take a look at this cake we made for a friends birthday.