jerry, The fedia servers were, for some reason, set to use CEST. I changed the timezone to UTC yesterday.
hitstun, (edited ) I thought that was going to fix it, but I'm afraid it's still happening. I just posted to my Fedia magazine and a Lemmy community and Lemmy thinks they were posted 2 hours from now. I wonder what else it could be? Another Lemmy bug?
Edit: Another Fedia user posted after me and now they're the top of Lemmy's "new" sort with a post 2 hours from now.
hitstun, Mastodon doesn't seem to have this problem. It gets correct timestamps for my actions.
chris, I strongly suspect it's a timezone bug in kbin. fedia.io is hosted in Germany (I think) which will be GMT+2, which would explain the two hours difference if it isn't converting back to GMT/UTC on the timestamps. Does this happen on kbin.social too? That would help determine if it's a kbin bug or just configuration on fedia.io.
e569668, (edited ) This makes the most sense to me, might need @jerry to confirm if the server running this has a timestamp in the future (compared to UTC), but either way sounds possible kbin isn't stripping timezones on payloads
Edit: it seems there is an issue at least on Lemmy's side for this https://github.com/LemmyNet/lemmy/pull/3496 as posted about in https://fedia.io/m/fedia/t/115620
jerry, both servers (app and database) are set to the correct time and to the UTC time zone.
hitstun, Hi there! I'm Hitstun and I've been reposting all the content from /r/FloatingIsFun into @FloatingIsFun , as everyone's probably seen. This bug is driving Lemmy users crazy because all of my threads and posts appear to come from two hours into the future, making them stick at the top of /all for two hours, even if they only have one upvote. Am I configured incorrectly? I'm in US Eastern Daylight Time and it's currently 9:38am here.
e569668, Am I configured incorrectly?
It's not a you thing, my posts also show up 2 hours into the future
Add comment