It is really snappy and nice, however I still don't understand why there isn't nested threads. It's such a pain trying to navigate around trying to figure out what is in reply to what.
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.
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.
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.
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?
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.