Subj : Re: IP only nodes with ICM flag
To   : Michiel van der Vlist
From : Dan Clough
Date : Sat Oct 11 2025 10:01:40

-=> Michiel van der Vlist wrote to Dan Clough <=-

 DC>> Firing people and *trying* to replace them may fix everything.

 MvV>> That's the wrong order. Replacements have to be found before
 MvV>> firing the ones in position.

 DC> No, they don't.  You lose nothing by firing non-existant people.  Fire
 DC> them and then offer the job to someone.

 MvV> That does not work in Fidonet where jobs are linked to a chalm in a
 MvV> technical chain. Removing a region entry or replacing it with a
 MvV> non-functional dummy will break the nodelist.

It's already broken.  What would removing non-existant nodes/nets hurt?  
They're already not reachable.  Rather than break the nodelist, this 
would bring it closer to being correct/accurate.  Isn't that the goal?

 MvV>> Fixing the problem of a disfunctional RC is obviously the job of
 MvV>> the ZC.

 DC> Yup, as I said.  But he does nothing, as usual.

 MvV> That you do not see it does not mean it is not there.

Well, how long has this RC been disfunctional?  Seems like it's been 
quite a long time to me.  What corrective actions has the ZC taken that 
I can't see?

 DC> Perhaps he's the one that needs to be fired.

 MvV> Firing the ZC does not solve the problem of a non functional RC.

It might, if the replacement ZC fired the non functional RC and replaced 
him.

 MvV>> I was just pointing out the hurdles in this particular
 MvV>> situation. Maybe the ZC could place the region in custody. For
 MvV>> starters he could remove the nets that are obviously dead. (4614
 MvV>> and 4624)

 DC> Sure, except for the fact that the ZC doesn't do his job.

 MvV> Ever heard of silent diplomacy?

Sure, it's another one of those non-functional idealogical fantasies 
that doesn't actually work.  It also takes forever, and in the end 
nothing changes, it just takes..... forever to know it.

 MvV>> And move Moldova (net 469) out of region 46. It is not enirely
 MvV>> dead. The host is gone but 469/122 is still on-line. He could be
 MvV>> moved to Region 56. (Z2 catch all)

 DC> Sure, except..... well, you know.

 MvV> No, I do not know.

See above regarding "the fact that the ZC doesn't do his job".

 DC> I am just pointing out that there are TWO problems here - a
 DC> non-existant RC, and an (effectively) non-existant ZC.

 MvV> ZC2 exists and responds to netmail.

Perhaps, but would you agree that there's more to the ZC job than simply 
responding to netmail?

Do you think if I netmailed him, he could explain the 2:2/29 nodelist 
entry that he doesn't fix?  Can YOU explain that one to me?


 

.... So easy, a child could do it. Child sold separately.
=== MultiMail/Linux v0.52
--- SBBSecho 3.29-Linux
 * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)

.