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, Jonas
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
