Hey Björn!

We have a Ukrainian real name (mine), a Swedish recepeint (you), and a msg_body where anything goes. One might be tempted to call it a smörgåsbord.

Life is good,
Maurice

-o o- o- -o o- -o o- -o o- -o -o o- o- -o -o -o
(\ /) /) (\ /) (\ /) (\ /) (\ (\ /) /) (\ (\ (\
^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ... Fidonet 4K - You load sixteen penguins and what do you get?
--- GNU bash, version 5.2.15(1)-release (x86_64-pc-linux-gnu)
* Origin: One of us @ (1:153/7001.2989)

Hey Моріс!

Perfect. I believe this reply confirms that we are the best there is. Nobody else comes close.

Life is good,
Maurice

o- -o -o -o
/) (\ (\ (\
^^ ^^ ^^ ^^
... Nimm meine Frau ... ich befehle es dir!
- Wolfgang Youngman
--- GNU bash, version 5.2.15(1)-release (x86_64-pc-linux-gnu)
* Origin: Little Mikey's EuroPoint @ (2:280/464.113)

Hello Maurice,

@MSGID: 2:280/464.113 641e8dc3
@REPLY: 1:153/7001.2989 641e8a14
@CHRS: UTF-8 4
@TZUTC: -0000

That "-0000" does not seem right...

Perfect.

Hmmm...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nieuw Schnøørd (2:280/5555)

Hey Michiel!

MvdV> That "-0000" does not seem right...

It is frowned upon but is entirely acceptable as per ISO standards. I've been thinking of using "-00:25:21" instead, as the base of a "Fidonet Time Space Continuum" coordinate system that by default would allow for up to the second corrections.

MvdV> Hmmm...

Agreed.

Life is good,
Maurice

-o o- -o o- o- o- o- o- o- -o -o o- -o o- -o o-
(\ /) (\ /) /) /) /) /) /) (\ (\ /) (\ /) (\ /)
^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ... Fidonet 4K - You load sixteen penguins and what do you get?
--- GNU bash, version 5.2.15(1)-release (x86_64-pc-linux-gnu)
* Origin: One of us @ (1:153/7001.2989)

Hello Моріс,

On Saturday March 25 2023 07:11, you wrote to me:


MvdV>> That "-0000" does not seem right...

The nummeric value does not match the combination of the time stamp in the header and your fysical location which is not the Zulu time zone. The value should be -0700 as in the messages from your Z1 AKA.

МК>> It is frowned upon but is entirely acceptable as per ISO standards.

It is not in complience with FTS-4008.002 and it is Fidonet standards that apply here.


Cheers, Michiel

--- GoldED+/W32-MINGW 1.1.5-b20110320
* Origin: Blijf Tønijn (2:280/5555)

Hey Michiel!

MvdV> The value should be -0700 as in the messages from your Z1 AKA.

AHA!!! You were right and I now have it fixed. Thank you for the heads up and the ftn datetime stamp is now back to UTC which it normally is. That was definetly a mistake on my part.

MvdV> It is not in complience with FTS-4008.002 and it is Fidonet
MvdV> standards that apply here.

It will no longer be an issue.

Life is good,
Maurice

o- -o -o -o -o o- -o -o -o o- o- o- -o -o o- o- /) (\ (\ (\ (\ /) (\ (\ (\ /) /) /) (\ (\ /) /) ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ... Fidonet 4K - You load sixteen penguins and what do you get?
--- GNU bash, version 5.2.15(1)-release (x86_64-pc-linux-gnu)
* Origin: One of us @ (1:153/7001.2989)

Michiel van der Vlist wrote to Maurice Kinal <=-

That "-0000" does not seem right...

I'm surprised Fidonet didn't specify UTC (or some USA time zone) for all
of Fidonet, given the ZMH requirement back before continuous mail was
possible.

I ran Fido BBS software, then an Opus CBCS as my first attempts at
running a BBS. I was amazed at how Opus could handle mail calling
during ZMH and regular callers every other time.

It wasn't very long before I discovered FrontDoor and Telegard, which
begat a multi-year effort at creating the One Batch File to rule them
all.



... Look through the eye to know thyself.
--- MultiMail/Win v0.52
* Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)

Hello Kurt,

On Saturday March 25 2023 09:29, you wrote to me:

I'm surprised Fidonet didn't specify UTC (or some USA time zone) for
all of Fidonet, given the ZMH requirement back before continuous mail
was possible.

I will go further than that: the founding fathers made a serious mistake by using local time instead of UTC - or GMT as it was called back then. There has always been a large overlap between the HAM community and the Fidonet community. When I became a HAM in the early sixties of the previous century HAMs already used GMT when logging contacts and exchanging QSL cards. It makes sense when using a medium that does not stop at national borders and time zones.

While it may not have been clear that Fidonet would quickly become a global thing, it would have been clear that it was never limited to one time zone. And while Tom Jennings was not a HAM (AFAIK) my intelligent guess is that by the time Fidonet had reached 50 nodes, about half of the sysops were HAMs and it would not have been too late to make the change from local time to GMT.


Cheers, Michiel (PA0MMV)

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nieuw Schnøørd (2:280/5555)

Re: en v�lsmakande liten bit
By: Michiel van der Vlist to Kurt Weiske on Sat Mar 25 2023 07:40 pm

While it may not have been clear that Fidonet would quickly become a global thing, it would have been clear that it was never limited to one time zone. And while Tom Jennings was not a HAM (AFAIK) my intelligent

If I recall my Fido history, the first networking was set up between San Francisco and 2 sysops in the Chicago area, 2 time zones away. From the start time zones were an issue.
--- SBBSecho 3.20-Win32
* Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)

Re: en v�lsmakande liten bit
By: Michiel van der Vlist to Kurt Weiske on Sat Mar 25 2023 07:40 pm

Hello Kurt,

On Saturday March 25 2023 09:29, you wrote to me:

I'm surprised Fidonet didn't specify UTC (or some USA time zone) for all of Fidonet, given the ZMH requirement back before continuous mail was possible.

I will go further than that: the founding fathers made a serious mistake by using local time instead of UTC - or GMT as it was called back then. There has always been a large overlap between the HAM community and the Fidonet community. When I became a HAM in the early sixties of the previous century HAMs already used GMT when logging contacts and exchanging QSL cards. It makes sense when using a medium that does not stop at national borders and time zones.

While it may not have been clear that Fidonet would quickly become a global thing, it would have been clear that it was never limited to one time zone. And while Tom Jennings was not a HAM (AFAIK) my intelligent guess is that by the time Fidonet had reached 50 nodes, about half of the sysops were HAMs and it would not have been too late to make the change from local time to GMT.

Each message can specify the date/time and zone which can be converted to/from UTC if desired by the receiving system. If the sender prefers, they can just use UTC (which I agree, should have been the assumed-default when no timezone header was included).

Like NNTP articles, it's really up to the sender as to how they want to represent the date/time of the message they're sending, but it should always be easily converted or compared with a local timezone of a reader.
--
digital man (rob)

Rush quote #71:
He's not concerned with yesterday, he knows constant change is here today Norco, CA WX: 54.9�F, 44.0% humidity, 0 mph ESE wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)