Just checking...
--- SBBSecho 3.06-Linux
* Origin: Stepping Stone BBS -- telnet://vintagebbsing.com (1:298/25)

Just checking...

Nope. :P

--- BBBS/Li6 v4.10 Toy-3
* Origin: Nightfall Ordain (1:298/26)

Re: Is this thing on?
By: Jon Justvig to cr1mson on Wed Sep 05 2018 08:04 pm

Just checking...

Nope. :P

Too late. I already know I'm supposed to use real names in Fidonet and fixed it. :P
--- SBBSecho 3.06-Linux
* Origin: Stepping Stone BBS -- telnet://vintagebbsing.com (1:298/25)

.TZUTC: 0000
.MSGID: 38.fido-fidotest@1:298/25 1ff5b2c6
.PID: Synchronet 3.17a-Linux Aug 26 2018 GCC 7.3.0
.TID: SBBSecho 3.06-Linux r3.92 Aug 26 2018 GCC 7.3.0
Just checking...
--- SBBSecho 3.06-Linux
ng.com (1:298/25)

Just replying :)
---
* OLXWin 1.00b * Because of BBSing, reading and writing actually pay off!
* Origin: Omicron Theta (1:116/17)

Hi cr1mson!

Your timezone is wrong.

05 Sep 2018 20:02, from cr1mson -> All:

@TZUTC: 0000
@MSGID: 38.fido-fidotest@1:298/25 1ff5b2c6
@PID: Synchronet 3.17a-Linux Aug 26 2018 GCC
@TID: SBBSecho 3.06-Linux r3.92 Aug 26 2018 GCC 7.3.0
Just checking...
SEEN-BY: 57/0 103/705 154/10 203/0 221/0 226/100 229/426 240/1661 5832 SEEN-BY: 267/800 280/464 5003 5555 310/31 317/2 3 393/68 423/120
712/848
SEEN-BY: 770/0 1 100 330 340 772/0 1 210 500 2320/100 200
@PATH: 298/25 282/1031 261/38 393/68 770/1 280/464

CU, Ricsi

... We're not retreating - we're advancing in another direction.
--- GoldED+/LNX
* Origin: Alex, I'll take "Things Only I Know" for $1000. (2:310/31)

Re: Is this thing on?
By: Richard Menedetter to cr1mson on Thu Sep 06 2018 09:19 am

Hi cr1mson!

Your timezone is wrong.

05 Sep 2018 20:02, from cr1mson -> All:

@TZUTC: 0000

Some BBSes do intentionally run on UTC. That doesn't necessarily make them "wrong".

digital man

Synchronet "Real Fact" #87:
Synchronet Message Base and its library, SMBLIB, was used by AXiS BBS Software. Norco, CA WX: 63.6oF, 88.0% humidity, 0 mph SE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.06-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Hi Rob!

06 Sep 2018 00:34, from Rob Swindell -> Richard Menedetter:

Your timezone is wrong.

@TZUTC: 0000

Some BBSes do intentionally run on UTC. That doesn't necessarily make
them "wrong".

Let me rephrase then.

@cr1mson
Are you sure that you want to send timezone 0 (all your dates are sent in UTC not local time)?
Also please use your real name.

CU, Ricsi

... The sooner I fall behind, the more time I have to catch up.
--- GoldED+/LNX
* Origin: Support your local medical examiner: die strangely. (2:310/31)

On 09/05/18, cr1mson pondered and said...

@TZUTC: 0000
@MSGID: 38.fido-fidotest@1:298/25 1ff5b2c6
@PID: Synchronet 3.17a-Linux Aug 26 2018 GCC
@TID: SBBSecho 3.06-Linux r3.92 Aug 26 2018 GCC 7.3.0
@SEEN-BY: 57/0 226/100 267/800 280/464 317/2 3 393/68 770/0 1 100 330 340 @SEEN-BY: 772/0 1 210 500 2320/200
@PATH: 298/25 282/1031 261/38 393/68 770/1
Just checking...
--- SBBSecho 3.06-Linux
* Origin: Stepping Stone BBS -- telnet://vintagebbsing.com (1:298/25)

Yep :)

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

Re: Re: Is this thing on?
By: Paul Hayton to cr1mson on Thu Sep 06 2018 09:11 pm

On 09/05/18, cr1mson pondered and said...

Just checking...

Yep :)

Thanks Paul. :) Anyone around here not on FSXNet, I encourage you to check it out.

