4 ms·
Hang on... My comment was not made "hours ago". It was made 3 days (2026-08-29) before this post reached the front page. You can hover over the "hours ago" lin
by rvz 2mo ago
Hang on... My comment was not made "hours ago". It was made 3 days (2026-08-29) before this post reached the front page.
You can hover over the "hours ago" link and the timestamp does not match the title.
Why is the timestamp of my comment (and many others) of this post manipulated? Was this post recently merged with another duplicate?
- embedding-shape 2mo ago"second-chance" pool or the "repost invited" pool. Seems it's not on https://news.ycombinator.com/invited https://news.ycombinator.com/invited so "second-chance" seems to be what happened. Introduced a mere 5 years ago :) https://news.ycombinator.com/item?id=26998308 https://news.ycombinator.com/item?id=26998308 Interesting you've been here at least since then and haven't noticed it before, happens relatively often, dare I say at least once a day?
- senordevnyc 2mo agoYeah, but that's different from what they're talking about. It looks like the code for comment timestamps has a bug where the human-readable version keys off the updated story timestamp or something?
- embedding-shape 2mo agoNo, what happens when an old submission goes through that invited/second-chance process is that any comments made on the submission would have their timestamps updated, so comments I left days ago, could show up as being made hours/minutes ago, although I didn't personally repost them. Exactly what parent describes. I'm guessing HN either by choice or by accident shows the "original timestamp" in that title attribute, while the user-facing rendering shows the newly bumped timestamp.
- lapetitejort 2mo agoI didn't know about it until one of my submissions was chosen as a second chance. Just one of the many features that old-timers have to pass on to the new blood