The issue is that users can be online with multiple xmpp clients at the same time, so knowing that the message has been delivered to a client isn't very useful.
What you want to know is if message has been read, this is already the experience with other non XMPP Services such as iMessage, Facebook, BBM. iMessage and Facebook for example, marks a message as read when you make that chat active. Spencer On Tue, May 14, 2013 at 1:36 PM, Peter Saint-Andre <[email protected]>wrote: > On 5/14/13 4:07 AM, Matthew Wild wrote: > > On 14 May 2013 08:57, Spencer MacDonald > > <[email protected]> wrote: > >> Out of interest how does one propose or suggest a XEP? > > > > http://xmpp.org/xmpp-protocols/xmpp-extensions/submitting-a-xep/ > > > >> Although the usefulness of read receipts is debatable, it would make > sense > >> for all clients to implement them in the same way. > > > > I agree. > > Although I question the usefulness of spending time and energy defining > an extension whose usefulness we find debatable, I wonder: what would > the user experience be here? Do I need to click a button verifying that > I have read and understood each message (say, before the client will > show me another message)? > > Peter > > -- > Peter Saint-Andre > https://stpeter.im/ > > > _______________________________________________ > JDev mailing list > Info: http://mail.jabber.org/mailman/listinfo/jdev > Unsubscribe: [email protected] > _______________________________________________ >
_______________________________________________ JDev mailing list Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [email protected] _______________________________________________
