@MSGID: 1:153/7001 b0471470
@CHRS: UTF-8 4
Hey Albert!
<Esc>:read !TZ=Canada/Pacific date
Wed Nov 4 15:20:07 MST 2026
Very sad. This is what happens when you let politicians decide what time it
is.
@MSGID: 1:153/7001 b0471470
@CHRS: UTF-8 4
Hey Albert!
Very sad. This is what happens when you let politicians decide what
time it is.
I notice you are in the (fidonet) politics of time yourself, by choosing not having a TZUTC kludge present in your message! ;-)
I notice you are in the (fidonet) politics of time yourself,
by choosing not having a TZUTC kludge present in your message! ;-)
@MSGID: 2:221/1.58@fidonet 32191c03
@REPLY: 2:280/464 6aebba7b
@PID: OpenXP/5.0.64 (Win32)
@CHRS: ASCII 1
@TZUTC: -0500
I notice you are in the (fidonet) politics of time yourself, by
choosing
not having a TZUTC kludge present in your message! ;-)
I have one:
EMP: /FIDO/TUXPOWER
ABS: Maurice Kinal@1:153/7001
BET: no relative of mine
ROT: 2:221/1!153/7001 757 280/464 221/1
MID: 1:153/7001 b0471470
EDA: 20261104221800W+0 <===== OpenXP's way to report TZUTC
LEN: 562
MAILER: GNU bash, version 5.3.20(1)-release (x86_64-pc-linux-gnu)
@TZ: +0000
I notice you are in the (fidonet) politics of time yourself,
Used to be. I haven't brought it up in ages now that I am back to being a regular nodelisted sysop.
by choosing not having a TZUTC kludge present in your message! ;-)
Do no harm. The TZUTC kludge has a corrupted offset for UTC. How about a TZ
kludge instead? As shown it deploys thee official ***STANDARD*** offset for
UTC rather than a bogus one.
As far as the localtime issue in this part of the world I also choose
not to give it any regard. What for?
Ah, politics again! ;-)
To interface on the same time with the others arround you in your
local community?
To interface on the same time with the others arround you in your
local community?
So far not an issue, even with ones getting it 'wrong' which are many since
Nov. 1, 2026. All my interfaces are on UTC except the clock on the wall which
I didn't bother turning back on the first, which makes it 'right' despite it
being more wrong than PST (Pacific Standard Time) would have been. Now the
wall clock is an hour and 11-ish minutes from the sun instead of only 11-ish
minutes it would be if we had stuck with PST.
I haven't had any complaints from the locals about the wireless hotspots which
are flying UTC.
As long as you and the locals are happy with it! ;-)
| Sysop: | Eric Oulashin |
|---|---|
| Location: | Beaverton, Oregon, USA |
| Users: | 122 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 11:35:47 |
| Calls: | 9,627 |
| Calls today: | 1 |
| Files: | 9,582 |
| D/L today: |
63 files (19,933K bytes) |
| Messages: | 432,797 |
| Posted today: | 2 |