Matt Corallo [ARCHIVE] on Nostr: 📅 Original date posted:2015-09-18 📝 Original message:Yes, I'm aware, however ...
📅 Original date posted:2015-09-18
📝 Original message:Yes, I'm aware, however they are closer to each other than UTC is to either :p.
On September 18, 2015 4:31:28 PM EDT, Gregory Maxwell <gmaxwell at gmail.com> wrote:
>On Fri, Sep 18, 2015 at 8:27 PM, Matt Corallo via bitcoin-dev
><bitcoin-dev at lists.linuxfoundation.org> wrote:
>> Google Calendar is localized, but has an option to change the
>timezone
>> of an event, it just doesnt have UTC in its options. So, yes, we
>should
>> use something that observes DST in roughly the same way as everyone
>else
>> - CEST/PDT/EST/etc.
>
>uh. There is fairly little global consistency in DST usage. Lots of
>places do dst on different dates.
>
>So if it's in some DST timezone it's likely to move twice each change
>for some subset of the people who do it.
>
>E.g. europe and US end DST one week apart.
📝 Original message:Yes, I'm aware, however they are closer to each other than UTC is to either :p.
On September 18, 2015 4:31:28 PM EDT, Gregory Maxwell <gmaxwell at gmail.com> wrote:
>On Fri, Sep 18, 2015 at 8:27 PM, Matt Corallo via bitcoin-dev
><bitcoin-dev at lists.linuxfoundation.org> wrote:
>> Google Calendar is localized, but has an option to change the
>timezone
>> of an event, it just doesnt have UTC in its options. So, yes, we
>should
>> use something that observes DST in roughly the same way as everyone
>else
>> - CEST/PDT/EST/etc.
>
>uh. There is fairly little global consistency in DST usage. Lots of
>places do dst on different dates.
>
>So if it's in some DST timezone it's likely to move twice each change
>for some subset of the people who do it.
>
>E.g. europe and US end DST one week apart.