| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Feature request: PHN |
Hello mark, On Tuesday June 18 2019 17:53, you wrote to me: MV>> What you requested was that binkd could be configured tp transmit MV>> the information. "nodeinfo" can do that. All that is needed is MV>> that the sysops adds the iformation to the "nodeinfo" line in MV>> his/her binkd config. ml> that does not cause binkd to transmit a PHN line like other systems ml> do... how hard is this to understand???? :sigh: The PHN line obviously is a relic from the POTS age. The "phone" keyword in the config crearly indicate that it was meant for the phone number. Binkd is the leading binkp implementation. Instead of sheepishly following others it should lead. Progress is not just adding new stuff, it is also getting rid of archaic ballast. Binkd does not use phone numbers. The PHN line is archaic ballast. The makers of binkp were wise to ommit it. Using it for IP information is improper use. The proper place for IP information is the NDL line. That is were the capability flags are and IP info is conveyed as parameter in an IP related flag. Like this: nodeinfo CM,MO,IBN:fido.vlist.eu,RPK,NPK,ENC,NC,PING,IPv6 The PHN line is archaic ballast. IP info belongs in de NDL line. How hard is that to understand? Cheers, Michiel --- Fmail, Binkd, Golded* Origin: http://www.vlist.eu (2:280/5555) SEEN-BY: 103/705 154/10 203/0 221/0 1 6 360 229/426 230/0 240/5832 280/464 SEEN-BY: 280/5003 5555 292/854 310/31 320/219 396/45 423/120 633/0 267 280 281 SEEN-BY: 633/384 410 412 509 640/1321 1384 712/848 770/1 2452/250 3634/12 SEEN-BY: 5019/40 5020/1042 5053/58 @PATH: 280/5555 464 221/1 640/1384 633/280 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™.