| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: RFC type packet format thoughts |
PLEASE DELETE ME FROM YOUR MAILING LIST I DON;T KNOW WHOYOU ARE!!!
On Sunday November 17 1996, Mark Lewis said to andrew clarke:
ML> BTW, this "origin line doesn't immediately follow it" is not a
ML> valid technical statement. No spec guarantees that. No spec
ML> even says they come in that order. Just more of the mess.
ML> BFN. Paul.
ac>> In echomail, have you ever actually seen a tearline that didn't
ac>> come immediately before an origin line?
ML> yep!! there are some programs out there that are derived from other
ML> networks and how they work. one such network is the RIME/PCRELAY
ML> network. in that network, the tearline is above all program notices,
ML> taglines, fluff and stuff...
ML> ie:
ML> --- Msged/2 4.00
ML> fred, somesite
ML> ... taglines are wasteful and should be torn off with other
ML> garbage.
ML> * OFFLINE! QWK door
ML> # Origin: another net in another place (100:3/42)
ML> (3:635/728.4{at}fidonet)
ML> the above is a perfect example of what the tearline was originally
ML> designed for... originally as in the first person to come up with it,
ML> not as in used by this network...
ML> here in fidonet, i do see the following style as well...
ML> --- Msged/2 4.00
ML> + OFFLINE! QWK door
ML> (3:635/728.4{at}fidonet)
ML> in other words, with fido's anarchistic methods of development, the
ML> tearline doesn't mean caca... if the original use of the tearline had
ML> actually been kept in it's implementation, we wouldn't have the
ML> tearline discussions that we are having today.
ML> )\/(ark
Andrew Clarke
--- Zeus BBS 1.1
ML> * Origin: Blizzard of Ozz, Melbourne, AustraliaML> * Origin: Blizzard of Ozz, Melbourne, Australia * Origin: Metnet-10 lines bbs. Free Internet-web/ftp. 01482 442251 (2:2502/129.0) SEEN-BY: 13/13 37/100 50/99 102/735 105/103 119/88 129/11 138/146 153/800 920 SEEN-BY: 157/586 200/204 201/505 203/512 992 204/200 209/720 7211 239/1 SEEN-BY: 260/742 261/1137 270/101 102 103 104 211 272/160 280/1 801 282/4073 SEEN-BY: 283/657 292/511 876 320/119 321/1 332/1 334/201 341/70 1002 344/3 SEEN-BY: 345/12 348/105 362/37 367/1 385/100 387/31 396/1 402/311 403/150 SEEN-BY: 405/0 406/100 430/105 440/1 600/348 620/243 626/660 632/348 640/206 SEEN-BY: 640/305 820 821 822 823 700/101 711/409 410 413 430 808 809 934 SEEN-BY: 712/515 713/317 724/10 800/1 2002/2002 2430/1423 2433/225 2601/100 SEEN-BY: 2602/100 2604/104 2613/5 2624/306 2630/1001 3401/308 3611/18 3615/7 SEEN-BY: 3615/50 3838/1 7104/2 @PATH: 2502/129 1000 442/403 255/1 250/107 254/153 106/2000 396/1 270/101 @PATH: 209/720 640/820 711/409 808 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™.