Sincerely,
Jon Justvig
--- SBBSecho 3.06-Linux
* Origin: Stepping Stone BBS -- telnet://vintagebbsing.com (1:298/25)

On 2018 Sep 05 20:02:24, you wrote to All:

@TZUTC: 0000
@MSGID: 38.fido-fidotest@1:298/25 1ff5b2c6
@PID: Synchronet 3.17a-Linux Aug 26 2018 GCC 7.3.0
@TID: SBBSecho 3.06-Linux r3.92 Aug 26 2018 GCC 7.3.0
Just checking...
--- SBBSecho 3.06-Linux
* Origin: Stepping Stone BBS -- telnet://vintagebbsing.com (1:298/25) SEEN-BY: 15/0 19/36 34/999 90/1 116/18 116 120/302 331 123/25 140 150 755 SEEN-BY: 135/300 153/7715 154/10 218/700 220/60 222/2 230/150 152 240/1120 SEEN-BY: 250/1 261/38 100 1466 266/404 512 267/155 275/100 280/1027 282/1031
SEEN-BY: 282/1032 1056 1060 291/1 111 298/25 26 320/119 219 340/400 342/13 SEEN-BY: 393/68 396/45 640/1384 712/848 801/161 189 2320/100 105 3634/12

15

SEEN-BY: 3634/22 24 27 50 119 666 5020/715 1042
@PATH: 298/25 282/1031 261/38 3634/12

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... A pest is a man that can talk like an encyclopedia - and does.
---
* Origin: (1:3634/12.73)

Hi Jon!

06 Sep 2018 17:18, from Jon Justvig -> Paul Hayton:

@TZUTC: 0000

Sorry ... I missed your reply on the timezone setting.
Is your system running with local time?

CU, Ricsi

... Never go to the cannibal restaurant... Dinner costs an arm and a leg.
--- GoldED+/LNX
* Origin: Most of our future lies ahead. (2:310/31)

Re: Is this thing on?
By: Richard Menedetter to Jon Justvig on Fri Sep 07 2018 02:45 pm

Hi Richard!

06 Sep 2018 17:18, from Jon Justvig -> Paul Hayton:

@TZUTC: 0000

Sorry ... I missed your reply on the timezone setting.
Is your system running with local time?

Yup, not sure about the time zone. I haven't ever had a complaint in that department, but you know life, if it's bound to break, it will eventually. Nothing seems to last forever, except maybe earth, water, wind and fire. :)

Sincerely,
Jon Justvig
--- SBBSecho 3.06-Linux
* Origin: Stepping Stone BBS -- telnet://vintagebbsing.com (1:298/25)

Hi Jon!

07 Sep 2018 17:53, from Jon Justvig -> Richard Menedetter:

@TZUTC: 0000

Yup, not sure about the time zone.

Sorry ... I do not understand.
You do not know what timezone you live in???

I haven't ever had a complaint in that department

Well, now you have ;)

but you know life, if it's bound to break, it will eventually.

It did not break.
Something can only break if it worked beforehand.

You seem to have it misconfigured from the start.

If you are not sure what timezone you are in then at least configured your editor to OMIT the timezone statement completely instead of sending out false information!!

CU, Ricsi

... A little knowledge can be dangerous, the lack thereof, devastating.
--- GoldED+/LNX
* Origin: If we're both going to Hell, maybe we should carpool? (2:310/31)

Hi! Richard,

On 08 Sep 18 12:54, you wrote to Jon Justvig:

@TZUTC: 0000

Yup, not sure about the time zone.

Sorry ... I do not understand.
You do not know what timezone you live in???

Fidonet isn't what it used to be, Richard. Now, I'm not sure if this is the case with Jon but some operators tend not to have their own hardware. A lot of
fellers have their systems -hosted- elsewhere, sometimes quite remote from where they reside. So there is some frustration as to which TZ might describe where their configuration is. ;)

Cheers,
Paul.

... Dust is a protective coating for furniture.
--- GoldED+/LNX 1.1.5-b20130515
* Origin: Quinn's Rock - Live from Paul's Xubuntu desktop! (3:640/1384)

Hello Paul,

On Saturday September 08 2018 21:02, you wrote to Richard Menedetter:

You do not know what timezone you live in???

Fidonet isn't what it used to be, Richard. Now, I'm not sure if this
is the case with Jon but some operators tend not to have their own hardware. A lot of fellers have their systems -hosted- elsewhere, sometimes quite remote from where they reside. So there is some frustration as to which TZ might describe where their configuration
is. ;)

