Hi, I am just realizing that all these magic server features are incompatible to encryptions which use ratchet mechanisms. Because those depend on messages received in order. So for example OMEMO could never use these archive features, I don't think we can do anything about that.
We still have OpenPGP. Which should have no problem with that. Yeah your approach with the "external name" stuff looks fine to me. I'm not sure about this merge approach, looks like it could run into server stanza size limits in bigger group chats, definitely doesn't seem like it can scale up well. For single chat this should be fine and probably convenient, for group chats i think it makes more sense to request fastend content separately. Not sure what you mean by archive id and message id mismatch, yes those are never the same but why is this a problem? When we use the merge functionality of the server we would never need the archive ids of fastening messages, only for non-fastening messages. because of that i would say the archive-id can be omitted and the applied content can also be within the forwarded element. Or maybe I don't understand what other problem there is. Would be interesting to get the opinion of server developers if such merge features are even realistic to implement. Regards Philipp
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
