Do you thread comments on your startup?
spoiledtechie.com
spoiledtechie.com
Threaded/Linear have their pros and cons.
To have threaded comments, it means you are limiting the user to explicitly reply to one comment. As an aside, it's possible to make one comment be a reply to many, and then creating some really neat conversation graph out of it, but that's just so complicated. I think we can all agree that threading is the ability to reply to one comment, and create a tree structure of comments.
Threaded comments create a tree of conversation; it's highly structured. Nearly as important as your post is where in the thread it goes. You lose the option to post something more general, or something that references several other posts. The importance in threaded conversations is the structure and not chronology.
Linear comments is all about chronology. The conversation evolves over time, and you lose the structure. It's flat. If you want to reply to someone, you're just quoting then. By the way, a linear commenting system without quoting, in my opinion, is the lowest form of commenting. It almost angers me to see it being used, anywhere.
Nearly all forums use non-threaded, and it seems to work out great! It's more of a community builder -- let's all join this conversation as it passes through time.
Threaded conversations have the problem of becoming highly specific very quickly. But, they allow the structure to be clearly visible. Also, threaded conversations don't allow you to dig for what you want as easily. You'll never be able to order a tree-like structure in any meaningful way unless you flatten it.
The conclusion I ultimately reached was always use threaded, because if you're smart about it, threaded implies linear as well. You can always flatten a tree -- the data is there. But it's much harder to take a linear set of comments and imply which is a child of which based on quoted text. In short, you can go from threaded to non-threaded, but not vice versa.
So, I allow my users to view the conversation as a thread, with very smooth features, like instantly sorting children of any post by Date, Username, or Score. And, coming soon, I'm going to allow a non-threaded view. It will just flatten the tree and show posts, in any order they choose, date, score, username, etc. If the post is a "reply" then I just annote: "In reply to [link]summary of replied post[/link]"
One major issue with threading is scalability. What happens when you have 500 comments in one giant tree? Which do you show? How do you prune the tree? Do you show that gem of a comment that has a depth of 8? Do you hide it's siblings or parents? It really becomes a lot of trouble... and the solution seems to be: "ajax it in."
-sam
I've been experimenting with a tree-like layout which doesn't have that problem (although it may have other problems). It's no where near completion, but here's an example with data pulled from a reddit thread:
Disqus is very easy to integrate with your design, has a fantastic feature set, Facebook connect and great development team.
Some issues are that it won't integrate with your accounts (obviously) and it can be quite slow sometimes.
I believe if they were going to do something controversial (eg, close down / remove big features) they'd let us know in advance.
They need me far more than I need them.
So on the site, there are two "commentesque" systems. There's one for the general critiques (the focus of my site), which don't get threaded because they're grouped by the user that made them. There's no discussion in those comments, or there's not much. The focus is on constructive, objective feedback.
For the forum, we decided to go almost entirely minimal. A screenshot from the alpha can be found here: http://tinypic.com/view.php?pic=f18vb&s=5
The idea is that we wanted to focus on back-and-forth talk. The three of us in that thread all knew each other on an older site of mine, so that's already established, but we want a feel of community. As in, instead of lurkers and posters, you've got a place where if you're new, you can talk to older users and become sort-of welcomed into things. You lose that with threads, because suddenly it's all-too-easy for a user to get completely ignored if they don't join one of the bigger threads.
And, you're right, if you don't join a popular thread in a threaded comment system, you will probably be ignored. But you won't if you're one of the first to post in that page, thus somehow making the oldest more relevant, and if you get lots of replies your comment will be seen by more people, which makes sense to me since it would be a hot topic.
There is no perfect commenting system, I guess, but the big flaw in linear conversations is that replies are not emphasized and the relations between comments is easily lost. It would be useful when time is relevant.
I would prefer a threaded system, sorted by rating as well, kind of what Reddit or HN has: the hottest, top-rated, most recent comments on the top; the oldest, lowest-rated, not-replied-to ones more likely to be ignored.
"The current standard for any interaction is the comments section of the sites. The comment section is the talk back, the conversation to the site. It is what allows for user participation and what most people would declare what Web 2.0 really is."
This kind of status-quo talk makes me simultaneously angry and sleepy.