| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | human-readable nodelist format |
>> Mainly leting a node have multiple addresses (since many do) and >> thus saving repeating the same node with the same connection info >> and thus make the nodelist easier to maintain? ac> I don't see any reason why a single node shouldn't be able to have ac> multiple connection methods listed in a new format nodelist. I agree, what I'm suggesting is where one physical fidonet system has multiple fido addresses (eg as an NC and as a regular node) they could somehow list both addresses in the single nodelist record. in the current nodelist you see some entries where the same system is listed twice because they can't fit everything the want on a single nodleist line. OTOH I guess they could just list the other addess as a preferred uplink and that'd probably do most of what's needed. -=> Bye <=- ---* Origin: Misery loves company, but company does not reciprcate (3:640/531.42) SEEN-BY: 120/544 123/500 132/500 400/300 490/33 633/104 260 262 267 270 284 SEEN-BY: 633/285 634/383 640/531 954 1674 690/682 712/610 848 713/615 771/4020 SEEN-BY: 774/605 800/1 2432/200 @PATH: 640/531 954 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™.