#5 OOPS tag for SLCP

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

Full_Name: Josh Wilmes
Lily_Core:
client:
OS:
Submission from: (NULL) (171.70.144.186)

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
destination
from its scrollback, if so desired. (this is a questionable feature, but
perhaps
someone would want it..)

The main reason for this is that someone suggested on lily-dev that bots should
ignore
oops messages.

Introducing a new event type (rather than public) seems like a colossally bad
way
to do this ;)

--Josh

Discussion

  • Josh Wilmes

    Josh Wilmes - 2000-12-16
    • priority: 5 --> 1
     
  • Josh Wilmes

    Josh Wilmes - 2000-12-16
    • priority: 1 --> 5
    • status: open --> closed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks