aboutsummaryrefslogtreecommitdiffstats
path: root/src/modules/objects/KvsObject_treeWidgeteItem.cpp
diff options
context:
space:
mode:
authorGravatar Vladimir Panteleev2016-07-07 06:27:46 +0000
committerGravatar Vladimir Panteleev2016-07-28 17:18:16 +0000
commitf5d6aa3640b3bf3bbaede22fe771676bd48b7dcf (patch)
tree6f1f82b0615cf1f100a3e82cb66cad7f34844587 /src/modules/objects/KvsObject_treeWidgeteItem.cpp
parentdocumentaion: formatting fixes (diff)
downloadKVIrc-f5d6aa3640b3bf3bbaede22fe771676bd48b7dcf.tar.gz
KVIrc-f5d6aa3640b3bf3bbaede22fe771676bd48b7dcf.tar.bz2
KVIrc-f5d6aa3640b3bf3bbaede22fe771676bd48b7dcf.zip
Implement `znc.in/self-message` IRCv3 capability
This capability is used to indicate that the client supports receiving messages previously sent by the user. In ZNC, it is required for proper playback of private message conversations. More information: http://wiki.znc.in/Query_buffers#Self_messages The implementation is fairly straight-forward. In the relevant places, we switch the method used to identify if a message is a private message or belongs in a channel - instead of comparing the target to our nickname, we check if it starts with one of the server-announced CHANTYPES characters, which has the additional benefit of avoiding a race condition when changing nicknames. Possible forward improvements: - Currently, if the first message received for a window is a self-message, we do not call setTarget. As far as I've seen, the effect is purely cosmetic (the target is not added to the member list, which is hidden by default anyway). - CTCP code for each CTCP message type needs to be manually updated to handle self-messages. This patch only addresses ACTION CTCPs.
Diffstat (limited to 'src/modules/objects/KvsObject_treeWidgeteItem.cpp')
0 files changed, 0 insertions, 0 deletions