XSF Discussion - 2020-10-27

  1. MattJ

    Apart from XEP-0313, does anyone know other features that the client must disco their account to discover?

  2. Zash


  3. Link Mauve

    vCard conversion?

  4. Link Mauve

    And bookmarks conversions, all three of them?

  5. MattJ

    Not carbons, according to the XEP

  6. Link Mauve

    Also PEP stuff most likely.

  7. MattJ

    It's just come to my attention that this stuff isn't covered by the caps we put in stream:features

  8. Zash


  9. Zash

    Also account vs host features is weird

  10. MattJ

    That's the discussion I'm having with a client dev right now :/

  11. flow

    put user caps string too in stream:features?

  12. Zash

    Can you?

  13. Zash


  14. MattJ

    Seems like a sensible solution, obviously you need to differentiate the two somehow

  15. flow

    Zash, probably even in sasl's <success/>

  16. jonas’

    add an @address attribute to <caps/>?

  17. jonas’

    so that you can have multiple in <stream:features/>?

  18. jonas’

    I hear '390 is still experimental

  19. Zash

    jonas’, do it

  20. Zash

    and then we can shove in subdomains as well :)

  21. flow


  22. Zash

    I had some ideas around a recursive disco#items-like thing that'd include caps of its items

  23. jonas’

    pep., https://github.com/xsf/xeps/pull/988 poke

  24. jonas’

    (nothing to see here)

  25. jonas’

    MattJ, related: https://github.com/xsf/xeps/pull/924

  26. jonas’

    IMO account is the logical entity

  27. jonas’

    but there is some prior art in the other direction

  28. Zash

    Uh, fun

  29. MattJ

    Yes, 191 was the first I checked actually when looking for "proof" :)

  30. jonas’

    fun fact: I made that PR because of a deployment where '191 is *not* available for all accounts

  31. Zash

    jonas’: Breaking change to a Draft XEP? Mmmmmmmm

  32. jonas’

    Zash, good point :)

  33. MattJ

    Holger, do you know if ejabberd advertises MAM on the server JID?

  34. MattJ

    I guess an XML console can tell me

  35. MattJ

    unless it replies differently to remote users

  36. Holger

    MattJ, yes MAM is advertised both on the server and account JID.

  37. Holger

    I think an older revision mandated the server JID? Or some client(s) assumed it ... 😕

  38. MattJ

    Seems some clients definitely assume it :(

  39. MattJ

    I don't know about older XEP revisions

  40. MattJ

    Apparently Openfire is also guilty of this

  41. MattJ

    I want one of these to be combined with "and if you sent a MAM query to the server JID, a local user can access all messages that the server has seen"

  42. Holger

    > Apparently Openfire is also guilty of this I think it's our specs fault 🙂 My impression was we were moving from server to account JID (where it makes sense), but only half-heartedly. IIRC I PRd against multiple XEP examples that got it wrong and stuff.

  43. Holger


  44. MattJ

    Makes sense

  45. Holger

    Also e.g. https://xmpp.org/extensions/attic/xep-0359-0.5.0.html#disco vs. https://xmpp.org/extensions/xep-0359.html#disco ... and I'm pretty sure there's more such examples.