Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 2224  |
|  Paul Hayton to Jeff Smith  |
|  Re: Seen-by lines  |
|  01 Apr 19 20:11:38  |
 TID: Mystic BBS 1.12 A43 MSGID: 3:770/100 cebb7442 REPLY: 1:282/1031.0 f7d89ff6 TZUTC: 1300 On 01 Apr 2019 at 12:09a, Jeff Smith pondered and said... JS> The problem as I see it is that the net needs to be specified at the JS> beginning of each line to indicate which net the following nodes belong JS> in. Until a new or different net is specified. The same principle is JS> true and used in the setup of many pieces of FTN software. JS> JS> I would surmise that the Seen-By lines are not looked at as one JS> continuous line but as separate sequential lines. And therefor the net JS> specification would need to be specified at the beginning of each line. Hi Jeff Yes Mark has basically said the same thing. I have sought clarification in the FTSC echo in an attempt to find some documentation that confirms this. Perhaps it's a case of some FTN software looks for this whilst others do not? Best, Paul --- E:avon@bbs.nz ------ W:bbs.nz --- --- K:keybase.io/avon -------------- --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32) * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100) SEEN-BY: 15/2 57/0 103/705 123/1970 153/250 154/10 203/0 221/0 226/17 SEEN-BY: 226/100 229/107 354 426 452 1014 240/5832 249/206 317 267/800 SEEN-BY: 280/464 5003 292/624 854 317/2 3 322/757 342/200 393/68 396/45 SEEN-BY: 423/120 712/848 770/0 1 10 100 330 340 772/0 1 500 2452/250 PATH: 770/100 1 280/464 229/426 |
[ << oldest | < older | list | newer > | newest >> ]