Comment spam continues to plague us

Despite the wonderful MT-Blacklist (and I finally managed to update to 1.63 beta RC2) this morning there was some comment spam waiting for me. Keeping the blacklist up-to-date is very important, and I've done so (and this prevented another 5 or so other spams from getting trough) - but since it's updated by a human, it will always take some time to react.

Incidentally, MovableType 3.0 is on the horizon and they seem to have solved the problem, in a way anyway, and I'd like to hear our readers opinions on the solution. They have implemented a system called TypeKey - let me explain this to you briefly. Basically, it's a registration system - so in the future you would be required to register before being able to comment on this blog. It's not as bad as it sounds though - you would be registering with TypeKey, not with D/k (and I would never get your personal details unless you allow it), and with one registration you would be able to comment on all blogs that use TypeKey authentication. In practice this would mean that when you comment for the first time, I would need to authorise you as a poster before the comment would appear, and all future posts would automatically come trough.

So, people who make comments on this blog, how would that sound to you? I really want to keep commenting as easy as possible, but I really despise spam and I'd like to keep it to the minimum if at all possible. If I added TypeKey autentication to commenting, would you still continue to comment?

(Incidentally, due to an issue with the previous version of MT-Blacklist, trackback pings haven't been working and I only now realised this - if you have pinged us in the past, it hasn't registered. It's working now though in case you want to re-ping us.)

You can't add any more comments, but if you wish you can email the author.