@John-1 kind of like reddit but instead you can collapse at each layer. i have not seen anyone other than reddit do this, if only reddit wasnt so slow and like i said allowed collapsing the replies at each layer so you can keep things organized and focused.
@John-1 the way it currently functions is fine but why do i need to see a reply a second time in the thread, the first time was when i expanded the reply by clicking on it and the second time when i found it in the thread. i would rather only see it once. i think reddit comes closest to how our brains work. im surprised something hasnt come out already satisfying this niche
i could be wrong but redundancy is not a good thing in terms of workflow efficiency. i mean if the second time i saw the reply it was an iteration of the original that would be cool, i know a radical idea, just brainstorming out loud
@John-1 Thanks for your thoughts.
We discussed this approach many many times over the years, but it comes down to a matter of technical limitation. We designed NodeBB from the start to be linear in format, and so in order to support a threaded model, that would require a significant rework of how we manage the pids in a topic.
That's not to say that it would never happen, but at currently, we feel the approach of exposing one layer of direct replies to be a sufficient workaround.
Keep in mind if we supported both linear and threaded formats, it would essentially double the code and quadruple the complexity. That in and of itself is a reason not to do it 
@John-1 i know users can ignore threading and reply to something on the same layer instead of using the sublayer to reply. who cares its related to the original post. as long as we have the option to thread all the way down it takes load off the higher layers even if not completely, it at least attempts to keep things organized. i plan on pursuing such a project but its nodebb's speed and stability making me want to use it as a base
