Full_Name: Josh Wilmes
Submission from: (NULL) (18.104.22.168)
Add a OOPS tag for SLCP messages generated by an /OOPS.
Something like this:
%NOTIFY SOURCE=#119 EVENT=public TIME=949552051 NOTIFY RECIPS=#103 VALUE=4=test
%NOTIFY SOURCE=#119 EVENT=public TIME=949552063 NOTIFY OOPS RECIPS=#103
VALUE=25=Oops! Please ignore that.
A smart client could then even remove the last message from that user to that
from its scrollback, if so desired. (this is a questionable feature, but
someone would want it..)
The main reason for this is that someone suggested on lily-dev that bots should
Introducing a new event type (rather than public) seems like a colossally bad
to do this ;)
Log in to post a comment.