Unfortunately, when submissions get put back into a "2nd chance queue", the "elapsed time calc" is modified to be more recent -- which causes confusion. The thread that's given "new life" for more engagement now has a mix of real and fake "x hours ago".
If you're on a desktop browser instead of a smartphone, you can use F12 Dev Tools to inspect the parent post[1] elements to see that the original timestamp is still there as "2024-12-26T05:23:25 1735190605" ... which is actually about 4 days ago.
Some search engines (bing) still has a cache of this thread we're in from 4 days ago.
It says "9 hours ago" to me. Is this one of those situations where HN reposted the post and the comments as well? I wish the date and time were kept accurate instead of being confusingly changed.
If you're on a desktop browser instead of a smartphone, you can use F12 Dev Tools to inspect the parent post[1] elements to see that the original timestamp is still there as "2024-12-26T05:23:25 1735190605" ... which is actually about 4 days ago.
Some search engines (bing) still has a cache of this thread we're in from 4 days ago.
https://imgur.com/a/example-hacker-news-thread-put-back-into...
If one were to click on that 4 day old thread, you come here where all the comments are "x hours ago". It's confusing.
[1] https://news.ycombinator.com/item?id=42546687