XSF Discussion - 2019-06-06

  1. Kev

    Handling of unhandled stanzas to a local domain. 6120 says " either (a) handle the stanza as appropriate for the stanza kind or (b) return an error stanza to the sender.". 6121 helpfully says just to do what 6120 says. This is clearly vague, as returning an error for every stanza that isn't handled must be wrong (e.g. bouncing a bounce).

  2. Kev

    What do people generally do - drop everything except iq get/set, which error? Error everything that could be errorred (including headline etc.)?

  3. Guus

    Kev Openfire delivers messages to the local domain JID to all configured admins.

  4. Guus

    presence stanzas appear to be treated as if the 'to' attribute was empty.

  5. Guus

    (I'm looking at behavior, not code, so I might be missing things)

  6. Ge0rG

    There is also this weird duality where on c2s connections a client is sending to the account by default, not to the server domain

  7. Kev

    Guus: Ta.

  8. Kev

    Ge0rG: Weird duality?

  9. Guus

    fwiw, the Openfire behavior likely predates 6120.

  10. Ge0rG

    Kev: well, technically your stream is to your account, so the default @to is your bare JID, it's just a bit weird for client devvs

  11. Kev

    Fair enough - I never found that bit particularly odd, but I might be in the minority :)

  12. Zash

    I think that makes perfect sense. What's weird about it?

  13. Zash

    Other than the historical thing where tons of things are advertised on and hooked onto the server JID, while newer things often go on the account JID

  14. Ge0rG

    Zash: maybe it's just because the perceived endpoint is the server, not my account

  15. Kev

    My reading of this is that the minimally compliant thing to do is to error on iq get/set and swallow everything else, although I suspect errorring on a message (other than =error) might also be useful.

  16. MattJ

    I generally follow a policy of error for any unhandled/undelivered stanza

  17. MattJ

    Silent stanza loss is bad

  18. Zash

    And Prosody doesn't silently discard CSNs, they get saved to offline storage 🙂

  19. Kev

    I considered bouncing everything, but bouncing presence seemed more likely to be unhelpful than helpful. Maybe I'm wrong about that.

  20. Kev

    The really vital thing to bounce seems to be get/set.

  21. Kev

    Is there an argument for bouncing presence too?

  22. MattJ

    Yes: silent stanza loss is generally bad

  23. MattJ

    Trying to subscribe to a server's JID should return an error (if the server doesn't support that)

  24. MattJ

    For an example

  25. Kev

    That's probably fair.

  26. Kev

    Thanks all.

  27. MattJ


  28. Seve says hi!

  29. MattJ

    Hi Seve!

  30. MattJ

    ralphm, Guus?

  31. Guus

    as announced two weeks ago, I'm unavailable today.

  32. ralphm

    Sorry, got distracted

  33. ralphm bangs gavel

  34. ralphm

    0. Welcome + Agenda

  35. ralphm

    Nyco and Guus sent regrets

  36. ralphm

    Are we good with the agenda?

  37. Ge0rG

    I'd like to provide a very brief update on the German gov't contact

  38. MattJ

    Sounds good, and I'm good with the agenda

  39. ralphm

    Great, that's already on it

  40. Seve


  41. ralphm

    1. Discuss server setup

  42. ralphm

    MattJ tried to follow up and then I failed to. We'll try again.

  43. ralphm

    2. Messenger Regulation in Germany / EU

  44. ralphm

    Ge0rG: the floor is yours

  45. Ge0rG

    I've talked to the person behind freie-messenger.de (another open protocols initiative), and obtained the contact of the respective person in the German ministry.

  46. Ge0rG

    The contact person is Dr. Schäfer, whom I've contacted and provided a brief info of what the XSF is and who I am. He's currently obtaining an overview of relevant companies and projects/initiatives, and we will schedule a phone call after my holiday, in ~3 weeks

  47. Ge0rG

    that's it

  48. ralphm

    Cool. Thanks for doing this!

  49. Seve

    Thank you very much Ge0rG, very appreciated, glad that you will be able to speak with him

  50. ralphm

    I'll put the item on the backburner, pending that call, and am confident you'll come back when you have talked to Dr. Schäfer.

  51. Ge0rG

    I'm going to schedule 15-30mins to introduce ourselves and to see where we might provide help

  52. Ge0rG

    regardless of that, we should develop an idea of what we actually do want.

  53. Ge0rG

    make XMPP the default baseline interop protocol?

  54. Ge0rG

    make XMPP the #1 suggestion communicated to companies?

  55. Ge0rG

    require all companies to use _the same_ interop protocol?

  56. Ge0rG

    require all companies to use the same _officially standardized_ interop protocol?

  57. Ge0rG

    I'm pretty sure we won't be able to put XMPP into actual law. And I'm pretty sure that won't be useful anyway.

  58. ralphm

    This is a good question indeed.

  59. Ge0rG

    because who knows what the state-of-art will be in a decade or two

  60. ralphm

    I agree that they won't mandate XMPP, but a well-known standard protocol suite would be good. Particularly if it isn't something like RCS.

  61. Ge0rG

    ralphm: I'm eager to hear your rationale against RCS after the meeting

  62. ralphm

    Sure. For clarity, that's my personal view.

  63. Ge0rG

    Maybe Board should ponder a bit about the anticipated goals for the phone call

  64. ralphm

    I'm also interested in what the community thinks about this. Anyone lurking here, or reading this after the fact, with an opinion, please let us know.

  65. ralphm


  66. winfried

    for the record: I making a (probably unsuccessful) push right now to make XMPP the mandatory standard for message exchange in Dutch healthcare right now

  67. Ge0rG

    winfried: I'd love to hear your lessons-learned from that, on-list, via personal mail or otherwise, until June 22nd

  68. ralphm

    winfried: good to know. Would be interesting if you could share which arguments you use to make that case.

  69. Ge0rG

    ...and which aruments weren't good in the first place

  70. Ge0rG

    ralphm: it would be great to escalate that to The Community. Feel free to re-use parts of my initial Board mail.

  71. mtavares

    winfried, that would be great

  72. ralphm

    We also have other people in our community that have dealt with governmental and/or military requirements, so that could help as well.

  73. winfried

    Right now I am in a conference... I will post an e-mail on it to the memberlist

  74. ralphm

    winfried: thanks!

  75. ralphm

    3. Fabian Sauter on SCAM

  76. ralphm

    Seve added this one

  77. Seve

    Yes, he asked about joining in this very room

  78. ralphm

    He's doing the Berlin Sprints?

  79. Seve

    Although nothing else was mentioned, if there was a purpose behind, or if we need help, etc

  80. Seve

    ralphm, I met him at the Sprint there in Berlin, but I think he may be related to another one in another german city, not sure

  81. ralphm


  82. Seve

    I expected him to be here today so we could talk about it, but he is not, unfortunately

  83. ralphm

    Seve can you ask him to expand on what he wants to do on SCAM?

  84. Seve

    Yes, I will try to reach to him

  85. ralphm

    I have no objections at this point, but a bit more than this would be good.

  86. Seve


  87. ralphm

    4. Tigase use of the XMPP logo

  88. ralphm

    I believe I asked Peter this a while back, looking up what he said

  89. ralphm

    “stpeter‎: Hey, sorry, I was offline yesterday. I would think the logo is under the IPR policy, if it's licensed under anything.”

  90. ralphm

    nyco added this card, I don't know how that request came to us.

  91. ralphm

    Added info to the card

  92. ralphm

    5. Roadmap page

  93. ralphm


  94. Seve


  95. Seve

    It is basically this: https://github.com/xsf/xmpp.org/issues/564

  96. ralphm

    Well, first of all, I believe that page is out of date.

  97. MattJ

    I think the page needs removal or an update

  98. ralphm


  99. Seve

    We may want to discuss if we have a roadmap or not, before thinking on even linking it from the sidebar

  100. ralphm

    I'm curious if Council has an opinion on having a Roadmap like that.

  101. MattJ

    We've consistently failed at Board determining a roadmap the past few years, but if Council wanted to put some content there it would be good

  102. ralphm

    I wouldn't want to update it with without their involvement.

  103. ralphm


  104. ralphm

    I need to think about this some more. dwd: could you (and Council) think about this, too?

  105. ralphm

    6. AOB

  106. ralphm

    I forgot this at the beginning: can one of you make minutes?

  107. ralphm

    Also, anything else?

  108. Seve

    Not from me

  109. MattJ

    Who is collecting the use-case reports?

  110. MattJ

    There was one I saw shared somewhere about Nintendo using XMPP for notifications

  111. Ge0rG

    regarding SCAM applicants: wouldn't it be great to have them write a short application page on the wiki?

  112. Ge0rG

    doesn't need to be voted on by all members, just Board as-is

  113. ralphm

    MattJ: I saw a tweet thread on that. Would be very interested to get a case study from them.

  114. Seve

    It may be a good idea to start with a wiki page with the use-case reports, with some links and such, so we all can contribute

  115. ralphm

    The talk itself was not allowed to be recorded :-(

  116. ralphm

    Ge0rG: good idea. ← Seve

  117. ralphm

    Seve: agreed

  118. Ge0rG

    MattJ: https://twitter.com/jj1bdx/status/1134749626546843649

  119. Ge0rG

    there was also a japanese blog with photos

  120. Seve

    Vaulor, do you have it?

  121. Seve

    Here it is https://ascii.jp/elem/000/001/796/1796780/

  122. ralphm

    Do we have a way to contact the speaker?

  123. Ge0rG

    we could contact jj1bdx and ask for speaker info

  124. Seve

    Looks like he is an ejabberd contributor https://twitter.com/mickael/status/1134762932708028416 so maybe someone from our community can reach for contact details

  125. ralphm

    I'll try to reach out.

  126. ralphm

    7. Date of Next

  127. ralphm


  128. ralphm

    8. Close

  129. Seve


  130. MattJ


  131. ralphm


  132. ralphm bangs gavel

  133. MattJ


  134. Ge0rG

    Holger is the most friendly ejabberd developer I know. Maybe he could reach out?

  135. ralphm

    I've had contact with jj1bdx, and he's forwarding my request

  136. ralphm

    Seve: those slides are from a 2018 presentation, it seems

  137. ralphm

    related, but probably different from what jj1bdx tweeted

  138. Ge0rG

    fun fact: jj1bdx is a user of my other app

  139. Ge0rG