Return-Path: <lf-lists@mattcorallo.com> Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 75C1116F8 for <bitcoin-dev@lists.linuxfoundation.org>; Fri, 18 Sep 2015 20:47:18 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.bluematt.me (mail.bluematt.me [192.241.179.72]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 0CA7B1B1 for <bitcoin-dev@lists.linuxfoundation.org>; Fri, 18 Sep 2015 20:47:18 +0000 (UTC) Received: from [IPv6:2607:fb90:269:50ce:882f:8e4c:a9f7:691e] (unknown [172.56.13.6]) by mail.bluematt.me (Postfix) with ESMTPSA id 949E358481; Fri, 18 Sep 2015 20:47:16 +0000 (UTC) In-Reply-To: <CAAS2fgR59+iFjg5n6des50rJCA8vkRAvjKC3QgRjiYSyy-bA9A@mail.gmail.com> References: <20150918010709.GB5251@amethyst.visucore.com> <55FC70A5.9080603@mattcorallo.com> <CADJgMzsuBrXT1qOAScu+fv_A7Du1XrFoix8nSO14qXj2YD4KtQ@mail.gmail.com> <55FC7394.4060901@mattcorallo.com> <CAAS2fgR59+iFjg5n6des50rJCA8vkRAvjKC3QgRjiYSyy-bA9A@mail.gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 From: Matt Corallo <lf-lists@mattcorallo.com> Date: Fri, 18 Sep 2015 20:36:41 +0000 To: Gregory Maxwell <gmaxwell@gmail.com> Message-ID: <8F9BCA09-1658-4E0D-BE82-BB9EEA08270E@mattcorallo.com> X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>, Cory Fields <cory@coryfields.com>, Pieter Wuille <pieter.wuille@gmail.com> Subject: Re: [bitcoin-dev] Weekly development meetings on IRC X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org> List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe> List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/> List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org> List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help> List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe> X-List-Received-Date: Fri, 18 Sep 2015 20:47:18 -0000 Yes, I'm aware, however they are closer to each other than UTC is to either :p. On September 18, 2015 4:31:28 PM EDT, Gregory Maxwell <gmaxwell@gmail.com> wrote: >On Fri, Sep 18, 2015 at 8:27 PM, Matt Corallo via bitcoin-dev ><bitcoin-dev@lists.linuxfoundation.org> wrote: >> Google Calendar is localized, but has an option to change the >timezone >> of an event, it just doesnt have UTC in its options. So, yes, we >should >> use something that observes DST in roughly the same way as everyone >else >> - CEST/PDT/EST/etc. > >uh. There is fairly little global consistency in DST usage. Lots of >places do dst on different dates. > >So if it's in some DST timezone it's likely to move twice each change >for some subset of the people who do it. > >E.g. europe and US end DST one week apart.