The location of the server is irrelevant. It is the location of the terminal from where the message is written that counts. The time in the message header displays the local time *1) of the writer of the message. The TZUTC kludge shows the difference between that local time and UTC.


*1) With the knowledge that we have now, I say that using local time for a global medium was a design error. Message and packet headers should be in UTC. Optionally converted to local time by the reciever.


Cheers, Michiel

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

Hi! Michiel,

On 08 Sep 18 13:20, you wrote to me:

*1) With the knowledge that we have now, I say that using local time
for a global medium was a design error. Message and packet headers
should be in UTC. Optionally converted to local time by the reciever.

I think we're in agreement, and we may have talked about this before. But I have to say that I came from a working environment with a lot of telex traffic.
Which meant that each message was timestamped with the then current UTC (GMT) date/time value.

Back in the Fidonet realm, such a practice would just leave any conversion to/from local time to whatever message reader the sysop is using.

Cheers,
Paul.

... "Nothing's too good for the man who shot Liberty Valance."
--- GoldED+/LNX 1.1.5-b20130515
* Origin: Quinn's Rock - Live from Paul's Xubuntu desktop! (3:640/1384)

Hi Paul!

08 Sep 2018 21:02, from Paul Quinn -> Richard Menedetter:

@TZUTC: 0000

Yup, not sure about the time zone.

Sorry ... I do not understand.
You do not know what timezone you live in???

Fidonet isn't what it used to be, Richard.

I agree ... I am just not quit sure if we mean the same thing ;)

Now, I'm not sure if this is the case with Jon but some operators tend
not to have their own hardware.

I know only one person who can tell us ...
Let's wait for his answer.

A lot of fellers have their systems -hosted- elsewhere,
sometimes quite remote from where they reside.
So there is some frustration as to which TZ might describe where their configuration is. ;)

Well most of that systems are root servers.
You can configure anything that you want. Just configure it if it were at the location you are.
If it is not a root server then just check what TZ is configured.
Quit easy in any case.

CU, Ricsi

... The smallest good deed is better than the grandest intention.
--- GoldED+/LNX
* Origin: THISTAGLINEISDESIGNEDTOGIVEYOUAHEADACHE! (2:310/31)

Hi Michiel,

On 2018-09-08 13:20:03, you wrote to Paul Quinn:

MvdV> *1) With the knowledge that we have now, I say that using local time
MvdV> for a global medium was a design error. Message and packet headers
MvdV> should be in UTC. Optionally converted to local time by the
MvdV> reciever.

You are missing information that way! I like to know at what local time a message is written. It could give some information about the state of mind of the message writer at the time he wrote the message. It's also interesting to know the time zone of the message writer.

With local time + utc offset, you have all information. Your software could in theory convert that to UTC if that's your preference, or your own local time...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello Paul,

On Saturday September 08 2018 21:39, you wrote to me:

*1) With the knowledge that we have now, I say that using local
time for a global medium was a design error. Message and packet
headers should be in UTC. Optionally converted to local time by
the reciever.

I think we're in agreement, and we may have talked about this before.
But I have to say that I came from a working environment with a lot of telex traffic. Which meant that each message was timestamped with the then current UTC (GMT) date/time value.

Yes, I think we have discussed this before. When I was active as a radio amateur (PA0MMV) I used to keep the logs in (then) GMT. Also the time on QSL cards was in GMT. To make it easier to check against he logs.


Cheers, Michiel

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

Hello Wilfred,

On Saturday September 08 2018 17:22, you wrote to me:

MvdV>> *1) With the knowledge that we have now, I say that using local
MvdV>> time for a global medium was a design error. Message and packet
MvdV>> headers should be in UTC. Optionally converted to local time by
MvdV>> the reciever.

You are missing information that way! I like to know at what local
time a message is written.

You have a tendency to like to know too much...

It could give some information about the state of mind of the message writer at the time he wrote the message. It's also interesting to know
the time zone of the message writer.

If the sender of the message wanted to reveal that information, it could easely
be solved by adding a TZLOC kludges that tells the difference between UTC and the sender's local time.

And if the sender does not want to reveal that information... you have no need to know.

With local time + utc offset, you have all information.

The UTC time is needed to compare logs. Without the TZUTC kludge, I do not have
that information. Many messages still do not have a TZUTC kludge.

Comparing logs is much more important than knowing the local time of the sender.

Your software could in theory convert that to UTC if that's your preference, or your own local time...

Not when the TZUTC kludge is missing...


Cheers, Michiel

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