Text 3361, 102 rader
Skriven 2012-09-13 10:25:04 av Robert Bashe (2:2448/44)
     Kommentar till en text av mark lewis (1:3634/12.0)
Ärende: Pvt nodes vs points
===========================
mark lewis wrote to Robert Bashe on Wednesday September 12 2012 at 13:35:

RB>>> Yes, but the problem was that the domain is listed differently in
RB>>> various systems.

ml>> how is that a problem??

RB>> As described. I simply do not believe that _all_ the various methods
RB>> of listing domains will be covered by such a "selection" program.

ml> dude... there's only two or three places that the domains can be
ml> listed...

"Dude" - that was exactly my point. Why not agree on _one_ place and make
things easier for everybody?

RB>>> ,290,Wueppel-BBS,Merzenich,Doris_Schmitz,49-2421-981180,9600,MO,C M,
RB>>> XA,V32B,V34, X75,IBN:24555,INA:wueppel.doene.de

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?

Whose job is that? If someone has problems contacting the node, they'll
complain. I don't go running around checking the nodelist for proper usage just
because I have nothing else to do. Note that I found this example by pure
chance, just glancing through the nodelist.

RB>> And my comment about agreeing on a _binding_ method of including
RB>> domains in a nodelist entry stands. In my opinion, that would be the
RB>> key to preparing a really reliable "include" list for binkd.

ml> there is a "binding" agreement... it is detailed in the FTS document
ml> describing the nodelist...

And then you remark that there are multiple places where a domain can be
entered in the nodelist. A "binding agreement" to do what you please isn't
exactly what I had in mind.

RB>> To be frank, after putting up with Bjorn Felten and Michiel van der
RB>> Vlist, I'm getting a little sick of this nit-picking when someone
RB>> unintentionally (or in Bjorn's case, because of the impracticality of
RB>> using high-ASCII characters in fido messages) misspells a proper
RB>> name.

ml> i did say "please" and i didn't get mad...

OK, my reaction was exaggerated. I told you why the confusion occurred and now
add that I've had quite a bit of stress with sick/lost pets and other negative
matters over the period since Good Friday of this year. It's been a rotten year
for me and sometimes that shows through.

ml>> it is even moreso not required with the f.n.z conversion that is
ml>> default...

RB>> Assuming anyone knows what domain that's supposed to go to.

ml> i've been telling folks and the binkd guys have as well since they are
ml> the ones handling that stuff... unfortunately those using other
ml> software that can't change the base domain for f.n.z lookups have a
ml> problem... all lookups of *.fidonet.net return the same IP number...

The binkd.cfg I got with my copy, admittedly a while ago, includes:

domain fidonet \\fido\\outbound\\fidonet 2
domain fido alias-for fidonet
domain fidonet.org alias-for fidonet

Most people, like me, will simply accept that without change. Now tell me if
fidonet.org still exists and is operative.

ml>> ... in fact, with so many folks using binkd and the f.n.z
ml>> conversion...

RB>> Binkd yes, the f.n.z. conversion absolutely no. Maybe where you are,
RB>> certainly not here.

ml> binkd has it built in and uses it even if you don't... to be more
ml> specific, it uses it each and every time there's a connection and the
ml> AKAs are presented... you cannot prevent that... it /is/ used, period!

May be, but you still can't contact anyone with binkd without specifying a
domain in the configuration or an "include" file. If you can, it'd be new to
me.

ml> i keep telling you this but you refuse to accept it :sigh:

As you refuse to accept that PVT nodes are essentially identical to sysop
points unless the PVT node (as here) includes a domain to allow it to be
crashmailed ;-) We all have our problems.

ml> [why do i try?]

I sometimes have the same feeling. If it gets too stressful, forget it.
Otherwise try to keep calm. I don't always manage that either ;-)

Cheers, Bob

--- GoldED+/W32 1.1.5-0613
 * Origin: Jabberwocky System - 02363-56073 ISDN/V34 (2:2448/44)