Patch against centericq-4.20.0 Overview -------------------------------------------------------------------------------- In Jabber, unlike Internet Relay Chat (RFC 1459), a client receives the messages it sends in group chat (one-to-many) settings (IRC 'channels', Jabber 'conferences' or 'groupchat' type messages). This means that a Jabber client should not display its outgoing messages to the user for groupchat messages. I left a comment in the patch which indicates my thoughts on how I do not believe this to be the best way of doing this for the future. I am not familiar with many of the protocols that are supported by CenterICQ (I only use IRC and Jabber) so I do not know if the overwhelming majority are like IRC or like Jabber, or if there is an even split. I still think that it might be the best going forward if the hook classes were extended to report on whether the protocol should expect a response back from the server in these cases (or conversely, whether the client should display the outgoing message). Description of Patch -------------------------------------------------------------------------------- The patch modifies src/eventmanager.cc It adds a conditional which checks whether the protocol (ev.getcontact().pname) is jabber and if it is, if the contact in question is a conference (ischannel(c)). In the case that it is, it skips the steps: eventwrite(cev, history); logger.putevent(cev); time(&lastevent); Which does the equivalent of not logging the outgoing message, and not displaying it to the user. Instead, it gets logged and displayed when the conference server sends the message to all participants. Note: cvs did not build on my machine when I tried (2005-05-30). Admittedly, I did not try very hard to fix it. There appeared to be an issue with generating the configure script using autoconf.