Per-post comment RSS feeds
After following the thread on Sam Ruby's blog about Dave's comment tracking feature request, I figured I'd try RSS-izing comments on each of my posts. As things seem to have been going lately, I'd underestimated MovableType, and it turned out so much easier than I'd thought. :) I'd had an RSS feed for comments overall on my site, but now I have individual RSS feeds for each post. (Notice the
in the comments section now.) The RSS feed is also linked in the head as per RSS autodiscovery discussions.
I don't think aggregators are really ready yet for these per-post comment RSS feeds, but the availability of the data gives food for hacking. Being that they're pretty disposable and of interest for a very short time, aggregators will likely need to implement expiry times for feeds, or watch for a period of inactivity before unsubbing. Grouing feeds would be nice too, in case I wanted to round up all my points of weblog discussion participation. I've got a few things of this sort in my AmphetaOutlinesWishList, with which I hope to play with further aggregator ideas.
If you use MovableType and you're interested in trying this, check out these two templates: recent_comments_rss.xml.tmpl, for blog-wide comments; and archive_entry.rss.tmpl, for per-post comments. The former template is added as an index template in MovableType, whereas the latter is an archive template. Also, the per-post archive template will need to be added to the list of individual archive templates in the Archiving section of your blog config. You'll want to give it a template for the filename, perhaps something like <$MTEntryID pad="1"$>.rss.
At present, I'm publishing in what I think is vaguely RSS 0.92 format. Whether it complies with the spec, I'm not quite sure because I was lazy. I plan to revisit this soon to make it at least comply with RSS 1.0. ShareAndEnjoy.
shortname=ooobio
Archived Comments
I implemented per-thread feeds (rather than per-user feeds, for some perverse reason) in the Python Community Server a while back, but have found that they weren't really that useful.
Some poor aggregator has been faithfully downloading http://www.pycs.net/system/comments.py?u=0000003&p=69&format=rss 20 times a day for months, despite the fact that it has never contained any items. Aggregators need to have exponential backoff times or something.
BTW, I have a script to make RSS feeds from RCS comments. At http://dev.myelin.co.nz/commentmonitor/tracker.py you can generate an RSS feed for anybody on radio.weblogs.com, blogs.salon.com or www.pycs.net.
Phillip: Yeah, I'd definitely like to see some more smarts in the polling frequency of aggregators. Got a little blurb about that on my AmphetaOutlinesWishList. Maybe a combo of manual preferences and automatic back-off would be a start.