# Introducing nested replies **URL:** \ **Category:** Announcements\ **Tags:** nested-replies\ **Created:** [May 12, 2026, 11:21pm UTC](https://meta.discourse.org/t/introducing-nested-replies/402812 "2026-05-12T23:21:22Z")\ **Posts on this page:** 1\ **Showing post:** 69
**Author:** ![markvanlan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/markvanlan/32/160087_2.png) [@markvanlan](https://meta.discourse.org/u/markvanlan)\ **Post date:** [July 24, 2026, 2:48am UTC](https://meta.discourse.org/t/introducing-nested-replies/402812/69 "2026-07-24T02:48:31Z")
> [@JonahAragon1](#): > > - It would be nice if I collapse a thread, it’d stay collapsed when I reopen the topic in the future Might be nice.. probably not that easy to implement.. I’ll keep it in the back of my mind. > [@JonahAragon1](#): > > - It’d also be nice if new replies since the last time I opened the topic were highlighted As you noted in your next post, we have the little dot that disappears as you scroll them into view. This is a great idea though, to make it more prominent for nested replies. Noice. > [@JonahAragon1](#): > > - I wish the “X new replies” button was always visible, stickied to the top of the page like where the “sort by” selector is, instead of only when I scroll all the way up to the top. Yep great idea > [@JonahAragon1](#): > > - Opening a topic navigates to a seemingly random part of the topic? It shouldn’t, this could be a bug.. or you’re going forward and backwards and forgetting where you are. For nested replies I implemented aggressive model caching so you can go forward/backwards and the scroll position and what is open/collapsed is all still exactly as it was. I think the cache lasts for 10 topic views so it’s possible you revisited, loaded the cache and expected to be back at the top instead of where you were? > [@JonahAragon1](#): > > - Even when clicking browser notifications about new replies, sometimes new replies don’t appear until I refresh the page. I think this is especially (only?) the case if I click a notification from the topic when I have the topic open. Interesting, will look into this. > [@JonahAragon1](#): > > Currently the main problem I have is just that this is still too buggy to use I’m surprised to hear this. We have some pretty large communities using nested replies now, and I haven’t heard this before. Will keep an eye on it though > [@JonahAragon1](#): > > maybe there could be an option for New to sort the threads by the newest _reply_ in the topic rather than newest top-level thread > > Indeed, most common feedback I’ve seen on my forum is that nested replies makes following a post live near-impossible: I get where you’re going with this, but lets say the chain is 10 levels deep, and the levels all go deep.. sorting by that won’t add any value if the discussion keeps going on in a super deeply nested convo. Unless in this new mode, we autoload the absolute newest threads all the way down to the newest content. I like the idea but not sure about how we would do it. > [@JonahAragon1](#): > > > [@markvanlan](#): > > > > The two paradigms are very different and users shouldn’t be interacting so differently on the same content. > > Honestly I do not follow this argument > [@JonahAragon1](#): > > Okay, now I’ve posted thrice so I’ll stop replying here for now. Ahh I appreciate all the feedback and really liked seeing your forum where you and your users were talking about the feature. A very cool thing to see out in the wild. You’re almost convincing me that it should be an option. I’ll kick it around internally. * * * I know I didn’t respond to everything you wrote, but it’s all heard. Thanks for testing, talking to your users and giving the feedback over here. Much appreciated 🤜 🤛 . If you find any solid repros for bugginess send it over here. --- _[View the full topic](https://meta.discourse.org/t/introducing-nested-replies/402812)._