[prev in list] [next in list] [prev in thread] [next in thread] 

List:       nanog
Subject:    Re: [time-nuts] Fwd: FW: Memorial service for David Mills
From:       Dave Hart <davehart () gmail ! com>
Date:       2024-03-07 20:00:50
Message-ID: CAMbSiYDwNF5Cff65wVc9u87kF2C6QpxtWM5GnfO+f6bBpNQOaw () mail ! gmail ! com
[Download RAW message or body]

On Thu, 7 Mar 2024 at 14:16, <tme@asteroidinitiatives.com> wrote:

> On 2024-03-07 04:10, Dave Hart via time-nuts wrote:
> > [...] this coming Monday at 3:00pm local time.  With Sunday's leap
> > ahead in local time, that's 17:00 UTC, Noon US Pacific time.
>
> Thank you for this notice. However, if this is 3:00 PM (1500) EDT that's
> 1900 UTC.
>
> Is that interpretation correct?
>

Yes, thanks for the correction.  I clearly shouldn't do time math in public.

To further confuse matters, I took the option in Gmail's triple-dot "more"
composition menu to "Set up a time to meet" hoping it would include a
useful calendar attachment or at least a link to include the event in a
recipient's Google Calendar.  As received by another account of mine, it
was neither, and the text had the wrong time (13:00 UTC) despite having the
correct time in my Google Calendar, which is set to show both UTC and
Eastern time.  Local time can be tricky, and I'm glad NTP generally shrugs
and leaves that problem to others.

[Attachment #3 (text/html)]

<div dir="ltr"><div dir="ltr"><div class="gmail_default" \
style="font-family:&quot;trebuchet ms&quot;,sans-serif;font-size:small"><span \
style="font-family:Arial,Helvetica,sans-serif">On Thu, 7 Mar 2024 at 14:16, &lt;<a \
href="mailto:tme@asteroidinitiatives.com">tme@asteroidinitiatives.com</a>&gt; \
wrote:</span><br></div></div><div class="gmail_quote"><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">On 2024-03-07 04:10, Dave Hart via time-nuts \
wrote:<br> <span class="gmail_default" style="font-family:&quot;trebuchet \
ms&quot;,sans-serif;font-size:small">&gt; [...]</span>  this coming Monday at 3:00pm \
local time.   With Sunday&#39;s<span class="gmail_default" \
style="font-family:&quot;trebuchet ms&quot;,sans-serif;font-size:small">  \
</span>leap<br> &gt; ahead in local time, that&#39;s 17:00 UTC, Noon US Pacific time. \
<br> <br>
Thank you for this notice. However, if this is 3:00 PM (1500) EDT that&#39;s <br>
1900 UTC.<br>
<br>
Is that interpretation correct?<br></blockquote><div><br></div><div \
class="gmail_default" style="font-family:&quot;trebuchet \
ms&quot;,sans-serif;font-size:small">Yes, thanks for the correction.   I clearly \
shouldn&#39;t do time math in public.</div><div class="gmail_default" \
style="font-family:&quot;trebuchet \
ms&quot;,sans-serif;font-size:small"><br></div><div class="gmail_default" \
style="font-family:&quot;trebuchet ms&quot;,sans-serif;font-size:small">To further \
confuse matters, I took the option in Gmail&#39;s  triple-dot &quot;more&quot; \
composition menu to &quot;Set up a time to meet&quot; hoping it would include a \
useful calendar attachment or at least a link to include the event in a \
recipient&#39;s Google Calendar.   As received by another account of mine, it was \
neither, and the text had the wrong time (13:00 UTC) despite having the correct time \
in my Google Calendar, which is set to show both UTC and Eastern time.   Local time \
can be tricky, and I&#39;m glad NTP generally shrugs and leaves that problem to \
others.</div></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]