XMPP Council - 2022-12-21


  1. Ge0rG

    I'm not going to make it today.

  2. jonas’

    ack, thx for the notice

  3. moparisthebest

    hello all

  4. jonas’

    o/

  5. daniel

    Hi everyone. It's time

  6. daniel

    1) Roll call

  7. moparisthebest

    o/

  8. jonas’

    o/

  9. daniel

    Ge0rG said he won’t make it. is larma here?

  10. daniel

    I guess not but moving on

  11. daniel

    2) Agenda bashing

  12. daniel

    nothing to bash

  13. daniel

    3) Editors update

  14. daniel

    the editor published three new XEPs

  15. daniel

    a) NEW: XEP-0475 (Pubsub Signing) (https://xmpp.org/extensions/xep-0475.html) b) NEW: XEP-0476 (Pubsub Signing: OpenPGP Profile) (https://xmpp.org/extensions/xep-0476.html) c) NEW: XEP-0477 (Pubsub Targeted Encryption) (https://xmpp.org/extensions/xep-0477.html)

  16. jonas’

    and one protoxep

  17. daniel

    yes

  18. larma

    Here, sorry for the delay

  19. daniel

    4) Items for voting

  20. jonas’

    hi larma :)

  21. daniel

    a) Proposed XMPP Extension: Stream Limits Advertisement (https://xmpp.org/extensions/inbox/xep-sla.html)

  22. daniel

    +1 looks straight forward and useful

  23. jonas’

    (larma, could you stay around for a minute after the meeting? I've got a question regarding dino :))

  24. larma

    +1 for sla

  25. jonas’

    +1 for xep-sla

  26. moparisthebest

    +1 though I'm not sure it solves anything if remote limits are lower :'(

  27. daniel

    5) Pending votes

  28. daniel

    none

  29. daniel

    6) Date of Next

  30. daniel

    I'm going to propose +2w

  31. jonas’

    that sounds appropriate

  32. larma

    Works for me

  33. jonas’

    I'm off work in calendarweek 1, so as usual I might be completely out of my rhythm and may require gentle poking

  34. moparisthebest

    I'm fine either way but makes sense as I assume we aren't going to have a lot of things to vote on next week anyway

  35. Link Mauve

    MattJ, Zash, re xep-sla, you mistyped XEP-0153 as XEP-0053 fyi.

  36. Zash

    Oh no

  37. daniel

    OK. +2w (Jan 4th) it is

  38. daniel

    7) AOB

  39. jonas’

    none from me

  40. moparisthebest

    ha good catch Link Mauve

  41. moparisthebest

    nothing here

  42. larma

    RE sla: I'd love if the error message would contain machine readable limit information (to also solve end-to-end issues, even if it may take multiple attempts)

  43. daniel

    8) Close

  44. daniel

    Thank you all. Happy holidays. see you next year

  45. jonas’

    thanks daniel :)

  46. larma

    Also RE Link Mauve comment: I wasn't sure if it was mistyping 0153 or 0054 :D

  47. jonas’

    happy new year's then!

  48. jonas’

    larma, question: what's the prospect of '392 in dino?

  49. larma

    Thanks all and happy holidays

  50. jonas’

    larma, question: what's the prospect of '392 (consistent color generation) in dino?

  51. moparisthebest

    thanks all and happy holidays+new year etc etc :D

  52. Link Mauve

    larma, I also wondered, but went with the most likely candidate. ^^

  53. larma

    jonas’: good question. I think it's implemented already but not used for anything. We weren't exactly happy with how it looked, but we might want to revisit that and see what we can do.

  54. jonas’

    I've been using it for months (had rebased your commits) and I'd love to not have to rebase regularly :)

  55. jonas’

    if there's anything which can or has to be done spec wise, you know where to find me :)

  56. moparisthebest

    Zash, that XEP is very useful but I can't come up with a good solution for when a remote S2S limit is lower :'(

  57. Zash

    moparisthebest, I don't understand and now is not a good time to process anything

  58. Zash

    moparisthebest, I don't understand and now is not a good time to process anything (for me)

  59. Zash

    could you write down what you think the problem is somewhere? mail to standards@ for example

  60. moparisthebest

    client connects to their server A, the limit is 100 bytes, client sends a 99 byte message to remote server B, but remote server B's limit is 50 bytes

  61. moparisthebest

    I guess server A doesn't bother trying to send it to B and instead sends an error to the client, but that's pretty rough

  62. Zash

    better than the s2s connection being closed and anything that was in transit being lost

  63. moparisthebest

    I agree

  64. Zash

    which is what happens regularly right now, any time anyone requests the vcard of someone with huge avatars

  65. larma

    The only "solution" would be fragmentation and that would get a big NO from me...

  66. Zash

    but the point is to make the limits clear to both parties, so then they can abort early if they find they're about to send something too big. doesn't the protoxep text say this already?

  67. moparisthebest

    you could have a way to query your server for the limit to remote server B, but that gets pretty rough too

  68. larma

    The limits could be different depending on the stream though.

  69. Zash

    The working name for this was "pathmtu". :)

  70. moparisthebest

    I typed "query your server for the mtu" but then backspaced lol

  71. emus

    Does Council want us to announce new XEPs or something like this? It could look like this: https://fosstodon.org/@xmpp/108058245120853596 The only thing I'd require is what info should go in etc. and maybe a ping if something new is out

  72. Zash

    I observe that this SLA still waits for Ge0rG

  73. moparisthebest

    emus, yea I think it at least needs waiting until editor publishes them, but you could announce the 3 new ones

  74. emus

    But is it correct to wait or not? Lets go only the official way

  75. emus

    In genereal such posts get quite some attention, at least the last times there were way more shares than for other posts

  76. Zash

    larma, re machine readable limits in errors, something like https://xmpp.org/extensions/xep-0363.html#errors ?

  77. Zash

    I have another half-finished protoxep full of various s2s related error conditions

  78. larma

    Zash: yes, like that

  79. Zash

    I made a note

  80. Zash

    thanks