Using nntprss To Archive Blog Content

A week or two ago, I sung the praises of nntprss, a RSS aggregator-as-NNTP-server. I’ve been using it heavily since that article, and it really has been doing the trick. However, there’s been an interesting side effect here as well.
nntprss has an option for treating RSS feeds as “historical” – thus saving posts if the related item is removed from the RSS feed. It also leaves the original post alone if an item has been edited. So how is this useful?
It’s been hard to miss the fight about Echo. What is essentially turning into Nerd Wars, we have the Trotts, Sam Ruby, and a handful of others on the “Echo is good” side, while Dave Winer and Dave’s followers are on the “Why reinvent the wheel?” side. Edit: I had originally lumped Don Park in with the Dave side, but as he pointed out in my comments, he (and many others) are sitting in a sort of middle position.
So how’s this been useful? Well, a lot of people commit blog edits (especially Dave Winer), and there’s usually no way to track this effectively, outside of praying for a Google cache or someone quoting the portion that gets changed. But nntprss catches it well. For instance: Mark Pilgrimwrote about leaving RSS alone, because otherwise people are “shoehorning”. This is obviously a shot fired at the Dave camp, so of course Dave has posted about it. This is the first article I see (Dave’s posts go to people.blogceleb.winer, just for reference; I’m stripping a few headers) – boldface for the part you should watch for:

Twenty minutes later, this article appears:

Granted, the ability to detect changes is often limited by excerpt size, but most of the time you can catch things like this.
So again, high recommendations for nntprss; everyone should set up their own install and enjoy.