> I lose track of the which comment corresponds to which parent Me too, here at HN. When I'm reading on my phone, looking at reply R to a parent post P somewh

> I lose track of the which comment corresponds to which parent Me too, here at HN. When I'm reading on my phone, looking at reply R to a parent post P somewhere far above, and I want to re-read P — then I place my finger to the left on the screen, at the current indentation depth, and scroll up up up, past the even-more-indented-replies above ... until the indentation depth becomes 1 step less than my finger. Then I've found the parent comment :- ) Problem is, how do I find the reply R again. And, sometimes I accidentally move my finger, losing track of both R and P. In Talkyard, one can instead click the arrows to jump to the parent, and the Back to jump back to the reply R — here's a demo about that: https://www.talkyard.io/-32/how-hacker-news-can-be-improved-3-things https://www.talkyard.io/-32/how-hacker-news-can-be-improved-... If you want to try this yourself, go here: https://www.talkyard.io/-71#post-16 https://www.talkyard.io/-71#post-16 then click the long arrow to the left, then click Back at the bottom of the screen. > unfold level 1 replies for the first comment, while keeping level 2 hidden Something like that, yes. At the same time, since popular / "good" replies are sorted first, I think it can make sense to unfold a few of the level 2 replies, for the topmost level 1 replies — so one needs to click fewer times, to read the "most interesting" things. But these are minor details; I agree with the overall idea. > Rather for myself, but as an account setting Ok. There're also custom user groups — so a site admin could configure this setting for the Everyone group, and then one could override it, individually. \* * * >> what things lag the most > Mostly animations [...] Ok, thanks for the detailed feedback. I think the code is doing things too much sequentially — like, first loading any draft — an X * 100 ms round trip to the server. Then scrolling the post one replies to into view, Y * 100 ms, then scrolling the preview into view, Z * 100 ms (so both are visible at the same time, if possible). — If instead everything happened at once, it'd seem more instant. (Also, there're editor Javascript:s that JIT-compiles and runs the first time one opens the editor.)