Hacker News Reader

Comment by tipiirai | Hacker News Reader

Moot has a concept of "paths" which allow you to setup unlimited discussion hierarchies. All parent paths contain all the moots from the children.

We're putting together more docs to help cover these concepts soon!

Single thread (which we call a moot) doesn't support threading. If you try to browse bigger threads here in HN or in Reddit you'll soon realize that you'll get lost. Especially when you come back to the site it's impossible to know what has changed. We think discussions should be chronological.

Later we're adding support for replying to replies (one level only) and a way to branch from the main topic.

View on HN

> If you try to browse bigger threads here in HN or in Reddit you'll soon realize that you'll get lost.

That never happens to me, especially on reddit, where threads are collapsible. How do you end up lost?

> Especially when you come back to the site it's impossible to know what has changed.

No it's not. There's a reddit gold feature for that.

You end up lost when you see there's a new reply on a thread you've been following (post count is 67 but yesterday it was 66) and then you go trying to find it for about five minutes. You end up re-reading about 30% of all the posts until you finally find what you were looking for. Repeat until you've read the entire thread 20 times.

But that's not a bad experience compared to when you go read a threaded conversation for the first time when there's over 50 posts — the whole thing is just unreadable. Add to this that even the most technical people can rarely reply to the right post 100% of the time.

The reddit gold feature I mentioned directly addresses what your first paragraph describes. New comments since your last visit are highlighted.

And I don't understand your second paragraph; it never happens to me, but that doesn't mean it's not a problem. Could you help me understand why you find these threads unreadable? Do you make use of the "collapse thread" button?

It's not about being lost, it's about not being able to read bigger threads.

The answer is no-thread.

I have yet to look at the features you provide, in detail; however, am I the only one who thinks that the word "moot" is the opposite of what you're trying to achieve? Why would anyone moot anything if they're trying to converse?

Also, your embedding option looks lot more similar to branch.com which I think is strugglig to make a space.

Reply on news.ycombinator.com