Luke Dashjr [ARCHIVE] on Nostr: 📅 Original date posted:2015-09-18 📝 Original message:On Friday, September 18, ...
📅 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
📝 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