Subj : Weekly nodelist report on noteworthy changes (290)
To   : Andrew Leary
From : Michiel van der Vlist
Date : Sat Oct 17 2020 14:49:14

Hello Andrew,

On Saturday October 17 2020 01:36, you wrote to me:

 MV>> That may be, but how do you explain this response by 1L320/119 to
 MV>> my ping to 1:320/319

 AL> Same issue.  Apparently the nodediff didn't get processed on 1:320/119
 AL> until after your ping came through.  I just checked and it's now on
 AL> NODELIST.290, so another attempt should work fine.

I send another ping to 1:320/319, routed via 1:320/119. Time 08:11 UTC.  No bounce this time, but over four hours after the fact no Pong from 1:320/319 either. Also no trace from 1:320/119. You use O-T/Track for the bounce, so it is a reasonable assumption that you use O-T for the Ping as well. I don't use O-T any more, apart from the fact that it is 16 bit abandonware, it does not cooperate well with BSO. But in the past, I managed to make it Ping, but never Trace.

It seems for historic reasons that I route mail for you nick of the woods via 1:320/119. That must be a remnant from time that 119 was your only listed node number. I will change the routting to go via 1:320/219 and try again. Later I will try a direct connect with 319.

As an aside... You still use diffs? I was stopped using diffs ages ago. I use the full sized lists. I do make the diff available fir anyone interseted, but there are no takers.
Also I do not use the weekly nodelist. I use Z2DAILY and DAILYUTF for anythng needing a nodelist. Uncompressed. Binkd does fine with its internal compreesion...

Ping to 1:320/319 routed via 219 timed 12:47 UTC


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
 * Origin: Nodelist Police Station (2:280/5555)

.