Just 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 locatedtimezoneoffset 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()
So just for additional context: This meme was brought to you by the following API response scheme: json { "time": "2007-12-24 18:12", "servertimezone": "Europe/Vienna", "timezoneoffset": -8 } when it could have just been json { "date": "2007-12-24T18:21:00-07:00" }
If you use utc here and a time zone definition changes, you’re bonedI'm pretty sure that things like the tz database exist exactly for such a case.
As far as I can tell it's the other ways around: IPv4 is getting more costlyExample: AWS started to charge for IPv4 addresses a few months ago - a IPv4 address now costs around $3.6 per month
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()