jdev - 2023-11-22


  1. MattJ

    Well, bind1 doesn't say that a server must keep offline messages indefinitely, amd bind2 doesn't say MAM archives must expire, so it's not strictly a bind1 vs bind2 thing, but related to implementation and deployment decisions

  2. Zash

    It does allow for increased confidence level of "this message been delivered to all (known) clients".

  3. Zash

    Bind2 does allow for increased confidence level of "this message been delivered to all (known) clients".

  4. MattJ

    If it's exclusively used on the account

  5. edhelas

    Prosody doesn't implement Stanza-ID in MUC ? https://github.com/movim/movim/issues/1252#issuecomment-1822372718

  6. edhelas

    Or did I overlooked something ?

  7. edhelas

    Ah, it seems that for direct messages its the case, but when queried via MAM the stanza-id is truncated ?

  8. Zash

    I don't understand

  9. Zash

    > <result xmlns='urn:xmpp:mam:2' id='9fb80f6e-ba98-42e8-a09a-6732e03ed4e5' queryid='jj2DHdGhMeR8'> That's the id.

  10. edhelas

    But there is no <stanza-id/> item anymore ?

  11. Zash

    There wasn't one before it was archived.

  12. Zash

    https://xmpp.org/extensions/xep-0313.html#results > The result messages MUST contain a <result/> element with an 'id' attribute that gives the current message's archive UID (archived messages MAY also contain a XEP-0359 <stanza-id> element, but clients MUST NOT depend on it). Note the last part.

  13. Zash

    You are breaking a MUST NOT.

  14. edhelas

    So, what is happening in the case of https://xmpp.org/extensions/xep-0461.html#business-id ?

  15. edhelas

    If the message is retrieved by MAM and that I don't have to depend on the returned <stanza-id>

  16. edhelas

    (or in this case that the <stanza-id> doesn't exists ?

  17. edhelas

    I'm in the case of a MUC there

  18. Guus

    Zash/MattJ: does Prosody push IQ pings to a MUC occupant when the client is in CSI? Openfire is kicking out users for inactivity, after they fail to respond to a ping request sent by the room. This particular occupant joined through federation, from a Prosody-powered domain. I'm seeing the ping responses come in after ~15 minutes. I'm trying to figure out what could cause the delay.

  19. Zash

    IQ is always pushed

  20. edhelas

    So, if I understand correctly, in case of direct <message> I can use <stanza-id> for MUC, and once I retrieve them using MAM, I have to rely on <result id=''> that is actually the same ID as the <stanza-id> (and in this case the <stanza-id> is not there anymore.

  21. edhelas

    > The result messages MUST contain a <result/> element with an 'id' attribute that gives the current message's archive UID (archived messages MAY also contain a XEP-0359 <stanza-id> element, but clients MUST NOT depend on it)

  22. edhelas

    In this paragraph, it is not clear that the Message Archive UID == stanza-id

  23. nicoco

    I think the fact that MAM id == stanza-id should be more explicit too. Slidge as a MAM server does that, but I remember needing to discuss this here to understand it, which is probably a sign that this should be made more explicit.

  24. Zash

    https://xmpp.org/extensions/xep-0313.html#archives_id makes that explicit, no?

  25. Zash

    "not there anymore" but you're getting a copy of the message _before_ <stanza-id> was added