| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Immediate Action Require |
PL>PL>> will prevent the new node from ever sending the node application.
PL> CS> NC's are not supposed to block unlisted nodes. Thats a primary 'do
PL> CS> not do that' thing many NC's got stupid about and did anyways.
PL> CS> NC's have to be unblocked so as to accept new nodes.
PL>I was bringing up a hypothetical... my system is not listed
PL>as LO, nor ever has been since I've been NC here, and you
PL>know that.
Yes, and my reply was to those who do run LO (only reason technically
for adding a 9999 listing, but some others do it out of net tradition
they were 'raised with').
PL>The responses other than "this should not do that, or that should not
PL>this" so far have been insufficient reasons for not actualy
PL>allowing listings in nets of the 9999 listing, other than
PL>bullshit claims that hold no weight.
PL>JEEZE. If it's a matter of the size of a nodelist that
PL>bothers everybody (and I don't see how it could) as in the
PL>old days, and if I see the typing of "bandwith" one more
PL>time (it just may make me crazy), I just may go over the
PL>edge!!!!
Grin, has nothing to do with size of nodelist either. More like just
extra un-needed junk is all. If the NC isnt running LO, its a harmless
cosmetic fluff that gives neither benefit nor harm.
xxcarol
___
þ OLX 2.2 TD þ MSI - Connecting The World In '94
--- Maximus/NT 3.01
* Origin: Owl's Anchor (1:261/1466)SEEN-BY: 633/267 270 5030/786 @PATH: 261/1466 123/500 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.