XMPP Council - 2024-11-05


  1. moparisthebest

    Time or did timezones ruin things once again?

  2. dan.caseley

    Just thinking the same thing

  3. dan.caseley

    Wait, we're an hour late, aren't we?

  4. Kev

    It's an hour ago, according to the agenda Daniel sent.

  5. daniel

    Yes. It's time

  6. daniel

    1) roll call

  7. dan.caseley

    Howdy ๐Ÿ™‚

  8. daniel

    Oh no it is indeed an hour late

  9. dan.caseley

    Have fixed my calendar.

  10. daniel

    But if we are all here anyway...

  11. moparisthebest

    Oh good because I would have missed it lol

  12. larma

    ๐Ÿ‘‹

  13. daniel

    Is singpolyma around too?

  14. singpolyma

    helloโ€‹

  15. daniel

    2) Agenda Bashing

  16. daniel

    Nothing to bash

  17. daniel

    3) no editors update

  18. daniel

    4) Items for voting

  19. daniel

    a) Move 'XEP-0490: Message Displayed Synchronization' to stable https://xmpp.org/extensions/xep-0490.html

  20. singpolyma

    Is it concerning at all that there are no implementations of the server assist part?โ€‹

  21. daniel

    LC had good turn out. +1

  22. daniel

    Not at this stage. This may or may not be something I'd remove before final

  23. Kev

    Oh, one of my team had some errors they noticed in the spec that I forgot to forward. I think they were editorial though, will try to remember to dig them out and send on.

  24. singpolyma

    +1โ€‹

  25. dan.caseley

    Yeah, that was a real positive response on the list. +1

  26. daniel

    Personally I was not a huge fan of server assist and only put it in because people at the summit very explicitly asked for it

  27. daniel

    So if I goes at final I'm fine with it

  28. moparisthebest

    +1 also think we should remove non implemented bits before final

  29. singpolyma

    fairโ€‹

  30. larma

    +1

  31. larma

    Just for my understanding: do current client implementations have support for server assist?

  32. daniel

    Yes

  33. daniel

    Conversations for sure

  34. daniel

    Monal I'm 50% sure

  35. singpolyma

    Does the client need support for it?โ€‹

  36. singpolyma

    the server just updates the node for you doesn't it?

  37. daniel

    You need to withhold the pep publish for once

  38. daniel

    But anyway that makes it accepted. Thanks. Moving on

  39. daniel

    5) Pending votes Travis on 3 PubSub proto xeps from last week.

  40. daniel

    5) Pending votes moparisthebest: on 3 PubSub proto xeps from last week.

  41. moparisthebest

    Still gonna be on list :(

  42. daniel

    Ok

  43. daniel

    6) date of next

  44. daniel

    +1w wfm

  45. singpolyma

    +1w wfmโ€‹

  46. larma

    > You need to withhold the pep publish for once Should have been more precise: Do you add the additional displayed marker if the server announces support?

  47. daniel

    larma: yes I implement the spec.

  48. larma

    +1w wfm

  49. moparisthebest

    Couldn't the server just silently reject it if it implements this?

  50. moparisthebest

    +1w wfm

  51. daniel

    moparisthebest: I think the point is to reduce traffic

  52. moparisthebest

    > Couldn't the server just silently reject it if it implements this? Not the right word... Couldn't the server just do nothing

  53. daniel

    So you want to know

  54. singpolyma

    >> You need to withhold the pep publish for once > Should have been more precise: Do you add the additional displayed marker if the server announces support? Oh yes I see, it's like a different element added to outgoing messages. I don't do that but then I guess it won't break anything then

  55. moparisthebest

    Makes sense yes

  56. dan.caseley

    Sorry, comms blip. +1w wfm

  57. daniel

    7) aob

  58. moparisthebest

    None here

  59. daniel

    Assuming no AOB

  60. daniel

    8) close.

  61. daniel

    Thank you all

  62. dan.caseley

    Thanks Daniel!

  63. dan.caseley

    See you all at 4pm UTC next week ๐Ÿ˜€

  64. moparisthebest

    Seriously what TZ is the meeting pegged at?

  65. moparisthebest

    My Android calendar still has the same bug

  66. moparisthebest

    Is this still right? https://www.moparisthebest.com/council.html

  67. daniel

    > Seriously what TZ is the meeting pegged at? UTC

  68. dan.caseley

    Meeting is on UTC/GMT. That looks right to me.

  69. daniel

    But today we were an hour late

  70. daniel

    Because I messed up

  71. daniel

    I simply forgot and then got confused about the time zone

  72. moparisthebest

    singpolyma: you are iteam, can we get that html uploaded on xmpp.org maybe :)

  73. singpolyma

    I'm only on iteam for dns and mail server so far, hehโ€‹

  74. dan.caseley

    Maybe hold off a few weeks... The next council may pick a new time ๐Ÿ˜€

  75. moparisthebest

    Then edit the file :P

  76. Kev

    Isn't Council term nearly over anyway, and new Council chooses new schedule.

  77. moparisthebest

    That's what dan.caseley just said (:

  78. Kev

    I blame the time machine.