[Standards] UPDATED: XEP-0333 (Chat Markers)

Spencer MacDonald spencer.macdonald.other at gmail.com
Wed Oct 28 21:30:27 UTC 2015

You are correct it's purely client based (although this wasn't originally the case) so determine support should be between 2 clients.
In regards to sending not sending an error, I just borrowed that from the delivery receipts XEP :-)

From: Thijs Alkemade <me at thijsalkema.de>
Sent: Wednesday, October 28, 2015 8:28 p.m.
Subject: Re: [Standards] UPDATED: XEP-0333 (Chat Markers)
To: XMPP Standards <standards at xmpp.org>

              On 28 okt. 2015, at 16:50, XMPP Extensions Editor <     editor at xmpp.org> wrote:        
         Version 0.2.1 of XEP-0333 (Chat Markers) has been released.     
Abstract: This specification describes a solution of marking the last received, displayed and acknowledged message in a chat.     
Changelog: Fixing typo ("cannot" repeated twice) (JC Brand). (XEP Editor (mam))     
Diff:      http://xmpp.org/extensions/diff/api/xep/0333/diff/0.2/vs/0.2.1     
URL:      http://xmpp.org/extensions/xep-0333.html     
                I tried to read this specification today, and it left me rather confused.             
                   From the introduction it is not clear to me how Chat Sate Notifications +                Carbons is insufficient.                  
             §4 has two examples where the client queries a server for support, but the             entire specification reads as if it only applies to clients.             
             Lastly, it says in §6:             
             > If recipient does not support the Chat Markers protocol it SHOULD NOT return an error.             
             While it does sound like a very sensible requirement, extensions shouldn't be             able to set requirements for all implementions that don't support it.             
             Regards             Thijs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20151028/3703f9f2/attachment.html>

More information about the Standards mailing list