3 ms·
Thanks. It's always a puzzle what to do with threads based on articles that have since been superseded by later developments. Do we start a new thread based on
by dang 2y ago
Thanks. It's always a puzzle what to do with threads based on articles that have since been superseded by later developments. Do we start a new thread based on a new article? The new article / thread usually fails to do very well, partly because there just was a big discussion, and partly because hearing about something getting fixed is less interesting and exciting than the original stimulus.
I've been playing recently with putting [fixed] at the end of the original title to indicate this sort of state change to the reader. Not sure if that's the best way, nor if the situation has genuinely been fixed or not, but I guess it's better than nothing. Swapping out the article and title would probably be too much of a rug pull on the existing thread.
- dang 2y agoPrevious examples of this for anyone curious: NIH.gov DNS servers down, making PubMed, BLAST, etc. unreachable [fixed] - https://news.ycombinator.com/item?id=43229201 https://news.ycombinator.com/item?id=43229201 - March 2025 (385 comments) Mozilla site down due to "overdue hosting payments" [fixed] - https://news.ycombinator.com/item?id=43226089 https://news.ycombinator.com/item?id=43226089 - March 2025 (102 comments) Ask HN: Stripe Atlas messed up my 83B election what do I do? [fixed] - https://news.ycombinator.com/item?id=40825802 https://news.ycombinator.com/item?id=40825802 - June 2024 (3 comments)
- ethbr1 2y agoMaybe [updated] as a more neutral term to indicate post-submission change?
- dang 2y agoOk! Updated above.