[Standards] Disappearing timers for OMEMO proposal

Jonas Wielicki jonas at wielicki.name
Sun May 13 10:38:03 UTC 2018

On Samstag, 12. Mai 2018 19:55:52 CEST Paul Schaub wrote:
> Hi!
> I get what you want to achieve, but I think it would be easier to define
> disappearing messages for general XMPP (not only OMEMO).
> As already stated, you cannot trust devices that announce support, to
> actually delete messages after the timer expired. Lets assume you do
> trust all involved devices. Lets see how to deal with legacy devices.
> Why not specify ephemeral messages like this:
> <message blabla="...">
>     <timer secs="300">
>         <body xmlns="jabber:client">This is an ephemeral message</body>
>     </timer>
> </message>

This is awful. It will require the message to carry a non-empty <body/> to 
deal with the MAM/Carbons mess (and also to help users of clients which do not 
support this feature).

In addition, this breaks all XEPs which depend on the <body/>, like References 
and 394.

kind regards,
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.jabber.org/pipermail/standards/attachments/20180513/6d489e50/attachment.sig>

More information about the Standards mailing list