Text 21883, 78 rader
Skriven 2011-08-22 12:50:49 av mark lewis (1:3634/12.0)
  Kommentar till text 21707 av Robert Bashe (2:2448/44)
Ärende: BinkD data in the nodelist
==================================
 RB> In Z2, the binkd-capable systems have listings like:

 RB> ,44,abel.dnsalias.net,Datteln,Robert_Bashe,49-2363-56073,9600,CM,XA
 RB> ,MO,V34,V42B ,V110H,X75,IBN,U,ENC

 RB> That's me, and as you see I have everything packed into one number:
 RB> binkd, analog and ISDN.

the problem with this is that legacy software doesn't know to look in the bbs
name field for the domain name and they cannot be made to do such...

 RB> In Z1, the procedure appears to be different.

 RB> ,23,Temp_Fidonews_Editor,Windsor_NY,Janis_Kracht,1-607-655-5652,960
 RB> 0,CM,XX,H16,
 RB> V32b,V42b,V34,V32T,X2C,INA:filegate.net,IBN,IBN:24555,IFT,ITN 

 RB> That's Janice. The IBN flag is there, as is the domain, but they're
 RB> in a different place.

this one has a bbs name and a domain name... they can, in fact, have multiple
domain names... one for different services... you'll note there are two IBN
entries indicating that the system has binkp on the standard port as well as on
another port...

 RB> ,303,lionsden.darktech.org,Trenton_ON,Joe_Delahaye,1-613-392-8896,9
 RB> 600,CM,XA,V3 2b,V42b,VFC,INA:lionsden.darktech.org

 RB> And That's Joe. But without the IBN flag.

IBN is not a default... in fact, the above doesn't really indicate that there
is any internet connection capability other than there being a domain name...
no internet protocols are indicated at all...

 RB> Now, I use a program called IPROUTE (v. 1.25, no newer versions
 RB> available) by a fellow called Volker Imre, which is set up to scan
 RB> the nodelist for binkd-capable nodes and make up an "include" file
 RB> to add them to binkd.cfg (since binkd doesn't use the regular
 RB> nodelist). This program works fine with nodelist entires like mine
 RB> above, but I have to add nodes like Janis and Joe manually if I
 RB> want to send them a netmail with binkd.

try the same task with a legacy mailer like frontdoor which can only operate
over ITN (telnet) and IVM (vmodem)... it is a huge PITA and we have several
conflicting methods in place... why? because several wanted their method to be
used, others wanted their own and no one could or would agree on anything...
couple that with the mainstream developers leaving for various reasons and you
end up with a bucket of foul stew that no one knows how to eat :?

 RB> What, if any solution, would cover _both_ types of listings? What
 RB> do people in Z1 do in such cases, do they have something like
 RB> IPROUTE - or do they also add nodes manually to their binkd.cfg?

i don't know but i really do wish that folk would stop trying to throw legacy
software and systems out with the bathwater... they are causing unnecessary
problems, strife and resentment...

 RB> It would be ideal if binkd were capable of using a regular
 RB> nodelist, but I haven't seen anything indicating that, or work on
 RB> such an add-on. 

i'll not comment on this because i do not want to ruffle any feathers again
like i did several years ago...

 RB> P.S. The situation doesn't appear to be uniform even inside Z1. I
 RB> just looked at my "include" file generated by IPROUTE and found the
 RB> following Z1 nodes: 

the worst problem is with the various methods and *Cs who don't know about them
as well as those same *Cs having to place this information into the nodelist
somehow... looking at that list you gave, i'll hazard a guess that they are all
running the same mailer/bbs software and that it/they recognize and work
properly with those entries whereas no other software does... so, here is yet
another method that has been introduced :(

)\/(ark

 * Origin:  (1:3634/12)