Text 2475, 52 rader
Skriven 2008-03-29 14:53:14 av Carol Shenkenberger (798.ftsc_pub)
   Kommentar till text 1808 av Michiel van der Vlist (2:280/5555)
Ärende: MakeNl_Ng
=================
    
 >  JK> Understand :) The needs in Zone 3 are very different, and it's
 >  JK> understandable that they need to use Pvt,Unpublished there.
 > 
 > Apart from the fact that obviously Z3 does nkt need Pvt - they use a nodelis
 > that has -Unpublished- without Pvt - as a sysop of a FidoNet node, I say tha
 > if -mind the if - if they have different needs, the problems can not be solv
 > by applying different standards to  different segments of the nodelist.

Unfortunately the situation in Z1 no longer allows for removal of ION NC and
RC with replacement by others who still have a POTS line.  (reminder to self,
find that dang power module and put the good modem on!  Some cant get a clean
connect to the #%@^ that ws inbuilt here on the box).

Removal of the ability to support that at this stage of the game, essentially
crashes and removes Z1's ability to operate or recover.  Z1 simply can not
function without a clean way to list ION's in any RC and below capacity.  Z3,
which never allowed that, works out it's internal listing 'by agreement' and
it's best to not say more there unless one of them wants to fill you in ;-)

So you end up with the problem that Z1 needs some changes in order to better
support what others want, yet still maintain internal operational capability.

The optimal solution first was get some sort of standard in use in Z1 (done
though I havent peeked to see if there arent discrepancies which there
probably are).  Then, work to removal of the 000- set in a way that works
well enough for all yet maintains the internal ability Z1 has now.

We've had some progress.  Now to work out the rest.

To swap messages slightly, you have the 'ina-tool.exe' Idea I postulated. 
That was framed in what the military calls 'an operational requirement'
language.  IE:  I gave what i percieved the end tool to need to do and left
it to others to work out implementation coding.  What i percieve is your
simple tool, might do what is needed, may need some additions (flags to say
where I want the INA data to go).  I could also see a command line sort of
like 'ina-tool /3 /6' (meaning put the INA data in field 2 and 6>.  Maybe use
- vice / as the / can be a confusement on *NIX machines.

That sort of tool could be used right now.  No nodelist format changes
required.  Might be really useful for other needs such as my Argus or my
Dbridge (not implemented, will be one day but taking my sweet time of
swapping off argus).  I might for example want to use it locally on my system
to shift INA data to field 3 then compile that with dbridge to solve why it
doesnt want to automatically pick up on Janis and BinkP her.

It;s more than just solving a few Telnet setups for FD/(IM?) systems.

            xxcarol

--- SBBSecho 2.12-Win32
 * Origin: SHENK'S EXPRESS telnet://shenks.synchro.net (1:275/100)