The Threaded discussion as a visual design pattern

Actuallly HN's threaded forum is the best I've come across yet. It's simple and easy to understand yet very flexible and works well for conversations with many threads because the interesting stuff rises to the top.

It drives me nuts when I visit popular blogs that serve as a place for discussion <i>and yet they have no nesting of comments</i> (three levels does <i>not</i> count). Forcing the linearity of comments does a big disservice to the readers, because inevitably people will go off into tangential conversations where #45 will reply to #15 and #79 will reply to #45. A lot of (but not all) people make up their own informal structure by prefixing their comments with the name or the number of the comment(er) they're replying to. I feel like I'm in the Stone Age when browsing through these conversations after reading through HN. We already have solutions for this crap!<p>Very few websites seem to be getting this right, and I can't understand why. Someone or something needs to force these people to evolve.<p>I would love to see a piece of software that analyzed a linear comment stream, inferred the dependencies, and restructured the comments in the browser. Is there anything like this?

HN distills some of the best ideas from its predecessors:<p>1) Scoring system for stories (Digg) and comments (Slashdot)<p>2) Community based story submission (Kuro5hin)<p>3) Infinite indentation (Usenet and Forums)<p>It's also interesting to note what they didn't include in the design: Subjects for comments<p>HN's approach is not without challenges<p>1) Following the conversation gets tougher when there are a lot of levels. Who said what?<p>2) By reordering the posts according to points the user gets disoriented.

This is an interesting and under-discussed topic (especially among designers), but there isn't a huge amount of insight in the article.<p>Could anyone point out some good resources on threaded discussion design?