for <email@example.com>; Wed, 2 Feb 2000 20:29:49 -0800
\nDate: Wed, 2 Feb 2000 20:29:49 -0800
\nSubject: OOPS tag for SLCP
\nFull_Name: Josh Wilmes
\nSubmission from: (NULL) (22.214.171.124)
\nAdd a OOPS tag for SLCP messages generated by an /OOPS.
\nSomething like this:
\n%NOTIFY SOURCE=#119 EVENT=public TIME=949552051 NOTIFY RECIPS=#103 VALUE=4=test
\n%NOTIFY SOURCE=#119 EVENT=public TIME=949552063 NOTIFY OOPS RECIPS=#103
\nVALUE=25=Oops! Please ignore that.
\nA smart client could then even remove the last message from that user to that
\nfrom its scrollback, if so desired. (this is a questionable feature, but
\nsomeone would want it..)
\nThe main reason for this is that someone suggested on lily-dev that bots should
\nIntroducing a new event type (rather than public) seems like a colossally bad
\nto do this ;)