📅 Original date posted:2015-09-18
📝 Original message:On Friday, September 18, 2015 8:24:50 PM Btc Drak via bitcoin-dev wrote:
> Google calendar is localised, so it doesn't matter. The problem with
> quoting UTC anyway it the meeting times are going to change for those that
> observe DST. It would be much better to quote an actual timezone of an
> actual area so it will remain constant, like 1700 CEST, or 0900AM PDT for
> example. Otherwise when the clocks change, what was a convenient meeting
> time will become inconvenient for some.
Not everyone does crazy clock-changing. Using such a time system for
scheduling seems to inconvenience the wrong position. (although perhaps
arguably better since most people probably use DST) :p
(Aside, if Google Calendar can't support standard UTC, that sounds like an
argument against using Google Calendar...)
> Urgh... Can we hardfork time? It's clearly in need of an upgrade...
Tonal time works nice any consistently. :D
Luke
Luke Dashjr [ARCHIVE] /
npub1tf…rfq0n
2023-06-07 17:40:53
in reply to nevent1q…q48j
Author Public Key
npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0nPublished at
2023-06-07 17:40:53Event JSON
{
"id": "f56afa701e729eefffc7fc90a98ab0453958930673fcd1323b832e4e2a0aa4d3",
"pubkey": "5a6d1f44482b67b5b0d30cc1e829b66a251f0dc99448377dbe3c5e0faf6c3803",
"created_at": 1686159653,
"kind": 1,
"tags": [
[
"e",
"ac9366433fe3ac9815769d3d08b392ba2c61c38580087cbe8f67ab0125465316",
"",
"root"
],
[
"e",
"7f72704fe99c4238d62dbfcccbefe511fe8276706ae49241d262eff3143fe7c3",
"",
"reply"
],
[
"p",
"cd753aa8fbc112e14ffe9fe09d3630f0eff76ca68e376e004b8e77b687adddba"
]
],
"content": "📅 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",
"sig": "37724f8ef30f0d848878616d1832d4b872fd5c097fd02ad41951ed61ac5c2134dfdf95f8af61859563b4b052b6f3fd8f64886f5052723d4f75d454ab7208ac78"
}