My quest for a loosely-coupled comment system has led me to the same conclusion Dave Winer reached a while ago: Use WordPress. Rather than cross-posting to my WordPress comments blog, though, I'd like to use it as a kind of a web service that I can integrate into my existing blog. And I'd like to do that as portably as I can, so that the glue can be repurposed for any blog publishing system I might switch to, as well as for any other comment service I might switch to.
I haven't created the glue yet, I'm just doing things manually in order to think through what the glue needs to do. So far I've identified these functions:
jonsradiocomments.wordpress.com/2006/09/24/a1529/That might not be straightforward, though. In this example, the original WordPress URL was something like:
jonsradiocomments.wordpress.com/2006/09/24/how-translucency-could...The descriptive trailing part of the URL, called the post slug, is derived automatically from the title. You can change it interactively, and I did, but that's a nonstandard feature and so isn't supported in any of the weblog APIs. I might instead have to embed the serial number in the title.
It seems mostly straightforward, but I thought I'd review the plan here in case anyone's been there and done that and has advice to pass along.
By the way, I'm not completely comfortable with the idea of freeloading on WordPress in this way. As I mentioned before, I'd pay a small monthly fee for a blog-independent service that's designed equally well for interactive administration of comments and programmatic integration into my blog. That offer still stands.
Former URL: http://weblog.infoworld.com/udell/2006/09/25.html#a1530