-={ dinsdag, 06 oktober 2015, 12:37:55 +0200 }=-

Hey Wilfred!

Let's try this again while this node's connection appears to be working ... for
now.  I am not holding my breath.

Forget about 1:261/38.0's setup.  I was only using that while the connection
here was broken ... again.  The point was that 1:153/7001.0's main link is
flying the wrong utc offset which is the one I posted.

Anyhow it really, really doesn't matter unless of course it does.  Speaking for
myself I don't use fidonet datetime stamps for anything as I suspect them to be
wrong nevermind any bogus utc offset that may or may not be subject to the whim
of some ignorant politician playing around with DST and ruining any possible
chance of network credibility.

Hopefully this message will get though to you and I am going to take this
opportunity to declare this a dead subject to me.  I have no plan to impliment
a TZUTC kludge and definetly don't expect to impliment a sort on this end that
depends on something that even if it becomes universal within fidonet is most
likely to cause greater grief than we currently have in fidonet.

That is this node's stupidity and it fully plans on sticking with it to the
bitter end which by all indications appears to be close at hand.  Besides with
the included datetime stamp between the -={ and }=- characters one can readily
see that the msg headers datetime stamp *is* utc and thus not subject to any
other node's stupidity let alone stupidity outside fidonet.

Life is good,
Maurice

... Don't cry for me I have vi.
--- GNU bash, version 4.3.42(1)-release (x86_64-unknown-linux-gnu)