-
-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Posted x ago
section in comments is incorrect for new comments
#141
Comments
on local servers it's even more wonky, on my local test it says 3 hours. i think it's because on the database side the date is stored as whatever timezone the server's in, but on the local side it reads it as UTC or something |
But the thing is even like that, the time will be incorrect if we count difference between timezones |
hm right i gotcha, hmm, gotta think abot that some more |
Why not implement it in JavaScript |
it is https://github.com/Osekai/osekai/blob/main/global/js/comment_system.js#L143 the issue i think at this point is the server is sending a time in UTC+1, but then the code is interpreting it as simply UTC so it thinks it's posted an hour in the future. shouldn't be too impossible to fix |
If the server always sending a time in UTC+1, you can use the |
the better way to do it is to just store dates in UTC instead. |
ic😅 |
this is fixed... temporarily... |
If new comment is created, it will say it was posted
59 minutes ago
, when it's actually not true, and tooltip shows actual post time (in GMT)The text was updated successfully, but these errors were encountered: