XSF Discussion - 2024-05-01

  1. pep.

    https://xmpp.org/extensions/xep-0045.html#enter-pres > After sending the presence broadcast (and only after doing so), the service MAY then send discussion history, the room subject, live messages, presence updates, and other in-room traffic. https://xmpp.org/extensions/xep-0045.html#enter-subject > After the room has optionally sent the discussion history to the new occupant, it SHALL send the current room subject. These two sentences conflict right?

  2. moparisthebest

    Unless it means if you send the discussion history then you MUST send the subject?

  3. moparisthebest

    But I can't say that makes a lot of sense...

  4. lovetox

    Pep. Look at the order of events in the xep

  5. pep.

    I know the order of events in the spec

  6. pep.

    I'm asking because §7.2.2 says MAY, and §7.2.15 says MUST

  7. MattJ

    I think this has come up before

  8. MattJ

    I *think* the conclusion was that subject is a MUST (even if empty)

  9. lovetox

    Room subject is not may

  10. lovetox

    The rest is ok with may

  11. pep.

    MattJ, yeah that's what 7.2.15 says

  12. pep.

    I'll submit a patch

  13. pep.

    I'd say s/MAY/may/ would fix it..

  14. pep.

    Is that breaking?

  15. pep.

    Conflicting instructions in the spec..

  16. jonas’

    I think this resolves if you grammatically bind the MAY to "send discussion history", instead of the entire enumeration thereafter.

  17. jonas’

    also, days since fixing a stream management counting bug: 0

  18. pep.

    Yeah but that's weird

  19. pep.

    $language

  20. pep.

    Also I have submitted this yesterday re disco https://github.com/xsf/xeps/pull/1341

  21. pep.

    “Element tt is not declared in div list of possible children” oops.

  22. pep.

    (fixed)