On mobile, the lines connecting the avatar to the link and the expand/collapse nodes have been removed, which looks strange. I can’t figure out the corresponding relationships at all.
did the view as flat button go missing? 
2개의 좋아요
It’s behind a group site setting now (hidden). It’s staff-only by default. The idea is end users shouldn’t be thinking in nested vs flat mode.
3개의 좋아요
yes but now i am getting notifications for this topic and i can’t find the latest post it refers to (or more likely i am not doing it properly lol).
3개의 좋아요
It is the nature of non-linear discussion.
There is a reason Discourse went with the flat one first, as Threaded discussion is ultimately too complex to survive on the public Internet? - #2 by codinghorror 
5개의 좋아요
We are missing a “Parent post” link indeed.
2개의 좋아요
Hmm… I don’t see a Flat view toggle now?
1개의 좋아요
It’s not missing the “Parent post” I don’t think.. when you’re deeplinked to a post it shows the parent as well. I believe the issue is mainly the consolidation of “replied” notifications. They get lumped together as N new replies and only link to the lastest reply, so the N-1 are super hard to find. Really need to think of a solution there. I’d love to not mess with our notification system.
Maybe we could append a query param to notification URLs for nested view and have a “step through” system for watched topics or something. cc @Lilly
1개의 좋아요
But in HN or Reddit, I can keep clicking on “Parent” to go all the way until I can grasp the context of that branch. I’ve used this flow many times when getting a notification on Reddit.
But consolidation doesn’t happen to direct replies right? Only watching and likes right?
3개의 좋아요
i just realized i can’t filter for my posts from my user card in this topic. 
just to reiterate - i love that you folks added this as a feature option and i can’t wait to use it on my forum (hoping soon). i have an use case that fits well as a way to test it.
2개의 좋아요
I still don’t understand though, I clicked on the notification for your post, and see all the parent nodes up to the root 
.
Good question, not sure. probably?
1개의 좋아요
I guess it is only a problem after 10 levels deep, where you won’t get all the context?
1개의 좋아요
We actually have a “view parent context” link for this case. We are about hit it with this conversation hehe. I believe we should be covered here. Not that the UX is perfect by any means, but I think we have this functionality fundamentally.
2개의 좋아요
the UX is working quite well i think. it just takes some getting used to when switching out of flat context topics. the experience is definitely getting better the more i use it and get the hang of navigating the topic. i think in a proper use case scenario, the nested commenting and different visual format will be much easier to follow. fantastic work Team, this is really impressive. 
4개의 좋아요
I’m seeing a notification of 7 unread messages in this topic, but no way to find where they are or to visit them. Even sorting by new doesn’t help.
So, the concept of new unreads might need adjusting, or the method of sorting by new.
11개의 좋아요
Yes, totally agree. You’re not at all wrong.
4개의 좋아요
I spent several minutes until I understood I had to scroll and expand multi-nested replies to see the actual new content.
I’m glad the nested topics view feels right for some people and communities. I wouldn’t engage in meaningful discussions on any platform using this layout (in this current state, which has at first glance no major differences with reddit?). 
3개의 좋아요
The two places I see this kind of nesting are Reddit and Hacker News - in both cases they allow folding (collapsing, hiding) - and in both cases my way of using them is to wait a decent interval before reading a thread. (If too early, I may miss wisdom.) I never revisit anything. And I never contribute.
2개의 좋아요