@MSGID: 2:221/1 6105b9d3[...]
@MSGID: 2:221/1 6105b9d3[...]
Nice... but no TZUTC kludge.
Distribution tree of area fidotest for last 31 days
Nice... but no TZUTC kludge.
As if that's really meaningful.
Nice... but no TZUTC kludge.
As if that's really meaningful.
Perhaps not so much in a robot message like that, but IMO for normal discussion it is.
Nice... but no TZUTC kludge.
As if that's really meaningful.
Perhaps not so much in a robot message like that, but IMO for
normal discussion it is.
I fail to see it, Carlos.
I fail to see it, Carlos.
Properly sorted messages when ordering by date in your editor/viewer, for example.
I fail to see it, Carlos.
Properly sorted messages when ordering by date in your
editor/viewer, for example.
30+ years into Fidonet and haven't felt the need once.
[ ...snipped... ]I fail to see it, Carlos.
I suppose that you have discussed this before. Is there some reason why you don't want the TZUTC kludge?
Hola! Carlos,
[ ...snipped... ]I fail to see it, Carlos.
I suppose that you have discussed this before. Is there some
reason why you don't want the TZUTC kludge?
This exchange may be a running joke on the part of Ward, based on the imprecision of the English language. Recall that all kludges have a common inherent attribute: they are -hidden- from normal view.
So, when he says that he 'fails to see it' then possibly he cannot, or will not, or does not, view kludges. For me, not seeing kludges would
be akin to being colour blind.
Hasta,...luego. :-)
Paul.
I suppose that you have discussed this before. Is there some reason why"""""""""""""
you don't want the TZUTC kludge?
@TZUTC: 0200
Anyway, in this message of yours, I see that Golded is showing me your local time. It looks to me like coming from the future.
Anyway, in this message of yours, I see that Golded is showing me your local time. It looks to me like coming from the future.
I suppose that you have discussed this before. Is there some reason why"""""""""""""
you don't want the TZUTC kludge?
Have I ever stated that?
@TZUTC: 0200
Anyway, in this message of yours, I see that Golded is showing me
your local time. It looks to me like coming from the future.
Yes, they are. Eight hours ahead of your clocks. I'm Australian.
I had assumed that this kludge was used by FTN
software and not just CN> something informative. :-/
It should be. But the Fidonet creator ghods didn't see the point when they were communicating only in the USA. In this era we should have message dates using UTC, and TZUTC values for ourselves, in order to calculate various time values for us (informational only).
Ok, I should have written "use" or "have", not "want".
I know... well, actually I only knew you were in Australia. :-) I had checked the nodelist to find out what your TZ should be when I saw some message you posted before with Golded that, BTW, didn't have the TZUTC kludge.
Anyway, the way it is, software can calculate the UTC date if the TZUTC kludge is present. In fact it seems that your T-Bird shows dates to you converted to your local time. In your previous reply you had this:
"On 08/03/2021 04:12 PM, you wrote to Ward Dossche"^^
and the local time of my message was 8:12 AM.
I've checked several Jamnttpd servers and my T-bird shows different
times for the same message: one shows the original local timestamp, another one converted for my timezone... I suppose that it depends on
how it's configured or something. I'll check again later.
Is your goal to strip out the 3rd(+) level of quoting on the path from Telegram to Fido? That's pretty good and reduces the clutter.
Hi, August!
Is your goal to strip out the 3rd(+) level of quoting on the path from
Telegram to Fido? That's pretty good and reduces the clutter.
Yes. You are right.
Hello Brother Rabbit!
** On Thursday 05.08.21 - 14:17, Brother Rabbit wrote to August Abolins: The reply system is not looking right in the LITRPG echo.
--
../|ug
Is it still bad now, or a little better?
I just replied to one in that echo. We shall see.
I saw some message you posted before with Golded that, BTW,
didn't have the TZUTC kludge.
That's probably Golded 1.1.4.7, and maybe why there's a version 1.1.5
now. ;)
I just waited till a civilized time for you to catch the note. :)
05 Aug 2021 09:23, you wrote to me:
I've seen in the github repo that the USETZUTC setting was disabled by default until 1.1.5, so it may work for you if you add 'USETZUTC Yes' to your cfg.
Don't worry, I disabled the sound for my Fido-notifications. :-)
Carlos
I have been a HAM for 50+ years and from the very beginning I always
used GMT (as it was called back then) for my logs (compulsory back
then) and for exchanging written confirmations called QSL cards. HAM
radio is a global thing, so using GMT or UTC is the logical thing to
do. I even had a clock in my shack that showed GMT.
With that background information, I think using local time in Fidonet
was a design flaw. Fidonet, like HAM radio is a globe spanning
activity. Even in its country of origin, the USA, it spanned more than
one time zone from the beginning.
Time information in Fidonet should have been in UTC, not local time.
For additional information a TZLOC kludge could have been used.
How are we doing so far? After all, you're my favourite Spaniard ...
:-)
I have been a HAM for 50+ years and from the very beginning I always
used GMT (as it was called back then) for my logs (compulsory back
then) and for exchanging written confirmations called QSL cards. HAM
radio is a global thing, so using GMT or UTC is the logical thing to
do. I even had a clock in my shack that showed GMT.
A different beginning...
With that background information, I think using local time in Fidonet
was a design flaw. Fidonet, like HAM radio is a globe spanning
activity. Even in its country of origin, the USA, it spanned more
than one time zone from the beginning.
I suppose that they didn't think it would expand so much. Or they just didn't think too much about this. :-)
Time information in Fidonet should have been in UTC, not local time.
For additional information a TZLOC kludge could have been used.
I think I've read some discussions about this in FTSC_PUBLIC time ago,
but I know it's difficult, if not impossible, to make some changes
like this in Fidonet.
Anyway with TZUTC, though maybe a bit kludgy, you can get the same
result (obtaining the UTC time) if the software supports this. But
other than Jamnntpd, no idea what editors or packages do (I'm testing several ones, little by little)
I suppose that they didn't think it would expand so much. Or they just didn't think too much about this. :-)
I suppose that they didn't think it would expand so much. Or they just didn't think too much about this. :-)
Maybe. Or maybe they considered GMT a "European thing". Like meters and kilogra
s. So they ignored it...
Maybe. Or maybe they considered GMT a "European thing". Like meters
and kilograms. So they ignored it...
Several of the offices involved in weather reporting have used it
for years. However, the general US public has enough trouble
figuring out the time zones in the mainland US these days. They
taught us about why there are time zones, what GMT is, etc., in
school. I guess they don't teach that any more. In my experience,
many people cannot even understand a 24 hour clock.
Maybe. Or maybe they considered GMT a "European thing". Like meters
and kilogra s. So they ignored it...
Several of the offices involved in weather reporting have used it for years. However, the general US public has enough trouble figuring out
the time zones in the mainland US these days.
They taught us about why there are time zones, what GMT is, etc., in school. I guess they don't teach that any more. In my experience,
many people cannot even understand a 24 hour clock.
They also messed the region-numbering for example.
Maybe. Or maybe they considered GMT a "European thing". Like meters
and kilograms. So they ignored it...
Anyway with TZUTC, though maybe a bit kludgy, you can get the
same result (obtaining the UTC time) if the software supports
this. But other than Jamnntpd, no idea what editors or packages
do (I'm testing several ones, little by little)
It is not to late to update Golded. It is open source...
They also messed the region-numbering for example.
Do you mean that net numbers are not related to region numbers, like in
z2 (mostly) and z4?
Maybe. Or maybe they considered GMT a "European thing". Like meters
and kilogra s. So they ignored it...
Several of the offices involved in weather reporting have used it for years. However, the general US public has enough trouble figuring out the time zones in the mainland US these days.
A Fidonet sysop is not representative for the general US public would you not s
y?
24 hour clocks are in general use here. Digital clocks are almost always config
red for 24 hour format. Broadcast guides are in 24 hour format. Public transpor
uses 24 hour format for the time tables.
It would have made a lot of sense to use the CCITT-numbering scheme as region numbers ... but the founding fathers in all their wisdom had no clue ...
Distribution tree of area fidotest for last 31 days
| Sysop: | Rempala |
|---|---|
| Location: | Richlands, NC |
| Users: | 103 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 177:22:19 |
| Calls: | 158 |
| Files: | 6 |
| Messages: | 110,512 |