| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | An political question |
HS>> Then its not a normal reply and you should not add a REPLY line if HS>> there was a REPLY pointing the Originator - the "other guy". ML> i think that you are confusing the fact that 'reply' as used in ML> FTS-0009 is used simply to mean 'a message that is "based" on another ML> message' I am not confusing nothing. My interpretation on how to use a REPLY TO OTHER GUY usage of FTS-9 does not break the addressing sequence, while the others do. Which is better? Its easy Mark. Just do normal replies to a Message. Have everyone do a normal reply and have a long thread with NO one doing a FOLLOW UP. In each and every message, no matter how deep in the Tree Level you go, the addressing is always correct and the MSGID always points to the messag author and the REPLY points to the other guy. Now how come when you do a "REPLY TO OTHER GUY" should this logic and perfect addressing logic break? Whats the REASON? For what PURPOSE? Sorry, hey, SX was the first off-line reader to do FTS-9 in both directions. Addressing was very important so I was able to see this first. Blue Wave, as I am finding out, does not support FTS-9 so it doesn't count. Sysop editors have the nodelist in front of them so they can easily and automatically check an address, but as I pointed out to Matt, that logic breaks for Points. ML> it seems that you have totally forgotten about JAM message bases and ML> their threading... JAM relys on the MSGID/REPLY control lines to link ML> replies of any type to the original... yes, when the original is purged ML> from the base, then threading is 'off' a bit but only in that you can't ML> get to the original... you can still go from one reply to another... Its off a bit? Its always off. Come on Mark, You know you can rely on threading and it certainly doesn't work across the board in general, what happens when JAM based is exported to a PCBOARD base or a HMS based or that base, etc. Its totally useless and if you use the BLUE WAVE reader to reply, JAMS's reply system goes out door because the REPLY line is lost. ML> RA, TimED, MKREADER, GOLDED, ALL the packages that use JAM and follow ML> FTS-0009 do it the same way... even _old_ versions of the software that ML> didn't worry about linking on them used them in the way described... Well, I am confident if they were PRESENTED with a REPLY TO OTHER GUY concept, and shown that their "Reply to OTHER guy" concept breaks ADDRESSING, they might reconsider what they are doing. I am sure they simply didn't see it and I see now others here didn't either. RA doesn't have a REPLY to other guy concept anyway. As I said about, ADDRESSING stays in intact for normal replies. Why break it when you do a "REPLY TO OTHER GUY"? --- Platinum Xpress/386/Wildcat! v1.2f* Origin: Xpress Tech Support BBS * 305-248-7815 (1:135/382) SEEN-BY: 10/8 13/13 50/99 78/0 90/90 102/735 103/2 104/821 105/103 107/411 SEEN-BY: 123/1 129/11 138/146 147/76 153/800 920 157/586 161/55 167/92 SEEN-BY: 200/204 202/1207 203/15 206/2711 209/720 218/801 239/1 245/6910 SEEN-BY: 251/12 261/1137 267/200 270/101 102 103 104 272/82 280/1 282/1 4073 SEEN-BY: 283/657 292/876 320/119 325/118 328/104 332/1 334/201 340/20 341/70 SEEN-BY: 342/12 345/12 346/49 348/105 353/211 353 362/37 367/1 369/110 380/25 SEEN-BY: 385/100 387/31 396/1 403/150 405/0 406/100 430/105 600/253 348 SEEN-BY: 620/243 626/660 632/348 640/201 206 217 305 820 821 822 823 690/660 SEEN-BY: 700/101 711/409 410 413 430 808 809 934 712/515 713/888 721/117 SEEN-BY: 724/10 800/1 2430/1423 2433/225 2490/3001 2604/104 2605/606 2613/5 SEEN-BY: 2621/100 2624/306 3401/308 3412/1114 3615/7 50 3619/25 3653/777 SEEN-BY: 3805/3 7104/2 7877/2809 @PATH: 135/382 292 992 3615/50 396/1 270/101 209/720 640/820 711/409 808 809 @PATH: 711/934 |
|
| 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™.