msg-confirm.txt

msg-confirm client capability
----------------------------------------------------------------------

Copyright (C) 2012 Alex Iadicicco <[email protected]>

Unlimited redistribution and modification of this document is allowed,
provided that the above copyright notice and this permission notice
remain intact.

The msg-confirm client capability allows a client's PRIVMSGs and NOTICEs
to channels and users to be sent back to the client as confirmation.

Currently, clients are forced to assume that their message reached
the target exactly as sent. However, clients have no way of knowing if
a message was blocked or modified by a server. This capability allows
clients to see messages exactly as the target recieves them. This could be
useful in, for example, server-side plugins that replace "bad words" with
a series of asterisks. This functionality mimics the behavior of JOIN,
PART, NICK, and other similar commands whose behavior may be blocked or
modified by the receiving server.

This capability would also allow clients to see exactly where their
message appears in relation to other messages. The client is receiving
messages in the exact same order as the server receives them. In the
case of dropped connections and ping timeouts, this capability allows
clients to see exactly which messages actually made it to the server,
barring the few cases where a message made it to the server but not back
to the client.