Modern XMPP project discussion - 2025-02-17


  1. saf

    Isn't there an XML standard for vCard? https://datatracker.ietf.org/doc/rfc6351/ Has the information in https://xmpp.org/extensions/xep-0054.html#history become outdated?

  2. saf

    it should have been replaced by xep-0292, but it was not specified

  3. Zash

    As it says in #history, xep-0054 is based on an unfinished draft of an XML representation of vcard3. Later, vcard4 got a proper standard xml representation, which is what xep-0292 uses. But since there is nothing more permanent than the temporary solution, xep-0054 aka vcard-temp just won't go away.

    👍 1
  4. Zash

    Most recently because it is what provides avatars for group chats. User avatars use https://xmpp.org/extensions/xep-0084.html since some time, and at least one client uses https://xmpp.org/extensions/xep-0292.html for profile info, but there are many clients that only deal with user avatars.

  5. Zash

    avatar/profile picture and https://xmpp.org/extensions/xep-0172.html for a nickname-only mini-vcard

  6. saf

    I hope that MUC avatars based on User Avatar (XEP-0084) will appear soon.

  7. lovetox

    ? Why

  8. lovetox

    I'm not aware of any unsolved problem

  9. saf

    Abandon XEP-0054 – embrace PEP.

  10. lovetox

    One has nothing to do with the other

  11. lovetox

    Avatar is a some bytes, why do you care how they are transmitted

  12. Squeaky Latex Folf

    So Vcard4 has no avatar support?

  13. edhelas

    There's a dedicated XEP for avatars

  14. Squeaky Latex Folf

    Vcard4 has photo

  15. Squeaky Latex Folf

    > There's a dedicated XEP for avatars Does it work for MUCs?

  16. Squeaky Latex Folf

    Vcard4 doesn't have pronouns though iirc

    🫤 1
  17. Squeaky Latex Folf

    But it does have gender

  18. edhelas

    For this I don't mind a dedicated XEP

  19. edhelas

    Also Hats are good for that, waiting for the support in ejabberd: )

  20. edhelas

    Also Hats are good for that, waiting for the support in ejabberd :)

  21. Squeaky Latex Folf

    Vcard4 seems pretty good for that kind of thing though

  22. Squeaky Latex Folf

    But it just doesn't have an official pronouns field

  23. Squeaky Latex Folf

    Unfortunately

  24. Squeaky Latex Folf

    I remember on IETF mailing list somewhere it was complained about

  25. edhelas

    Well then we can put it elsewhere :)

  26. Squeaky Latex Folf

    Potentially, but where?

  27. MSavoritias (fae,ve)

    i mean we can extend the profile with additional fields besides vcard. or extend vcard itself 🤷‍♂️️

  28. MSavoritias (fae,ve)

    its xmpp. its all hacks and things taped together :P

  29. edhelas

    Good things about XML is that you can add stuff everywhere you want* *if you write a proper namespace about it :)

  30. Squeaky Latex Folf

    Yeah XML is cool stuff

  31. Squeaky Latex Folf

    Just unfortunate you need to wrap all binary in Base64

  32. Squeaky Latex Folf

    Also, if a server is sending a a large stanza (e.g. base64), is the socket basically stuck during the transfer of that stanza, or can another stanza be sent/received in parallel?

  33. MattJ

    Yeah, the lack of pronouns in vcard4 is a real shame

  34. Zash

    https://www.rfc-editor.org/rfc/rfc9554.html#name-pronouns

  35. MattJ

    Ah, nice

  36. Zash

    TIL this RFC

  37. Squeaky Latex Folf

    Oooh

  38. snowstorm

    Why does <fn> have to have a <text> child?

  39. snowstorm

    never mind, I guess it's just to keep it one-to-one with the vcard spec: https://datatracker.ietf.org/doc/html/rfc6350#section-6.2.1