> I think it's useful in case you want to transfer between to different > clients, there for you need some kind of standard! And transfer via > XEP-0313 isn't really usable because it just works with unencrypted > messages...
Encrypted messages are not meant to be transferred. For example, OTR stands for Off The Record. Which means that messages should not be even recorded after being displayed. You've read them, that's it. If you want to transfer encrypted messages, use PGP like encryption, because what you suggest effectively cancels the difference between OMEMO and PGP/GPG. >1. CSV is a rather bad format and not fully standardized That was a joke. Of course, decent developers these days should use json for tasks like these. > Going a bit offtopic: we still have a lot of problems with message > delivery in XMPP, for example, we have no protection against server > failures during message delivery or we don't have reliable delivery > in presence of s2s failures. Yet, you want to add another source > of message delivery failures. Totally, this. We've developed a way to reliably deliver messages (modestly called 'reliable message delivery'), but regular chat messages are still vulnerable in cases of s2s failure. -- Ненахов Андрей Директор ООО "Редсолюшн" (Челябинск) (351) 750-50-04 http://www.redsolution.ru _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
