#3

closed
nobody
None
5
2000-12-16
2000-12-16
Anonymous
No

for <lily-bugs@centauri.org>; Wed, 2 Feb 2000 20:29:49 -0800
\nDate: Wed, 2 Feb 2000 20:29:49 -0800
\nFrom: josh@hitchhiker.org
\nMessage-Id: <200002030429.UAA13409@adira.centauri.org>
\nTo: lily-bugs@centauri.org
\nSubject: OOPS tag for SLCP
\n
\nFull_Name: Josh Wilmes
\nLily_Core:
\nclient:
\nOS:
\nSubmission from: (NULL) (171.70.144.186)
\n
\n
\nAdd a OOPS tag for SLCP messages generated by an /OOPS.
\n
\nSomething like this:
\n
\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.
\n
\nA smart client could then even remove the last message from that user to that
\ndestination
\nfrom its scrollback, if so desired. (this is a questionable feature, but
\nperhaps
\nsomeone would want it..)
\n
\nThe main reason for this is that someone suggested on lily-dev that bots should
\nignore
\noops messages.
\n
\nIntroducing a new event type (rather than public) seems like a colossally bad
\nway
\nto do this ;)
\n
\n--Josh
\n

Discussion

  • Josh Wilmes
    Josh Wilmes
    2000-12-16

    • status: open --> closed