[tz] Adding verified historic details
keisial at gmail.com
Wed Sep 4 22:20:04 UTC 2013
On 04/09/13 23:15, Lester Caine wrote:
> Paul Eggert wrote:
>> On 09/04/13 13:43, Lester Caine wrote:
>>> >Is that good enough to merge?
>> I'm afraid we can't add zones that differ only in pre-1970
>> dates until we can figure out how to filter them out in
>> the default case, as we aren't prepared for the
>> hundreds or thousands of new zones that would be feasible
>> if we opened the floodgates. Zefram has one prototype for
>> filtering, which I really must get to at some point.
> Paul - this is the point of contention !
> Deleting any data is wrong. If users have a reason for only viewing
> part of the data then fair enough, but we have the opportunity here to
> get this right before it becomes embedded in every browser. That does
> not want a broken set of timezones with this arbitrary cutoff - THAT
> is the very thing some of us want to get away from.
I don't know why a browser would want to embed its own copy of tz, but
this seems the wrong example. Actually, I think browsers should not
expose the full tz rules, as that would allow to pinpoint the user quite
accurately by probing old timezones that aren't actually needed by web apps.
More information about the tz