BL> It's a good ideal that falls apart in the execution. Paul has
BL> devised something that would work in perfect conditions without
BL> looking at how to stuff it up. It's easy to stuff up... just
BL> don't add EOT and put a false one after SOT. That way, every
BL> message is blank for anyone using a SOT/EOT-aware reader.

PE> If you want to write buggy software, it is far easier. Just
PE> write a PKT that has the first 5 bytes as "HELLO". That will
PE> not get processed either. Poor old Bob, doesn't even know what
PE> we have standards for.

BL>   My scenario does not need buggy software, Paul; just a PKT reader
BL> that does not add EOT and any keyboard. That covers 99.99% of Fido.

The software is buggy if it allows an ordinary user to enter 0x01.
Next you will be saying that MSGID is flawed too.  All you need is
a system that doesn't generate MSGID, and a keyboard.  It's crap.

BL>   EOT is flawed and I just demonstrated it. Your move. Now you have to
BL> work out a change to the specification that prevents me doing that.

No, it is YOUR responsibility to conform to the specs.  BFN.  Paul.
@EOT:

---