jdev - 2023-12-18


  1. pep.

    XEP-0203: « Information about the delivery delay is communicated by adding to the <message/> or <presence/> stanza one and only one <delay/> child qualified by a namespace to be issued when this specification advances to a status of Draft. » So.. does this mean there can only be one <delay/> tag in a message/presence. Maybe that can be reworded if that's not the case because it's confusing otherwise. It should probably say something like "unique delay@from"?

  2. flow

    pep., maybe ask psa in xsf@

  3. Kev

    The text says that a single entity must only add one delay tag.

  4. Kev

    Other entities may add their own delay tags.

  5. moparisthebest

    evil entities may add many delay tags

  6. jonas’

    evil entities may add delay tags with arbitrary values of @from

  7. jonas’

    stupid entities may add delay tags with their own bare jid @from when sending to semi-anonymous MUCs

  8. jonas’

    lots of fun to be had with that

  9. jonas’

    lots of fun to be had with that xep

  10. pep.

    (As mentioned in that other room, MUCs may want to rewrite those JIDs to the participant JID)

  11. pep.

    (As mentioned in that other room, MUCs may want to rewrite these JIDs to the participant JID)

  12. jonas’

    (they do not, though)

  13. flow

    I find the current xep203 wording highly ambiguous, hopefully will submit a PR and fix that (together with removing the "when this specification advances to a status of Draft." part)

  14. flow

    I find the current xep203 wording highly ambiguous, hopefully someone will submit a PR and fix that (together with removing the "when this specification advances to a status of Draft." part)

  15. jonas’

    yes please

  16. lovetox

    ok, but servers dont validate it anyway

  17. lovetox

    i also suspect multiple delays are quite rare