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