Hacker News Reader

I'm writing my own blog engine after Posterous' announcement. The way it works is that I create a static site which is upload somewhere, and it also publishes the post on Facebook and Twitter. Discussion happens there, on the social networks, and on the next build the comments are downloaded and stored in static files. This way when Facebook dies all the discussions will remain on the static site -- for good or bad. :-P

I wrote chronicle which handles this via a CGI. Comments are dumped into text-files and they are included in the rebuild.

That means there is a lag and a rebuild needed to publish them, but it works for me & my blog:

http://blog.steve.org.uk/

If you are a Ruby person, you could go with Juvia: https://github.com/phusion/juvia

I never used it though, as I decided against comments (and am using other tools now).

It's easy to add Disqus. But if you think you don't own comments in Disqus, it is a problem.