| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | human-readable nodelist format |
>> erm... the current use of the "BBS Name" field in the currently used >> St. Louis Format (SLF) nodelist as a domain name instead of the system >> name is one such example of an alternative use... granted, its not >> being misused in what you are proposing or working on but it is a >> possibility that someone may do the same... ac> Field 3: Node name ac> FTS-5 = "This is the name by which the node is known" ac> FTS-5000 = "This is the name by which the node is known. For ac> IP nodes this field may alternately contain an ip address or ac> E-Mail address for email tunneling programs." ac> Nothing about a BBS name there. thank you! you've helped me in ways that we may not be aware of ;-) ac> Not that I even run a BBS, ac> but for people who do, why should they care about what's in ac> that field anyway? What difference does it make? Maybe the ac> ZCs can all mark the field with a big X for every node in ac> their zone. Then it would make the nodelist smaller for all ac> the people complaining about the nodelist being too big. Then ac> you'll get people whinging about how the nodelist is shrinking ac> and we're all doomed. So we're all doomed. hahaha... yup, as is birth is the beginning of death... )\/(ark* Origin: (1:3634/12) SEEN-BY: 106/2000 120/544 123/500 132/500 400/300 490/33 633/104 260 262 270 SEEN-BY: 633/285 634/383 640/954 690/682 712/848 771/4020 774/605 2432/200 SEEN-BY: 3634/12 @PATH: 3634/12 106/2000 123/500 774/605 633/260 285 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™.