| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: NodelistGuide or FAQ |
*** Quoting Steven Horn from a message to Russell Tiedt ***
RT> Will do, but the idea is to beat out an unambiguous FAQ, that
RT> clearly states how it is to be done, distribute as widely as
RT> possible, and when people ask, point them to it, one standard
RT> document. With no FTSC at present, we need to somehow inform the
RT> "ignorant" of their non-compliance.
SH> But under whose authority is the FAQ issued? Rick van Ruth tells me m
SH> ION listing is non-compliant but it was devised by my RC with input fr
SH> me and works like a charm. Why should I change it?
Not everyone knows everything. I for sure do not. The problems your
nodelist ¨entry has doesnt affect you directly, but can affect others
outside your zone ¨or within it.
People generally trap out 000- numbers but they may not catch 1-000
numbers. ¨The country code needs to GO. Generally when some of the
argumentative Z2 ¨sysops (or Z3) complain about 000- entries they really do
not have proper ¨blocking or are afraid somehow. Most such entries are not
actually dangerous. ¨Yours actually is possibly dangerous in that it can
lead to someone outside the ¨USA (or within it) trying to dial you. 1-000-
isnt blocked by many. They ¨wouldnt think to add it to their block set.
Look, anyone who knows me knows I'm not a nodelist 'copper' but this one
¨catches even me.
xxcarol
--- Telegard v3.09.g2-sp4
* Origin: SHENK'S EXPRESS, Sasebo Japan 0956-25-2561 (6:757/1)SEEN-BY: 106/2000 120/544 123/500 140/1 633/260 262 267 270 285 634/383 SEEN-BY: 640/954 654/0 690/682 757/1 771/4020 774/605 2432/200 7105/1 @PATH: 757/1 140/1 106/2000 123/500 774/605 633/260 285 |
|
| 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™.