@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?
| Sysop: | KrAAB |
|---|---|
| Location: | Donna, TX |
| Users: | 4 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 170:42:01 |
| Calls: | 57,180 |
| Files: | 3,971 |
| D/L today: |
26 files (9,999K bytes) |
| Messages: | 61,523 |