> If you want to represent a point in a calendar, use local timezone.
And actually, going back to the original comment, this part was covered by the article. Storing timezone doesn't cover the case of a location switching between timezones.
So it seems the article can't be summed up in a simple rule like the original comment contends.
> And it seems a bit pedantic to separate it
I would say that the fact that you can't see a distinction between time and a calendar is precisely the reason you're confused. So I wouldn't consider it pedantic.
In retrospective I wish I'd chosen a less fantastical example, because of course people are gonna get distracted. "Aliens" was not the point. But now I can't be bothered anymore, losing interest fast.
There is no absolute time in spacetime, so your calendar invite from an alien friend would include not only the coordinates on Jupiter but also a time value relative to something. Possibly Earth. Maybe even UTC, as observed on Earth.
Special relativity has nothing to with this conversation. You might as well have said "aliens don't speak english! gotcha!"
> You wanted to make a point that time does not depend on physical location
In addition, you got the point wrong. My point wasn't that time doesn't depend on physical location, at all. My point is the measuring the passage of time doesn't require a calendar or a timezone. Completely different points.
If I want to meet an alien species in Jupiter we're not going to coordinate using Earth's calendar. Doesn't mean it's impossible to meet just because they don't know Earth's calendar, we just have to specify a point in TIME without resorting to Earth's calendars. And points in TIME don't depend on timezone changes. Points in the calendar do.
A "timezone" is a map from point in time to point in the calendar. And a "timezone change" is an operation that takes a point in time from one point in the calendar to a different point in the calendar.
> The quirk is that the offset to UTC might not be static because of timezone changes,
An offset to UTC by definition does not depend on timezone, the same way that integers don't depend on timezones. 5 is 5 regardless of the timezone. If I say offset=3711, that has nothing to do with timezones.
You're confusing time with calendar.