* Daniel Gultsch <[email protected]> [2016-10-27 21:17]: > is there a reason you are including the SID in the URL? > > If not I would just propose doing > > xmpp:[email protected]?omemo=070c42a11644a78b2f6f56213be4686374222895eb67b781abc44b860c47656c,e3898c2083b830a5fcb5e49632a3442837f8e8a24bea2f39e37d632807c82871
What about using "omemo=base64(sid1 + key1),base64(sid2 + key2),..." Rationale: * URL-safe base64 provides the shortes feasible representation, and base64 is a dependency for Entity Caps and IBB already. * the sid is used as a 32bit integer (according to spec) * the key is the respective public key (fingerprint?) * the complete omemo parameter can be passed to the OMEMO implementation, instead of having to iterate over omemo-sid-* entries, and the OMEMO plugin can easily split on "," Kind regards, Georg
signature.asc
Description: Digital signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
