TIP: Click on subject to list as thread! ANSI
echo: locuser
to: Rod Speed
from: Paul Edwards
date: 1996-07-02 10:51:34
subject: Compliance

RS> Nope, *HE* used that particular word in the original question *YOU*
RS> asked him a long time ago. AND its dead fucking obvious that YOU didnt
RS> even PC on the very clear example of a completely unambiguous breach
RS> of 'the specs' on the date problem, EVEN THO it clearly did 'cause a
RS> problem' for you. You in fact chose to change your code to allow for
RS> it ANYWAY. So you have blown the feet right off your pathetically silly
RS> claim that even something that causes a non serious problem for a single
RS> node is something that its appropriate to PC on. In fact you are faking
RS> away like mad on that because you clearly had enough sense not to do that.

PE> The main reason I chose to not PC was because I realised I was
PE> allowed to just bin the entire message if it was out of spec.

RS> More porkies, you said to Bob that you changed your code
RS> to allow for it. Either THAT story or THIS one is a porkie.

I did?  I'm not sure what you're referring to here, I was unlikely to be
discussing low-level Tobruk code with Bob.  For efficiency reasons I
bypassed all checking of the date in my more recent versions of Tobruk. 
Except when writing to the messagebase.  And then when my routine finds a
bad date, it still prints it out as before, and then can choose whether it
calls Paul Markham's routine to try to get a date out of it, or simply bins
it.

RS> AND as Nugent says, thats positively counter productive and is MUCH more

Poor old Rod.  What Nugent actually says is exactly what I have said all along.

RS> likely to see them tell you to go and fuck yourself whereas they may well 
RS> be quite happy to fix a wart if you have the sense to politely point out 
RS> what the problem is rather than belt them in the face with a dead fish first
RS>  off.

I did.  Don't bother with the gross dishonesty, put all my messages on the
topic (the latest one with the 3D seenbys) and see how it reads.  No threat
of a PC, just a pointing out that a sysop should not be calling my software
a heap of shit when it is his system that is putting out a PC-able message.
 Poor old Rod.  BFN.  Paul. 
@EOT:

---
* Origin: X (3:711/934.9)

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™.