carrylex@lemmy.world to Programmer Humor@programming.dev · 4 months agoImplementing RFC 3339 shouldn't really be that hard...lemmy.worldimagemessage-square62fedilinkarrow-up1659file-text
arrow-up1659imageImplementing RFC 3339 shouldn't really be that hard...lemmy.worldcarrylex@lemmy.world to Programmer Humor@programming.dev · 4 months agomessage-square62fedilinkfile-text
minus-squaregjoel@programming.devlinkfedilinkarrow-up8·4 months agoTo be fair, returning the actual timezone (as defined by tz.db) is useful if you don’t just want the current time since you’ll be able to take DST into account. Not sure how Vienna is -8 though, it should be +1 (or 2 depending on DST).
minus-squarecarrylex@lemmy.worldOPlinkfedilinkarrow-up3·edit-24 months agoJust for further clarification, the API works like this: time is the local (client) time (in this case UTC-7) servertimezone is the time zone where the server is located timezoneoffset is the offset of the local time relative to the servertimezone (offset from the servers PoV) To get the UTC date you have to do something like this: time.minusHours(timezoneoffset).atZone(servertimezone).toUTC()
To be fair, returning the actual timezone (as defined by tz.db) is useful if you don’t just want the current time since you’ll be able to take DST into account. Not sure how Vienna is -8 though, it should be +1 (or 2 depending on DST).
Just for further clarification, the API works like this:
timeis the local (client) time (in this case UTC-7)servertimezoneis the time zone where the server is locatedtimezoneoffsetis the offset of the local time relative to the servertimezone (offset from the servers PoV)To get the UTC date you have to do something like this:
time.minusHours(timezoneoffset).atZone(servertimezone).toUTC()