←back to thread

283 points move-on-by | 7 comments | | HN request time: 0.143s | source | bottom
Show context
yellers ◴[] No.45219992[source]
Hang on a second, "(...) in 2023. US/* was moved to tzdata-legacy (...)"

US/* was moved to 'backward' (the file for backward compatibility) in the tz database in 1993(!) and as such was essentially marked as deprecated long enough. https://data.iana.org/time-zones/tzdb/backward

You're telling me you didn't notice ? It was on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying ‘Beware of the Leopard.

replies(3): >>45220141 #>>45221442 #>>45222056 #
zahlman ◴[] No.45220141[source]
> You're telling me you didn't notice ? It was...

In a large fraction of cases in the FOSS world, it comes across that the developers really do want to communicate this sort of thing, but there's no clarity on where or how they should do so. See for example various deprecations in Python packaging tools (and standards).

replies(2): >>45220294 #>>45220316 #
1. JdeBP ◴[] No.45220316[source]
In this case, they did communicate it, and the aforegiven Vogon reference is a mischaracterization. The naming convention is in the current IANA doco and Eggert copy.

* https://data.iana.org/time-zones/tz-link.html#tzdb

* https://web.cs.ucla.edu/~eggert/tz/tz-link.htm#tzdb

Paul Eggert explained the continent/ocean plus largest city naming convention on a WWW page almost a quarter of a century ago. The WWW page was so well publicized that you can find its URL baked into at least four of the O'Reilly animal-cover books from the early 2000s.

* https://web.archive.org/web/20011023074744/http://www.twinsu...

It was explained on Usenet and on mailing lists prior to that.

replies(2): >>45220643 #>>45224476 #
2. bbarnett ◴[] No.45220643[source]
You know, the tzdata people are quite haughty. They claim to store all that change, accurately, and yet here we are.

An example of this falsehood? Well, in the 70s my father convinced most of my hometown, at least the portions between Main St and Wharf, that DST was absurd.

For almost an entire year, this was observed.

Do you think they kept record in tzdata? I tried to convince them, but no! I still have some dateplanners my father had printed up, and even a picture of the sign that was out on the road (to alert visitors!).

But no!

Do not trust the tzdata people. As you can see, they are not so accurate.

replies(4): >>45221025 #>>45222746 #>>45225239 #>>45225303 #
3. macintux ◴[] No.45221025[source]
Once upon a time I stumbled upon a small book of maps showing the time zones in Indiana each year in the mid-20th century. It was fascinating to see how various towns and cities would jump back and forth between Eastern and Central year to year, with little regard for the surrounding rural areas.

I frequently kick myself for losing track of that book.

4. kccqzy ◴[] No.45222746[source]
You are just not providing sufficient proof. Think Wikipedia style proof. The fact that DST is or isn't observed should be published in a real book. A random dude printing some date planners or putting up a sign to be photographed isn't enough proof.
5. ◴[] No.45224476[source]
6. js2 ◴[] No.45225239[source]
It seems like they're being pragmatic, not haughty:

> "The tz database is not authoritative, and it surely has errors. [...] Errors in the tz database arise from many sources: Sometimes, different people in the same city maintain clocks that differ significantly. [...] Even if the time is specified by law, locations sometimes deliberately flout the law. [...] Any attempt to pass the tz database off as the definition of time should be unacceptable to anybody who cares about the facts."

https://data.iana.org/time-zones/theory.html#accuracy

7. dogecoinbase ◴[] No.45225303[source]
If you'd be willing to scan/post those I'd love to see them!