jdev - 2023-03-23

  1. masum.nishat21

    As of XEP-0050: Ad-Hoc Commands Section 2.3 Announcing the Command List it says "In some cases, a responder entity may find it appropriate to automatically push this information (e.g. a subscribed entity becomes available). In this case, the entity sends a <message/> containing the proper disco#items <query/>" No documentation is available on how some entities can subscribe to others' "http://jabber.org/protocol/commands" node. I also searched in XEP-0163: Personal Eventing Protocol with no luck.

  2. MattJ

    masum.nishat21: you're right, there is no such mechanism

  3. masum.nishat21

    MattJ: what is the implementation of that section?

  4. MattJ

    I'm not aware of any

  5. masum.nishat21

    MattJ: I'm creating an xmpp client. Should i just omit this section?

  6. MattJ

    I suggest so, yes

  7. MattJ

    There is occasionally talk about 'push' for disco#info, but nobody has really worked on it and that suggests nobody really needs it

  8. MattJ


  9. masum.nishat21

    MattJ: okay for now I'm leaving it as it is.

  10. masum.nishat21

    Can i request to take care of this section. I believe somebody may need it if it is well documented. Nobody works on this as unavailability of enough documentation.

  11. MattJ

    If somebody needs it, they can work on it. Otherwise it may be better to remove it or add a note

  12. masum.nishat21

    Is it possible for others rather than members of the xep community to work on it?

  13. pep.


  14. masum.nishat21

    What is the processing if i want to propose a draft for it.

  15. MattJ

    Take a look at https://xmpp.org/about/standards-process/

  16. MattJ

    If you have any questions, let us know... it would be good to get some feedback about that page as a starting point

  17. MattJ

    The "XEP community" is basically anyone who contributes, and anyone is welcome to contribute :)

  18. masum.nishat21

    Okay. I'll check it out.

  19. hi


  20. singpolyma

    masum.nishat21: FYI my client implements a UI for messages that attach a list of commands as per that section, and my gateway component hrs a few cases where it does send such messages. But I think we're the only ones

  21. jonas’

    wasn't there a "buttons" xep for that?

  22. singpolyma

    jonas’: I'm happy to hear of overlapping xeps of course

  23. jonas’


  24. jonas’

    iiinbooox :<

  25. jonas’

    if there are concrete use-cases, might be worth re-proposing this

  26. Zash

    jonas’, it was rewritten and accepted as https://xmpp.org/extensions/xep-0439.html

  27. jonas’


  28. jonas’

    then that :-)

  29. Zash

    I still have 0 XEP numbers on my CV :(

  30. jonas’


  31. jonas’

    but only because SLA is pending-on-editor-actoin?

  32. Zash


  33. jonas’

    wanna have one of mine? ;D

  34. Zash

    numbers go up?

  35. singpolyma

    Those both seem unrelated to the use case here, those are for chat bot interactions

  36. jonas’

    that's exactly what those were made for really

  37. singpolyma


  38. jonas’


  39. jonas’


  40. jonas’

    inferred wrong context

  41. jonas’

    what's your use case for ad-hoc attached to messages?

  42. Zash

    https://xmpp.org/extensions/xep-0045.html#voiceapprove this kind of pattern?

  43. singpolyma

    For example when someone initiates a jid switch in our service to change their jid, we push to the new jid a message "someone is asking to change oldjit to use this jid" kind of message. The can push button to start the command. Also for register they can start on web and type in their jid, we send a message "to start registration" and they can push the button

  44. singpolyma

    We plan to also use one for Bitcoin payment flow to get back to finish registering

  45. jonas’

    thank you I did not want to know about that

  46. singpolyma

    We could also use xhtml-im and xmpp:get?command;node= of course as another way, but there are trade offs

  47. jonas’

    my issue is with the mention and use of cryptocurrencies, not with the wire protocol.

  48. singpolyma

    No need to be rude :)

  49. singpolyma

    We will use it for cheques in the mail flow too, if you prefer to think about that

  50. moparisthebest

    jonas’: so you won't be a fan of a XEP for lightning payment integration? ;)

  51. jonas’

    for the purpose of my sanity, I'll disengage from this room for a while

  52. Kev

    > but only because SLA is pending-on-editor-actoin? I am sorry, I do feel very bad that I've not been able to keep up with work, health and Editor since the Summit. I hope to get back on top of things, it's 'just' a case of swimming to the top of the quicksand I'm currently in.

  53. moparisthebest

    XMPP is to chat what Bitcoin is to money, same thing

  54. singpolyma

    moparisthebest: ok, no need to troll the trolls :P

  55. moparisthebest

    Kev: don't feel bad, it's a lot of work, and you are a volunteer

  56. Kev

    Both the past volunteers has managed to keep on top of it :/

  57. moparisthebest

    singpolyma: I'm not, I genuinely never understood why people who prefer federated chat with no single entity in control don't also prefer federated money with no single entity in control

  58. Zash

    moparisthebest, would you kindly take your off-topic elsewhere

  59. singpolyma

    moparisthebest: yes, I understand, but also you're both just saying things you know will make the other upset at this point

  60. moparisthebest

    I'd like to understand the reasoning honestly

  61. moparisthebest

    If someone asks me why I respond that way to matrix I can tell them...

  62. flow

    I know I say it all the time, but XPath is really cool, and xmllint's --shell also

  63. moparisthebest

    I'm with you until you say xslt :)

  64. Guus

    weirdest wedding vows _ever_.

  65. jonas’


  66. flow

    Guus, are you new to this community? :)

  67. Zash

    Reminds me of x509guide.txt > By the power vested in me, I now declare this text string and this bit string 'name' and 'key'. What RSA has joined, let no man put asunder. -- Bob Blakley

  68. Guus

    flow: new & innocent

  69. Kev

    I'm not sure that's the right tagline for Flow.

  70. Guus

    I shall refrain from suggesting taglines for anyone but myself :D

  71. Kev

    Guus "Refrains from suggesting taglines"

  72. Guus

    I'd not go see that movie.