Subj : Weekly nodelist report on noteworthy changes (318)
To   : Nodelist Police Commissioner
From : Michiel van der Vlist
Date : Sat Nov 14 2020 10:49:54

Hello Nodelist,

On Friday November 13 2020 11:45, you wrote to All:

 NC> A new net:
 NC> Host,105,Oregon_Net,Portland_Or,Michael_Pierce,-Unpublished-,300,CM,IB
 NC> N:awesome.abon.us:24556,INA

I really wonder what inspired them to raise that net from the dead. "Elsewhere" I read this reborn net is to be populated from net 138, but that seems to be an error. It is repolulated from net 340.

Most sysops go into a flat spin at even the suggestion of changing node number, but the sysops from Oregon seem to see it as an outing...

Net 501 does not fir in the "modern" numbering system of (20xRegionnummber)+[0-19].

Net 340 is not unmanagebly big, so whay split it in two, because that is what it amounts to.

 NC> I think they used the previous version of this net as a base. Because
 NC> I know that Damon (which I have a link with) has moved at least 2
 NC> times since living in Portland. So they could have left out the Down
 NC> nodes.

The Down nodes come from net 340. I see no added value in moving moving Down nodes to another net. I'd say it is an opportinity to clear the dead wood...

 NC> And those empty INA's... :-(

It seems the new NC105 is still at the bottom of the learning curve. Lets give him a bit of time to do the climbing....

 NC> Node 7 connect with binkit, but doesn't present the correct aka:
 NC> 1:340/7 Node 10 connect with linux binkd Node 11 connect with
 NC> binkit Node 81 connect with linux binkd Node 82 connect with
 NC> binkit Node 1000 connect with Mystic, but doesn't present the correct
 NC> aka: 1:340/1000

The transfer is messy...


Cheers, Michiel

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

.