Text 3972, 124 rader
Skriven 2012-09-13 23:05:00 av Roy Witt (1:387/22)
   Kommentar till text 3867 av mark lewis (1:3634/12.0)
Ärende: Pvt nodes vs points
===========================
11 Feb 36 15:09, mark lewis wrote to Roy Witt:

 ml>>> this one is basically backwards...

 RB>>> May be, but it exists. That's the point of what I wrote above.

 ml>> has anyone contacted that NC and pointed out that it is backwards?

 RW>> Frankly, it shouldn't present a problem. IBN denotes that the
 RW>> system does BINKD, and in this case uses port 24555 instead of the
 RW>> normal port.

 ml> INA comes before that which it serves...

Not according to the notes at the bottom of the nodelist. IBN is listed
first among those flags. INA is listed last...if they need to be in a
certain order, then the description of where they go should be included or
at least list them in order of appearance in a nodelisting. Without
referring to some remote document nobody other than a FTSC member can
name, one should be able to rely on the info provided here.

If that's incorrect, then it's no wonder people are using flags in a way
that isn't called for.

 ml> it states this in the usage... in the example given, properly written
 ml> software will do a f.n.z conversion

Fuck that f.n.z shit. Its not needed.

 ml> of the address and then contact that way... the INA flag will be
 ml> ignored...

Somebody should inform the zone nodelist clerk of this. No wonder some of
the software doesn't work as it should.

 RW>> It should list the port after the INA: address with a | to indicate
 RW>> that port...as in INA:wueppel.doene.de|24555 -

 ml> this is not right... what if there are ITN and IVM protocols also
 ml> used?

Not my problem, just stating it as the INA flag instructions in the
nodelist state it.

;S   INA - Place to list a Fully Qualified Domain Name Or Static IP
;S         Address, to be followed by applicable protocol flags
;S         offered.   Usage:  INA:<somedomain.com>|<x.x.x.x>

According to this, that nodelisting is on the money except that the port
is listed in the wrong place! A different port number is an 'applicable
protocol flag' if I've ever seen one.

What's up with that?

 ml> they do not work on that port...

Correct, and neither does email, which is listed after the appropriate
flag IEM...but there is no implied requirement to some of these flags
because the protocol used is self explanatory. Like IBN, IFC, ITN, IVM.
etc., etc..

But the stupidity goes on and calls for a port listing thus in the case
of the ITN flag; "If the port is not 21 then the port number must be
placed after the ITN flag (ITN:60177) in the example given) if the Telnet
address is part of the ITN flag (eg ITN:farsi.dynip.com) then the port
number should be last (eg kraut.dynip.com:60177) always remember that the
flag cannot exceed 32 chars total."

Perhaps this is where the NC or sysop got the idea of using the BinkD port
listed with the IGN flag...

I like the idea of listing the internet address in the BBS field because
that places it where it can easily be found by both human and robot and
doesn't interfere with the use of a flag as intended. And the excuse given
that a BBS no longer has a place to list itself, well?

Having to look at a bunch of flags for a internet address is stupid, when
those flags can be used to list a port other than the default port for a
protocol if it's called for.

 RW>> IBN should still be in the listing though.

 ml> agreed but /after/ INA so that IBN will use the INA specified
 ml> domain...

That's not per the description called for in the nodelist notes.

 ml> and IBN should also contain its :port portion since that IBN is not
 ml> on the default port...

Not according to the notes with ITN...the port should be listed with the
IBN address...

 ml>> it may actually not matter, though, if there is a f.n.z DNS record
 ml>> for that node that points to the proper IP address ;)

 RW>> Jesssusss! Here we go with that f.n.z. crap again. Fuck that shit,
 RW>> don't bring it up again in my presence.

 ml> THEN DO NOT USE BINKD AT ALL! PERIOD! not even in DB!

I'd rather not have to get into that shit.

 ml>  f.n.z is built into binkd and there is NO getting around it...

Wanna bet? Read what Nick says about that usage. It will be ignored and
not used in v3.83 of DB...

 ml> your damned software and DO NOT bitch at ME when i point out how it
 ml> REALLY fuckin' works and i open your eyes to what is REALLY going on!

I'll believe what the author of that program says, not anyone else's.
Whether yours is the proper iteration or not.

                R\%/itt


... Mark Owen: "Hey, did you ever hear anything about that beer?
... Fellow SEAL: "You believed that shit, I bet you voted for change too,
... SUCKER."


--- GoldED+/W32-MSVC and D'Bridge 3.82
 * Origin: Lone Star Unit - Gulf States Backbone  (1:387/22)