Well, it's quite a common bug in distributed systems to have mismatching timestamps because different server machines which tagged different elements had different clock times.

Hopefully the time stamp of a post isn't done at the user machine level (or using data from it, such as stuff from HTTP headers) as those are far more likely to be misconfigured.

The only way I see for this be a Memmy bug is if there are two timestamp fields (a user one and a server one) and the user one is being picked up (I can only think of a separate user timestamp making sense for data manipulations on the user's own machine of the user's own posts).

[–] sgriff@lemmy.ml 2 points 2 years ago (1 children)

AFAIK this is an issue with Lemmy and nothing we can control (though i could be wrong)

[–] Scooter411@lemmy.ml 1 points 2 years ago

Makes sense - I just wanted to bring it to your attention just in case.

[–] FlihpFlorp@lemm.ee 1 points 2 years ago (1 children)

I’m on the test flight version and apparently some major portion of code was rewritten so I’m sure it just a display bug

[–] Scooter411@lemmy.ml 1 points 2 years ago (1 children)

Test flight users myself.

I actually now believe this is just a duplication issue on Lemmy’s part as I’ve seen the same comment pop up elsewhere….

[–] FlihpFlorp@lemm.ee 1 points 2 years ago

Weird

load more comments