BL> SOT/EOT is meant to prevent authors adding spurious kludge
 BL> lines maliciously, but it only works if the malicious author
 BL> adds the SOT to prevent hid adding the malicious kludge line...

 PE> In normal BBS software, the author only gets to put the text,
 PE> not the origin line or tearline (or EOT).

  I agree that SOT is useful to stop accidental screw-ups with Netmail
when there may be no leading #1 lines, but EOT has no function when
both the Tear line and Origin line do the same thing.

  If this only occurs in the reader, then a far safer method is to do
a character translation for all kludge lines (as BlueWave does) inside
text. Your system relies on the BBS software being SOT/EOT-aware to
work. The BlueWave system relies on nothing.

 BL> Of course Paul *does* add SOT/EOT, and to do so he has the read
 BL> the Tear line so he can put it inside. It's just silly.

 PE> Liar, liar, pants on fire. BFN. Paul.

  I apologise, but this only shows how stupid you are. SOT/EOT is
worse than useless if it is not there, or if the BBS software is
unaware of it. To be even slightly useful, it should be added by every
SOT/EOT-aware processor.

  If you have to rely on readers to insert it, you would be better off
promoting the idea that the text generated by all readers must not
include un-translated kludge lines.
 
Regards,
Bob
___ Blue Wave/QWK v2.12
@EOT:

---