From: Dave Scotese <dscotese@litmocracy.com>
To: Luke Dashjr <luke@dashjr.org>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>,
Pieter Wuille <pieter.wuille@gmail.com>,
Cory Fields <cory@coryfields.com>
Subject: Re: [bitcoin-dev] Weekly development meetings on IRC
Date: Fri, 18 Sep 2015 16:29:42 -0700 [thread overview]
Message-ID: <CAGLBAhcT0GkvKA0_d95=3XARng5aL2DQ-HFwtFWLvEJbry+VzA@mail.gmail.com> (raw)
In-Reply-To: <201509182150.06275.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 1931 bytes --]
I am in a timezone that uses DST (currently PDT), but I would like us to
use a timezone that does NOT use DST. It will be nice to have something
that reflects the seasonal patterns like my own body does. I hate the time
change in both ways.
On Fri, Sep 18, 2015 at 2:50 PM, Luke Dashjr via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> 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
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--
I like to provide some work at no charge to prove my value. Do you need a
techie?
I own Litmocracy <http://www.litmocracy.com> and Meme Racing
<http://www.memeracing.net> (in alpha).
I'm the webmaster for The Voluntaryist <http://www.voluntaryist.com> which
now accepts Bitcoin.
I also code for The Dollar Vigilante <http://dollarvigilante.com/>.
"He ought to find it more profitable to play by the rules" - Satoshi
Nakamoto
[-- Attachment #2: Type: text/html, Size: 2856 bytes --]
next prev parent reply other threads:[~2015-09-18 23:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 1:07 [bitcoin-dev] Weekly development meetings on IRC Wladimir J. van der Laan
2015-09-18 2:56 ` Alex Morcos
2015-09-18 4:19 ` Peter Todd
2015-09-18 4:30 ` Mark Friedenbach
2015-09-18 4:57 ` Luke Dashjr
2015-09-18 7:04 ` Jonas Schnelli
2015-09-18 8:20 ` Eric Lombrozo
2015-09-18 20:14 ` Matt Corallo
2015-09-18 20:24 ` Btc Drak
2015-09-18 20:27 ` Matt Corallo
2015-09-18 20:30 ` Jeffrey Paul
2015-09-18 20:34 ` Matt Corallo
2015-09-18 20:31 ` Gregory Maxwell
2015-09-18 20:34 ` Btc Drak
2015-09-21 13:01 ` jl2012
2015-09-18 20:36 ` Matt Corallo
2015-09-18 21:50 ` Luke Dashjr
2015-09-18 23:29 ` Dave Scotese [this message]
2015-09-18 21:50 ` Luke Dashjr
2015-09-21 13:29 ` Wladimir J. van der Laan
2015-09-21 13:51 ` gb
2015-09-22 14:03 ` Wladimir J. van der Laan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGLBAhcT0GkvKA0_d95=3XARng5aL2DQ-HFwtFWLvEJbry+VzA@mail.gmail.com' \
--to=dscotese@litmocracy.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=cory@coryfields.com \
--cc=luke@dashjr.org \
--cc=pieter.wuille@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox