News for hackers. Stuff that matters.
Re:How not to replace email: lessons from Google Wave by jimmies on Sunday February 18, 2018 @06:05AM (#16405489)
I think it does something unusual on deeply nested comments. It simply discourages deeply nested comments because they are usually unuseful except for the two participants.
Re:How not to replace email: lessons from Google Wave by u801e on Sunday February 18, 2018 @11:21AM (#16406714)
> I think it does something unusual on deeply nested comments.

IIRC, HN does roughly the same thing that reddit does for deeply nested comments (meaning that you have to click on a link to view more of the thread). The most deeply nested thread I was involved in [1] on HN didn't appear to be handled any differently than any other thread I've seen here.

[1] https://news.ycombinator.com/item?id=13632352

Re:How not to replace email: lessons from Google Wave by detaro on Sunday February 18, 2018 @11:23AM (#16406730)
It (temporarily?) hides the "reply" link after some depth, so you have to click the timestamp to go to the comment permalink instead and reply there.
Re:How not to replace email: lessons from Google Wave by pbhjpbhj on Sunday February 18, 2018 @11:56AM (#16406894)
Is that a function of nesting, I thought it was rapidity of responses -- to try to inhibit back-and-forth arguing.
Re:How not to replace email: lessons from Google Wave by u801e on Sunday February 18, 2018 @04:02PM (#16408611)
I have seen this happen if I try to reply soon after a post appears, but I don't recall it happening in the nested thread that I linked to.
Re:How not to replace email: lessons from Google Wave by rainbowmverse on Sunday February 18, 2018 @11:40AM (#16406805)
For example: your comment had no reply link, but the one above did.