3 ms·

A lot of this could be solved by inferring the time zone by location of the appointment. If you know the event occurs in a specific place at a specific time, yo

A lot of this could be solved by inferring the time zone by location of the appointment. If you know the event occurs in a specific place at a specific time, you almost certainly want it to be the standard time zone of that place. If that place uses DST, I couldn’t think of any reason to ignore it and opt for standard time regardless. Bonus: geopolitics change country lines, and that affects time zones as well. When the time zone at the appointment location changes due to border conflicts, you can get the new time zone without having to change anything.

toast0 4y ago
That works if you know the location of the appointment. But if you're going to a bar to watch a televised game with friends, the location in the appointment is probably the bar, but the timezone is wherever the game is held. If you're going to have a conference call and you have a shared calendar system, great everybody should agree; if all the participants have separate calendar systems, maybe you discuss the time to have the call and each enter it in your local time, which works fine until someone's government adjusts local time on short notice. Having separate appointments sounds fragile, but have you had a good experience with cross domain calendaring? I certainly haven't. Never mind, if you had a fully booked schedule collaborating across timezones and someone's government adjusts local time, now you've got a mess.