This post was apparently posted at 11:08 GMT+2, which is almost two hours in the future from now.
This is obviously a bug, but is it a frontend or a backend issue?
Post date is in the future
This post was apparently posted at 11:08 GMT+2, which is almost two hours in the future from now.
This is obviously a bug, but is it a frontend or a backend issue?
4 Comments
WtfEvenIsExistence@lemmy.ca · 15 pts · 3y
cactusupyourbutt@lemmy.world · 1 pts · 3y
might also be a timezone issue
nicman24@kbin.social · 7 pts · 3y
we now know your time zone
breadsmasher@lemmy.world · 3 pts · 3y
Its an issue with how timestamps are stored in the DB vs presented in the front end
A10@kerala.party · 3 pts · 3y
I had this issue when I start Lemmy docker compose up using an ssh session. But doesn't happen when I use Ansible to deploy the docker compose file. I think devs are aware of this and a fix is already merged