Justin Mason wrote: > > Anyone care to craft a response? I think we should. bonus points for > including the obligatory comp.risks tagline >
I submitted a reply right after the RISKS Digest issue came out. The issue after that indicated that there was a backlog of submissions to RISKS, so maybe my reply will be accepted and published. It isn't worth too much of a flame. For reference see http://xkcd.com/386/ I find it really interesting that the author of that rant to RISKS revealed how little he has learned from past mistakes by posting how he messed up an NNTP client and server that he wrote by ignoring some important details of the relevant RFC because he knew better than the RFC authors. As far as I'm concerned his post is an example of Muphry's Law, but in the realm of software design instead of spelling. -- View this message in context: http://old.nabble.com/SA-team-lambasted-in-RISKS-Digest-tp27789030p27799024.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
