jdev - 2020-01-20

  1. tao

    hey all -- does anyone know the XEP to add room icons to MUCs? XEP-0153 doesn't mention MUCs or groups, so unsure if that's the one commonly used.

  2. jonas’

    it’s unspecified

  3. jonas’

    people do XEP-0153 on MUC addresses and it breaks some clients, but works in others.

  4. tao

    ah, okay. i'm particularly interested in adding arbitrary metadata to MUCs, so it sounds like that could be done by assigning a vCard note to the MUC. thanks!

  5. MattJ

    What kind of metadata?

  6. MattJ

    usually metadata is published in disco#info

  7. MattJ

    (XEP-0030 / XEP-0045)

  8. tao

    not so much service metadata as in disco#info, but metadata about a room. e.g. when it was created, its rules, or similar. (this is for a custom thing, not a general XMPP client, so compatibility with existing MUCs is not much of a concern)

  9. MattJ

    There is a description field

  10. tao

    that might actually work quite very for my use case -- thank you! 🙂

  11. MattJ


  12. MattJ

    Even for a closed thing, you might hit obstacles using barely used/documented stuff like vcards on MUCs, but disco and room configuration is well supported

  13. lovetox

    hm when i send <stream:stream />

  14. lovetox

    neither ejabberd nor prosody answer with <stream:stream />

  15. lovetox

    i send the closing, shutdown my outgoing stream, and receive instantly a TLS EOF on the incoming

  16. lovetox

    wondering if this is a problem with GLib socket code, or if the server really dont bother to make sure and send the closing

  17. Zash

    Did you mean `</stream:stream>`?

  18. lovetox


  19. lovetox

    oh wait

  20. lovetox

    i send a opening instead of closing ^

  21. lovetox

    ok now it works as it should :)

  22. lovetox

    thanks Zash

  23. Zash