3 ms·

> It’s not just DST, it’s any TZ-related changes: locations can change TZ fir other reasons than dst. Exactly, and for that time zone info will not be enough,

> It’s not just DST, it’s any TZ-related changes: locations can change TZ fir other reasons than dst. Exactly, and for that time zone info will not be enough, you would need geographic coordinates.

deleted 5y ago
[deleted]
spacemanmatt 5y ago
To be more accurate you should also store relative velocity so the Lorentz transformation can be applied at display time
scatters 5y ago
Geographic coordinates can change as well (earthquakes; office moves). But that's why the tzdb uses major/dominant city names.
- samwillis 5y ago
  Issue with that is borders move, and with that time zones. So you may be in the “Europe/London” time zone now. But the north of England could annex itself and create a new time zone “Europe/Manchester”…
  - ycombobreaker 5y ago
    In the great schism of England, the meeting organizer fled to central Europe, and one of the primary stakeholders died. The meeting had to be rescheduled.
  - masklinn 5y ago
    A more realistic issue is that Scotland currently doesn’t have an entry in the tzdb.
layer8 5y ago
Depends on what you mean by time zone info. A time zone identifier like "Europe/Paris" will usually be sufficient.
- kalleboo 5y ago
  Time zone identifiers are created once an area stops matching the previously best-matched identifier. Like right now maybe all of France uses Europe/Paris, but if southern France decides to secede and change their timezone by an hour, they would all have to re-configure from Europe/Paris to Europe/Toulouse. The existence of a bunch of currently seemingly-redundant time zone identifiers are a testament to the history of this. So the only 100% future-proof solution is geographical coordinates that can be looked up in a continually-updated database.
  - layer8 5y ago
    > geographical coordinates So, what do you do for a remote meeting with participants in different places? You’d have to decide on one location. Specifying Paris when you are really in Toulouse isn’t much different. Yes, your meeting is now bound to Paris time, but at least it remains consistent with that. Furthermore, having had to work with call routing based on geolocation, I can tell you that geo coordinates aren’t always enough, due to inaccurate zip code and area code divisions and other factors.

deleted 5y ago

[deleted]

spacemanmatt 5y ago

To be more accurate you should also store relative velocity so the Lorentz transformation can be applied at display time

scatters 5y ago

Geographic coordinates can change as well (earthquakes; office moves). But that's why the tzdb uses major/dominant city names.

samwillis 5y ago
Issue with that is borders move, and with that time zones. So you may be in the “Europe/London” time zone now. But the north of England could annex itself and create a new time zone “Europe/Manchester”…
- ycombobreaker 5y ago
  In the great schism of England, the meeting organizer fled to central Europe, and one of the primary stakeholders died. The meeting had to be rescheduled.
- masklinn 5y ago
  A more realistic issue is that Scotland currently doesn’t have an entry in the tzdb.

layer8 5y ago

Depends on what you mean by time zone info. A time zone identifier like "Europe/Paris" will usually be sufficient.

kalleboo 5y ago
Time zone identifiers are created once an area stops matching the previously best-matched identifier. Like right now maybe all of France uses Europe/Paris, but if southern France decides to secede and change their timezone by an hour, they would all have to re-configure from Europe/Paris to Europe/Toulouse. The existence of a bunch of currently seemingly-redundant time zone identifiers are a testament to the history of this. So the only 100% future-proof solution is geographical coordinates that can be looked up in a continually-updated database.
- layer8 5y ago
  > geographical coordinates So, what do you do for a remote meeting with participants in different places? You’d have to decide on one location. Specifying Paris when you are really in Toulouse isn’t much different. Yes, your meeting is now bound to Paris time, but at least it remains consistent with that. Furthermore, having had to work with call routing based on geolocation, I can tell you that geo coordinates aren’t always enough, due to inaccurate zip code and area code divisions and other factors.