Here below is a bump disguised as feedback on the protoxep. It provides a way to indicate and synchronize (on a best effort basis, you can’t really shield yourself against a rogue remote client or server) the preffered expiration for the messages in this conversation, and send it with each message.
Since it is on a best effort basis, I disagree with the stated goal of preventing the clients that do not implement this feature from seeing the messages (section 2). This breaks compatiblity with most of the ecosystem while not really making sure they do not store the message. Thus I would suggest keeping the message contents in the message body, and having the separate <ephemeral/> element nearby, indicating to supporting clients that they should delete the message after a number of seconds, while obviously keeping the warning about non-supporting clients noted in section 4. On Tue, Jun 05, 2018 at 03:17:57PM -0000, Jonas Wielicki wrote: > The XMPP Extensions Editor has received a proposal for a new XEP. > > Title: Ephemeral Messages > Abstract: > This specification defines a protocol to send ephemeral messages over > XMPP and synchronize timer value setting across devices. > > URL: https://xmpp.org/extensions/inbox/ephemeral-messages.html > > The Council will decide in the next two weeks whether to accept this > proposal as an official XEP. > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: standards-unsubscr...@xmpp.org > _______________________________________________ -- Mathieu Pasquet (mathieui) - Poezio developer _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
