The blogspam code is live.
Living dangerously I switched DNS to point to the new codebase on my lunch hour.
I found some problems immediately; but nothing terribly severe. Certainly nothing that didn't wait until I'd finished work to attend to.
I've spent an hour or so documenting the new API this evening, and now I'm just going to keep an eye on things over the next few days.
The code is faster, definitely. The load is significantly lower than it would have been under the old codebase - although it isn't a fair comparison:
- I'm using redis to store IP-blacklists, which expire after 48 hours. Not the filesystem.
- The plugins are nice and asynchronous now.
- I've not yet coded a "bayasian filter", but looking at the user-supplied options that's the plugin that everybody seems to want to disable. So I'm in no rush.
The old XML-RPC API is still present, but now it just proxies to the JSON-version, which is a cute hack. How long it stays alive is an open question, but at least a year I guess.
God knows what my wordpress developer details are. I suspect its not worth my updating the wordpress plugin, since nobody ever seemed to love it.
These days the consumers of the API seem to be, in rough order of popularity:
There are few toy-users, like my own blog, and a few other similar small blogs. All told since lunchtime I've had hits from 189 distinct sources, the majority of which don't identify themselves. (Tempted to not process their requests in the future, but I don't think I can make such a change now without pissing off the world. Oops.)
PS. Those ~200 users? rejected 12,000 spam comments since this afternoon. That's cool, huh?