| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | 4x16meg Simms 4 Sale |
PE> If you don't follow the spec, it doesn't actually matter PE> a toss what happens, that's a problem with buggy software. Corse it matters. The most obvious situation is where you have two alternative algs, one which can reliably work out what the message is with the vast bulk of common warts you can see, and the other which is more fragile. What the fuck is the point of mindlessly just binning other than utterly pristine messages ? None, thats what. The real world is about robust software, not assuming absolute perfection. PE> Same as if the origin line is stuffed and the address is invalid. And if you just want to read the message, you may not actually give a damn. Even for echomail, the address also doesnt actually matter a stuff either. PE> It doesn't matter your end, it's the originator who needs to fix PE> his software, not you. A grunged message is a grunged message. And it may well make considerable sense to be able to handle those gracefully, particularly ones which only have minor blemishes. For example a 3D SEEN-BY doesnt actually matter a stuff to an end node, its not even used. Just plain stupid to fall flat on your face over it. @EOT: ---* Origin: afswlw rjfilepwq (3:711/934.2) SEEN-BY: 711/934 @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™.