| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | An political question |
ML>> then why tell me to fix my software (left quoted above> ? HS>> Because you LET a DUPE get out!!! ML> maybe someone upstream from you had to retoss the PKT that that message ML> was in? Whatever, it came from your system! Its still a dupe! ML> you may be 'right' as far as addressing is conerned but you are ML> DEFINITELY =WRONG= when it comes to using FTS-0009 for addressing... ML> you are also wrong about me not authoring any software... you don't ML> know what i have out there ;) Well, if its UNKNOWN, its useless. And as far as being wrong for FTS-0009, i am not, because NOTHING in FTS-9 says it is NOT for ADDRESSING. So please STOP instigating the IDEA that FTS-9 is NOT for ADDRESSING. It doesn't SAY that in FTS-9 and you are creating an ATMOSHPERE for future developers to BELIEVE that ok's to put ANYTHING in that FIELD. ML> then what FIDONET standard or proposal are you (going) to use for ML> this?? FTS-0009 =PLAINLY= states what it is for... Message ML> Identification and Message Linking... nothing else... Thats right, it says MESSAGE IDENTIFICATION!!!!!!! It says its a way for AN AUTHOR TO IDENTIFY the MESSAGE to WHICH HE WROTE, NOT WHAT YOU WROTE or the OTHER GUY WROTE, BUT WHAT HE, THE AUTHOR, WROTE!!!!!! That way by IDENTIFYING THE MESSAGE, I CAN CONTACT THAT PERSON, NOT or in the FUTURE without ANY CONCERN for TIME!!!!!!!!!!!!!!!!!!!!!! It WORKS 100% of the TIME.......until YOUR FOLLOW UP INTERPRETATION comes into play. ML> do what you want to, hector... you always do... however, i suggext that ML> you also make them aware of what the standard you are butchering really ML> says... if you don't, others will and once again, your software will ML> come out looking on the bad side of things... BS. I am not butchering FTS-9 and YOU CAN'T PROVE that I am. The end result, is that if you do a REPLY with my software, the NEXT guy, THE WORLD, will still be able to CONTACT an INDIVIDUAL. WIth your SOFTWARE, it will NOT happen. In the END, the END USERS will see that what works BEST is correct and they will NOT understand your REASONING for breaking an address. ML> you still haven't corrected your software to stop violating FSC-0046 ML> and that's been over a year ago that you were specifically notified... What are you talking about? your GECHO corrects it for me by tampering with the email system. ML> i'm not going to alter the way any of my software uses FTS-0009. What software? You ain't got no software HS>> How far you do you want to take this Mark? ML> the question is how far do you want to take it... you are wrong in your ML> use of FTS-0009 and you are trying to justify it with this addressing ML> argument... i suppose you tell the policeman that you are hungry and ML> that that gives you the right to exceed the speed limit while going ML> home, eh? it's the same argument... Thats a Paul Edwards jello brain analogy. But let me correct it for you: "But officer, look at the street sign?. Do you see it was TAMPERED? Some kids turned the direction around. It use to point that way, now it points this way." The officer will say.... "your right.... Luckily you didn't follow the sign, otherwise it would lead you in the WRONG direction and COST you money (fido-bucks)" No, YOU ARE JUSTIFYING A BAD ADDRESS FOR MAKING JAM THREADING WORK ON YOUR BBS ALITTLE BETTER. You are selfish and you are sacrificing the GOOD of the electronic mail world for your broken chaining logic. --- Platinum Xpress/386/Wildcat! v1.2j* Origin: Xpress Tech Support BBS * 305-248-7815 (1:135/382) SEEN-BY: 10/8 13/13 37/100 50/99 78/0 90/90 102/735 103/2 104/821 105/103 330 SEEN-BY: 107/411 123/1 129/11 138/146 153/800 920 157/586 161/55 167/92 SEEN-BY: 200/204 202/1207 203/15 512 206/2711 209/720 218/801 239/1 245/6910 SEEN-BY: 261/1137 267/200 270/101 102 103 104 272/82 280/1 801 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 344/3 345/12 346/49 348/105 353/211 353 362/37 367/1 369/110 SEEN-BY: 380/25 385/100 387/31 396/1 403/150 405/0 406/100 430/105 600/253 SEEN-BY: 600/348 620/243 626/660 632/348 640/201 206 217 305 820 821 822 823 SEEN-BY: 690/660 700/101 711/409 410 413 430 808 809 934 712/515 713/888 SEEN-BY: 721/117 724/10 800/1 2430/1423 2433/225 2490/3001 2604/104 2605/606 SEEN-BY: 2613/5 2621/100 2624/306 3401/308 3412/1114 3615/7 50 3619/25 SEEN-BY: 3653/777 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™.