Modern XMPP project discussion - 2026-02-16


  1. nicoco

    AFAIK we have the avatar/avatar-metadata PEP nodes because storing avatars in vcards is bad, performance-wise. VCard also isn't a good fit for storing the list of rooms of a space, is it? Ofc I may be wrong, but I think that whatever we can come up with to add "updates broadcast" and access control of conference servers is going to be so pubsub-looking that I don't understand the reservations about using pubsub (or a subset of) in the first place.

  2. edhelas

    Maybe people are afraid of implementing 0060 :p

  3. Alex

    Any modern client implements pubsub (PEP) these days already. Avatars, Nick, Bookmarks .....

  4. erebion

    How do OMEMO QR codes/links such as those from Conversations work? What is the OMEMO SID number? Could clients just add that as a link? Perhaps users could then transfer it using a different channel. Maybe I could then click it..? Dino has no way to scan the code and there's nothing else I could use on my Linux phone.

  5. jprjr

    Right sorry, when I said "vcard" I didn't strictly mean the vcard spec. I really just mean "a method of storing metadata about the conference service" A way to associate an image to the entire conference service, store admin info etc. Most things I see discuss images associated to individual rooms, or admin info for the higher-level host server. By "things I see" I pretty much mean prosody modules and their docs.