{ "attachments": [], "comments_archived": true, "date": "2002-09-23T01:39:58.000Z", "layout": "post", "title": "Per-post comment RSS feeds", "wordpress_id": 265, "wordpress_slug": "ooobio", "wordpress_url": "http://www.decafbad.com/blog/?p=265", "year": "2002", "month": "09", "day": "22", "isDir": true, "slug": "ooobio", "type": "entry", "postName": "2002-09-22-ooobio", "html": "

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.

\n

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.

\n

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.

\n

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.

\n\n\n\n

shortname=ooobio

\n

Archived Comments

\n\n\n\n
\n\n\n", "body": "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.\r\n

\r\nI 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.\r\n

\r\nIf 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.\r\n

\r\nAt 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.\r\n\r\nshortname=ooobio\r\n\r\n
\r\n

Archived Comments

\r\n \r\n \r\n \r\n
\r\n ", "parentPath": "./content/posts/archives/2002/2002-09-22-ooobio", "path": "2002/09/22/ooobio", "thumbnail": "http://www.decafbad.com/images/xml.gif", "summary": "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.\nI 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.\nIf 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.\nAt 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.", "needsBuild": true, "prevPostPath": "2002/09/21/ooobhi", "prevPostTitle": "Running Classic from a disk image?", "nextPostPath": "2002/09/23/ooobia", "nextPostTitle": "Pingback one-ups TrackBack" }