leighelse, 10 months ago

@robert_p_king I’ve done a lot of this over the years, and the best approach in my experience is to

[a] use an actively maintained third party time zone library,

[b] convert all timestamps to UTC and store them as that, and

[c] convert back to the user-selected time zone for display.

Of course, just because it’s proved best for me doesn’t mean it’ll be perfect for you, but it worked for me on multiple projects.

aligorith, 10 months ago

@robert_p_king
That's why we're on UTC only... it helps also that NZ is +12 most of the year (or "+12, + 1" otherwise)... it'd be much tougher for folks in the +4 to +11 band 😜

jond, 10 months ago

@robert_p_king Oooff, this reminds me of trying to establish and run overlapping rosters for five regional teams to provide 24/7/365 follow-the-sun cover in my old telco role. I wonder what happened to HTMLCal (which I think is what I used)...