Post age shown wrong

[PaMu1337]

There seems to be something wrong with the time settings of the website. All post times ("posted x minutes ago") are showing as 33 minutes more than they actually are. Immediately after posting something, it says the post is 33 minutes old.

Picture of this post immediately after posting:

 

[Famine]

There seems to be something wrong with the time settings of the website. All post times ("posted x minutes ago") are showing as 33 minutes more than they actually are. Immediately after posting something, it says the post is 33 minutes old.

Picture of this post immediately after posting:
View attachment 1475717

Post in thread 'Posting from the future: how exactly does this happen?'

May 20, 2025

That's correct, the "relative" timestamps are just calculated by comparing your system's time with the server's timestamp on the post. There is no queue.

I'm not seeing any issue with the server's time, so the issue would have to be caused by a system time or browser issue. If your system's time is correct, future timestamps can still be caused by caching bugs in the browser which should be fixed by refreshing the page.

• Jordan

 

[PaMu1337]

My system time is correct though. Refreshing doesn't help. Actually when I refresh the page, it shows correctly for a second, and then adds 33 minutes.
When I load the site in a private tab, it does show correctly though. It looks like the site is caching some things it shouldn't be caching.

 

[Famine]

When I load the site in a private tab, it does show correctly though.

If it doesn't occur in private mode it firmly suggests that it's a browser issue as noted by @Jordan in his post. Have you tried a force cache refresh with Ctrl+F5?

Edit: Is that a yes or a no? I can't tell.

 

[PaMu1337]

If it doesn't occur in private mode it firmly suggests that it's a browser issue as noted by @Jordan in his post. Have you tried a force cache refresh with Ctrl+F5?

It actually very firmly suggests that the website itself is caching something. Private mode just doesn't allow the website to access any info it stored. The fact that it reports fine in private mode and other websites shows that the browser is reporting its time correctly, and the issue is in the cached info from the website itself.

Edit: after a while it started showing correctly again

 

[Liquid]

Something similar frequently happens to me, definitely on mobile Firefox, unsure about desktop Firefox, but I'd been unable to prove it until now.

Joey's post is twenty-four minutes further in the past according to his post's timestamp. Note the time in the top left.