Hi, On Thu, Jan 15, 2026 at 11:37 AM Daniel Gultsch <daniel@gultsch.de> wrote:
Title: End-to-End Encrypted Contacts Metadata Abstract: This specification describes how to encrypt contacts metadata to minimize server exposure.
honestly I’m not entirely sure I like this. My naive implementation would just stick a bunch of <item xmlns='jabber:iq:roster' jid='nurse@example.com'/> in some sort of wrapper element into on singleton roster node. No multiple items, not separate node for groups. Just re-use the same <group/> children from jabber:iq:roster. I reckon for most medium sized rosters the encryption overhead is the bottle neck instead of the bandwidths constrains of one items vs multiple items. Reusing the namespace and syntax (with groups as children) would allow me to re-use the roster processing pipeline i already have. So with my council head I would only accept this XEP if we are either open of developing this XEP into what I’m outlined above OR if we are open to at some later point accept an alternative proposal that describes the above. (And then have the better idea win that way) cheers Daniel