#Jitsi xmpp archive

Support can also be determined via Entity Capabilities (XEP-0115), a.k.a. Client queries for server features ¶Įxample 2. If an entity supports the Chat Markers protocol, it MUST report that by including a Service Discovery (XEP-0030) įeature of 'urn:xmpp:chat-markers:0' in response to disco#info requests: Example 1.

Enable a client to fetch and set Chat Markers regardless of wether the other users in a chat are online.

Enable a client to mark the last acknowledged message in a chat.

Enable a client to mark the last displayed message in a chat.

Enable a client to mark the last received message in a chat.

Enable a client to mark a message as markable.

This document addresses the following requirements:

The term 'Chat Marker' refers to the stanza by which the recipient replies to a 'markable message' with a marker. The term 'markable message' refers to the stanza for which the original sender would like to receive a Chat Marker. The term 'read' in the context of iMessage, Google Hangouts and Blackberry Messenger, directly maps to the displayed element in the Chat Marker namespace. The term 'system notification' refers to a notification (typically a preview) that is displayed separately to a Chat. The term 'active chat' refers to a chat that a user is currently active in. This means that Chat Markers can only provide a heuristic solution, but this is often satisfactory for the majority of use cases. Note: Chat Markers do not mark each individual message, nor do they assume a reliable transport. This XEP outlines an efficient message based protocol to provide this functionally using Chat Markers. Moreover by using Chat State Notifications (XEP-0085) you could infer that a message has been read by the recipient, if they become active at any point after the message has been delivered, but again it would require multiple messages to 'sync up' chat states between resources. Message Delivery Receipts (XEP-0184) currently provides delivery receipts on a per message basis,īut it does not provide any mechanism for the user to indicate that they have read or acknowledged the message.Īs delivery receipts are sent on a per message basis it would require multiple messages to 'sync up' up delivery receipts between resources.

#Jitsi xmpp archive

If one or more of the resources is not connected, it can fetch Chat Markers from the Message Archive upon reconnecting. These visual indications (referred to herein as 'Chat Markers') are synced between all of the sender'sĪnd recipient's resources automatically, so the state of a chat is always consistent. These services provide a visual indication of when a message has been delivered to any of the recipients resources and (optionally) when it has been read. The concept of delivery and read receipts has been popularised by other messaging services such as iMessage, Google Hangouts and Blackberry Messenger. When to send Chat Markers and markable messages.