News for hackers. Stuff that matters.
Re:RFC 3339 vs. ISO 8601 by crooked-v on Thursday August 31, 2023 @05:28PM (#37343913)
What about storing current geo coordinates and a timestamp of when they were recorded? I feel like that should be enough for a theoretical future system to adjust mapping for continental drift.
Re:RFC 3339 vs. ISO 8601 by joshspankit on Thursday August 31, 2023 @05:41PM (#37344041)
Especially assuming an increase in computing intelligence in that time.
Re:RFC 3339 vs. ISO 8601 by ethbr1 on Thursday August 31, 2023 @10:33PM (#37346113)
The problem with geo coordinates is reverse mapping them back into political owners, so you can then determine current timezone policy.

There's 4 things at play here:

   - Coordinate location on the planet
   - Identifier for that location
   - Political entity for that location
   - Current timezone policy
Of those, coordinates are the only thing that doesn't change over time (for the spans we're talking about).

But are also a pain in the ass to use. F.ex. I'm sure someone on HN has the lat long for London memorized, but I don't.

Re:RFC 3339 vs. ISO 8601 by dmurray on Friday September 01, 2023 @03:29AM (#37347789)
London is perhaps the only major city where you could be expected to know one of these coordinates. It's defined to have longitude 0.
Re:RFC 3339 vs. ISO 8601 by c4mpute on Friday September 01, 2023 @06:52AM (#37349097)
I suggest giving date and time in the form of phase/frequency references to nearby pulsars. That should guarantee stability for a few million years.