DN> and don't give them cause to become defensive; e.g. threats right at
DN> the start get nowhere very fast and usually escalate for no good cause.

PE> No threats at the start.

RS> Pigs arse there werent, you said right
RS> from the start that it was a PCable offense.

PE> Crap.

Fraid you did, the FIRST time you said anything to the NODE, you did just that.

PE> Just a simple pointing out that messages from your system were out of spec.

RS> You havent actually established that they WERE

PE> Read the specs yourself.

No thanks, it aint as rigidly specified as you claim, just like the
presence of 0x01s aint anything like as rigidly specified as you claim.

PE> :-)

RS> No point in grinning yet, you aint established
RS> that it was 'causing problems for the network'

PE> Yes I have, one person is enough.

Pigs arse it is. If your code is mindlessly anal or just badly
written and falls over because it uses a fragile alg on the PATH
data, thats YOUR problem when the format aint rigidly specified.

And even when the format *IS* rigidly specified like with the date,
just because that caused YOU as one person a problem that DOES NOT mean
that you get to demand that everyone in the entire net cleans up their act
forthwith with you furiously PCing every breach of 'the specs' you can find.

Fraid Fido doesnt actually work like that, it will in
fact just flush you out of the system if you try that.
@EOT:

---