{"type":"rich","version":"1.0","author_name":"npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0n","author_url":"https://nostr.ae/npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0n","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-09-18\n📝 Original message:On Friday, September 18, 2015 8:24:50 PM Btc Drak via bitcoin-dev wrote:\n\u003e Google calendar is localised, so it doesn't matter. The problem with\n\u003e quoting UTC anyway it the meeting times are going to change for those that\n\u003e observe DST. It would be much better to quote an actual timezone of an\n\u003e actual area so it will remain constant, like 1700 CEST, or 0900AM PDT for\n\u003e example. Otherwise when the clocks change, what was a convenient meeting\n\u003e time will become inconvenient for some.\n\nNot everyone does crazy clock-changing. Using such a time system for \nscheduling seems to inconvenience the wrong position. (although perhaps \narguably better since most people probably use DST) :p\n\n(Aside, if Google Calendar can't support standard UTC, that sounds like an \nargument against using Google Calendar...)\n\n\u003e Urgh... Can we hardfork time? It's clearly in need of an upgrade...\n\nTonal time works nice any consistently. :D\n\nLuke"}