From: jsteve@superglobalmegacorp.com (Jason Stevens)
Subject: [TUHS] Happy birthday, Internet!
Date: Sun, 9 Apr 2017 10:42:19 +0800 [thread overview]
Message-ID: <D9A6E50B-04BC-4557-B1C2-AB07CA7A64C8@superglobalmegacorp.com> (raw)
In-Reply-To: <alpine.BSF.2.20.1704081456380.24640@aneurin.horsfall.org>
Moving to Hong Kong has made this a major issue for me as well... It can be strange sending stuff from the future and getting replies in the past, just as I then forget to phone people the day after for stuff so I have to slide my calendar+1 day. It's a shame we don't have a real universal time
On April 8, 2017 1:13:42 PM GMT+08:00, Dave Horsfall <dave at horsfall.org> wrote:
>On Fri, 7 Apr 2017, Greg 'groggy' Lehey wrote:
>
>> > Actual data transmissions were first made on October 29 later that
>> > year. If my two-minute research checks out.
>>
>> Yes, this was my date, too, though I call it 30 October (UTC).
>> https://en.wikipedia.org/wiki/History_of_the_Internet#ARPANET
>
>This is a problem that I regularly face, when keeping a global
>calendar.
>
>I'm in Australia (Sydney time), which is pretty much at the leading
>edge
>of the dateline, but most of America is close to the trailing edge, and
>
>therefore events can happen "yesterday".
>
>So, which reference should I use? My time, US time (for US events), or
>
>UTC? I'm starting to lean towards the latter, but it's equally
>confusing;
>I'll have people saying that it happened yesterday, by their reference.
>
>I dimly recall that the moon landings were on GMT (not the same as
>UTC),
>for example.
>
>--
>Dave Horsfall DTM (VK2KFU) "Those who don't understand security will
>suffer."
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170409/2d95dce1/attachment-0001.html>
next prev parent reply other threads:[~2017-04-09 2:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 4:48 Dave Horsfall
2017-04-07 4:58 ` Warren Toomey
2017-04-07 5:13 ` Lars Brinkhoff
2017-04-07 6:57 ` Greg 'groggy' Lehey
2017-04-08 5:13 ` Dave Horsfall
2017-04-09 0:09 ` Greg 'groggy' Lehey
2017-04-09 2:42 ` Jason Stevens [this message]
2017-04-10 5:54 ` Dave Horsfall
2017-04-07 13:55 ` Nemo
2018-04-06 20:56 Dave Horsfall
2018-04-06 23:10 ` Nemo
2018-04-06 23:19 ` Dave Horsfall
2018-04-06 23:56 ` Kurt H Maier
2018-04-07 4:54 Rudi Blom
2018-04-07 15:21 ` Clem Cole
2018-04-07 12:50 Noel Chiappa
2018-04-07 14:34 ` Steve Nickolas
2018-04-07 14:44 ` Clem Cole
2018-04-08 23:34 ` Dave Horsfall
2018-04-09 0:06 ` Clem Cole
2018-04-09 1:16 ` Kurt H Maier
2018-04-08 23:34 ` Dave Horsfall
2018-04-09 14:52 Noel Chiappa
2018-04-09 15:01 ` Erik E. Fair
2018-04-09 14:57 Noel Chiappa
2018-04-09 15:37 Noel Chiappa
2018-04-10 18:32 ` Clem Cole
2018-04-10 19:11 ` Clem Cole
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=D9A6E50B-04BC-4557-B1C2-AB07CA7A64C8@superglobalmegacorp.com \
--to=jsteve@superglobalmegacorp.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;
as well as URLs for NNTP newsgroup(s).