<oembed><type>rich</type><version>1.0</version><author_name>npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwet</author_name><author_url>https://nostr.ae/npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwet</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-09-18&#xA;📝 Original message:On Fri, Sep 18, 2015 at 8:27 PM, Matt Corallo via bitcoin-dev&#xA;&lt;bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&gt; Google Calendar is localized, but has an option to change the timezone&#xA;&gt; of an event, it just doesnt have UTC in its options. So, yes, we should&#xA;&gt; use something that observes DST in roughly the same way as everyone else&#xA;&gt; - CEST/PDT/EST/etc.&#xA;&#xA;uh. There is fairly little global consistency in DST usage. Lots of&#xA;places do dst on different dates.&#xA;&#xA;So if it&#39;s in some DST timezone it&#39;s likely to move twice each change&#xA;for some subset of the people who do it.&#xA;&#xA;E.g. europe and US end DST one week apart.</html></oembed>