Does anyone of you use XEP-0013 in your client other than for purging offline messages when you support MAM?
If this is the only practical usecase of XEP-0013 I'm planning to use the purging of messages as (strong) indicator that a client uses MAM and as such doesn't want the server to return errors if his smacks session times out while still having unacked stanzas in its queue. What problem do I want to address? Currently (at least in prosody) all unacked stanzas in a smacks queue trigger an error to the sender when the smacks session times out. In clients like Conversations or Gajim this error will be shown to the sender of the message. And this holds true even if the receiver uses multiple devices and the other device already acked the message using XEP-0184. This error is useless if the receiving device (the one the smacks session timed out for) uses MAM to later retrieve the message. More than that: it makes for very bad UX because people think messages got lost even though they eventually will arrive at the device in question. If XEP-0013 is used as indicator that the device wants to use MAM to retrieve messages, this in turn can be used by the smacks implementation to silently drop queued stanzas on timeout rather than sending back a spurious error confusing users. -- tmolitor _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
