Comment by ChrisArchitect 4 months ago [dupe] Earlier: https://news.ycombinator.com/item?id=46987559 2 comments ChrisArchitect Reply zahlman 4 months ago This is additional context for the incident and should not be treated like a duplicate. dang 4 months ago Yes, with a fast-moving story like this we usually point the readers of the latest thread to the previous thread(s) in the sequence rather than merging them. I've added a link to https://news.ycombinator.com/item?id=46987559 to the toptext now.
zahlman 4 months ago This is additional context for the incident and should not be treated like a duplicate. dang 4 months ago Yes, with a fast-moving story like this we usually point the readers of the latest thread to the previous thread(s) in the sequence rather than merging them. I've added a link to https://news.ycombinator.com/item?id=46987559 to the toptext now.
dang 4 months ago Yes, with a fast-moving story like this we usually point the readers of the latest thread to the previous thread(s) in the sequence rather than merging them. I've added a link to https://news.ycombinator.com/item?id=46987559 to the toptext now.
This is additional context for the incident and should not be treated like a duplicate.
Yes, with a fast-moving story like this we usually point the readers of the latest thread to the previous thread(s) in the sequence rather than merging them. I've added a link to https://news.ycombinator.com/item?id=46987559 to the toptext now.