> Tree-style comments are not the best format for every type of discussion.
I've found that they work well for discussions where there are several subtopics. Under what scenerio would this format not be considered the best format?
I've found that they work well for discussions where there are several subtopics. Under what scenerio would this format not be considered the best format?
The lifespan of a Reddit/HN submission is basically a day. Past that point and it's unlikely anyone will even read your comment.
In such cases, a traditional forum's bumping system lets you pick up timeless conversations for new people to take part of. So many times an archived Reddit thread will show up in Google results and it's sad that I can't contribute to the discussion nor will anyone read it if I could.
In more traditional forums (e.g. VBB) one effectively replicates the tree format through quoting - just without the tree being so clearly displayed.
E.g. showing every comment linearly with time, but each comment that has replies also has a "show replies" link which expands when clicked to show the replies as children. Those replies are the same comments shown later in the linear list; it's just a convenient alternate way of showing them on request in context.
* See all news messages since the last time. I could see all the threads, news messages were marked in bold. * Cycle through them, i.e. show me next unread. * Make whole threads as read (when the topic is not interesting to me) * Ignore a thread or subthread (when it's going offtopic or completely uninteresting to me)
And it was also super easy to filter out idiots, without anyone moderating the stuff.
That's one thing I've found lacking in practically any single forum out there. IMO, client side moderation is the best kind of moderation. That said, it can be daunting to a newcomer if the signal-to-noise ratio of a group is rather low due to numerous trolls, cross-posters, etc and they don't have their killfile set up yet.
The other is that trees make it harder to keep up with ongoing discussions as you can no logner just continue reading from where the thread was at when you last visited. Reddit actually has an OK solution for that which highlights new comments since your last visit(s) but it is only available to moderators or paid users.
Another possible solution would be a better notification system - with forums you can typically watch a thread to get notifications for any posts but with Reddit you only get notfications for direct comments to your post/comment.
One example might be a non-trivial tech support problem, where forum members work together to solve an issue. As the user tries solutions and posts their progress, the initial post isn't as valuable as the latest one. Other examples would include threads with real-time reactions to events, like a sporting event or political debate, or threads that are longer-running, like telling a story that unfolds over time.
But most longer running discussions will splinter into subtopics. If the discussion is short enough, the way it's displayed doesn't really matter either way.
> Other examples would include threads with real-time reactions to events, like a sporting event or political debate
I think the line between a mostly synchronous chat and an asynchronous discussion forum as been blurred a bit. In chat, it's a lot easier to follow a discussion as it's happening because you can read the messages as they come in and only pay attention to the ones you're interested in. But trying to read the log after the fact is a bit more time consuming because you have to search for the relevant messages amongst many.
In a threaded and asynchronous discussion, it's easier to go down a subthread to follow a particular discussion than it is to find that discussion mixed in with all the other posts.
That said, I find it interesting that email clients have moved towards displaying messages in a conversation view, yet newer chat clients like Slack are introducing threaded discussiion as a feature.