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?

  • @breadsmasherEnglish
    3•1 year ago

    Its an issue with how timestamps are stored in the DB vs presented in the front end

  • [email protected]
    3•1 year ago

    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