Text 2719, 88 rader
Skriven 2012-08-22 08:42:02 av Robert Bashe (2:2448/44)
   Kommentar till text 2710 av Ward Dossche (2:292/854)
Ärende: Twit list
=================
Ward Dossche wrote to Robert Bashe on Wednesday August 22 2012 at 00:42:

RB>> Your biggest mistake is judging Z2 by people like Michiel, Bjorn,
RB>> Torbjorn, Herman and the like. "Yes-men" like that don't give you a
RB>> true picture of the actual situation, and have more than once led to
RB>> the downfall of a would-be "great leader".

WD> Your mistake may be that you judge Z2 by what you know a little bit of
WD> R24.

Ward, you weren't even on the scene when I became a node in R24. Your good
buddy Ron Dwight, who helped us into several years' of intercine warefare that
except for a capable RC24 would have continued longer, was the "great leader"
at the time. And don't try the old trick of claiming the split in R24 was
strictly a local affair: everyone around at the time knew damned well that the
pressure for rigid lines of regionalization - totally impractical and expensive
in R24 - was coming from Ron himself. He did a great job of inciting
unnecessary dissent and damned near managed to destroy the region in the
process.

WD> Just a few months ago related to the missing RC24-matter you claimed
WD> that R24 had fallen asleep and none were caring about Fido.

Indeed, I was the first to point out that an RC who was unavailable and whose
system was regularly off line was not an ideal candidate for the job. It took a
while for others to accept that fact, but they did, and we now have reliable
communication in the region again. I might add that after the discussion
started, Werner himself asked to be relieved from his duties, as he no longer
had the time required to carry them out properly. Perhaps you didn't read Uli
Schroeter's comment to that effect.

WD> Now you paint a different story because 2 sysops have sort of reacted
WD> the way you wanted to.

Nice try. Everyone in R24 knows how unrealiable your system is, and that you
always either ignore suggestions for improvement or lauch personal attacks
against people who state the plain truth. Another problem you have, and that I
have long since pointed out to you, is that your system - as one of very few -
still sends out incorrectly dated messages that regularly land in my Y2K
logfiles. This is what my protected inbound looks like now:

10.08.2012  00:22               138 00001322.y01
03.08.2012  00:22               138 00001322.y2k
03.08.2012  01:05               216 00003902.y2k
10.08.2012  01:16               216 00004618.y2k
17.08.2012  01:24               216 00005069.y2k
10.08.2012  00:22               439 TK301000.BAD
03.08.2012  00:22               439 TK301001.BAD

All of this is from you. the *.BAD files are TICs for ARC archived nodediffs
(without the files having been delivered), all with CRC=0 (zero).

The Y2K program that traces such things gives me a nice log:

! 17 Aug 01:05:38 PKTD Pktdate Rev. 1.3 processing
D:\fido\inbound\prot\00003902.PKT (type: 2+)
! 17 Aug 01:05:38 PKTD Message #001 FTSC date: "03 Aug 112 00:58:48" fixed
(reason 1) to "03 Aug 12  00:58:48"
! 17 Aug 01:05:38 PKTD Message #002 FTSC date: "03 Aug 112 00:58:49" fixed
(reason 1) to "03 Aug 12  00:58:49"
! 17 Aug 01:05:38 PKTD Keeping a copy of the corrupted PKT as
D:\fido\inbound\prot\00003902.y2k for manual inspection.
! 17 Aug 01:19:35 PKTD Pktdate Rev. 1.3 processing
D:\fido\inbound\prot\00004618.PKT (type: 2+)
! 17 Aug 01:19:35 PKTD Message #001 FTSC date: "10 Aug 112 01:12:08" fixed
(reason 1) to "10 Aug 12  01:12:08"
! 17 Aug 01:19:35 PKTD Message #002 FTSC date: "10 Aug 112 01:12:09" fixed
(reason 1) to "10 Aug 12  01:12:09"
! 17 Aug 01:19:35 PKTD Keeping a copy of the corrupted PKT as
D:\fido\inbound\prot\00004618.y2k for manual inspection.
! 17 Aug 01:25:20 PKTD Pktdate Rev. 1.3 processing
D:\fido\inbound\prot\00005069.PKT (type: 2+)
! 17 Aug 01:25:20 PKTD Message #001 FTSC date: "17 Aug 112 01:19:56" fixed
(reason 1) to "17 Aug 12  01:19:56"
! 17 Aug 01:25:20 PKTD Message #002 FTSC date: "17 Aug 112 01:19:57" fixed
(reason 1) to "17 Aug 12  01:19:57"
! 17 Aug 01:25:20 PKTD Keeping a copy of the corrupted PKT as
D:\fido\inbound\prot\00005069.y2k for manual inspection.

Except for you, I haven't had anything flagged as a Y2K error in years.

So go right ahead, "big expert". But don't think your bluster is going to
impress anyone in R24. Facts tend to impress us more.

Cheers, Bob

--- GoldED+/W32 1.1.5-0613
 * Origin: Jabberwocky System - 02363-56073 ISDN/V34 (2:2448/44)