<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Agreed. We implemented read status at my company the same way Michael did in his reply. Read status works at a conversation level, not at the individual message level. We pretty much just store the datetime the client last opened the conversation with any message delivered before that time considered read. Should be a simple matter to have the jabber server send a receipt to the sender when this happens.<br><br>Sent from my iPhone</div><div><br>On May 14, 2013, at 9:02 AM, Spencer MacDonald <<a href="mailto:spencer.macdonald.other@gmail.com">spencer.macdonald.other@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">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.<div><br></div><div style="">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.</div>
<div style=""><br></div><div style="">iMessage and Facebook for example, marks a message as read when you make that chat active.</div><div style=""><br></div><div style="">Spencer</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Tue, May 14, 2013 at 1:36 PM, Peter Saint-Andre <span dir="ltr"><<a href="mailto:stpeter@stpeter.im" target="_blank">stpeter@stpeter.im</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 5/14/13 4:07 AM, Matthew Wild wrote:<br>
> On 14 May 2013 08:57, Spencer MacDonald<br>
> <<a href="mailto:spencer.macdonald.other@gmail.com">spencer.macdonald.other@gmail.com</a>> wrote:<br>
>> Out of interest how does one propose or suggest a XEP?<br>
><br>
> <a href="http://xmpp.org/xmpp-protocols/xmpp-extensions/submitting-a-xep/" target="_blank">http://xmpp.org/xmpp-protocols/xmpp-extensions/submitting-a-xep/</a><br>
><br>
>> Although the usefulness of read receipts is debatable, it would make sense<br>
>> for all clients to implement them in the same way.<br>
><br>
> I agree.<br>
<br>
</div>Although I question the usefulness of spending time and energy defining<br>
an extension whose usefulness we find debatable, I wonder: what would<br>
the user experience be here? Do I need to click a button verifying that<br>
I have read and understood each message (say, before the client will<br>
show me another message)?<br>
<span class="HOEnZb"><font color="#888888"><br>
Peter<br>
<br>
--<br>
Peter Saint-Andre<br>
<a href="https://stpeter.im/" target="_blank">https://stpeter.im/</a><br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
_______________________________________________<br>
JDev mailing list<br>
Info: <a href="http://mail.jabber.org/mailman/listinfo/jdev" target="_blank">http://mail.jabber.org/mailman/listinfo/jdev</a><br>
Unsubscribe: <a href="mailto:JDev-unsubscribe@jabber.org">JDev-unsubscribe@jabber.org</a><br>
_______________________________________________<br>
</div></div></blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>JDev mailing list</span><br><span>Info: <a href="http://mail.jabber.org/mailman/listinfo/jdev">http://mail.jabber.org/mailman/listinfo/jdev</a></span><br><span>Unsubscribe: <a href="mailto:JDev-unsubscribe@jabber.org">JDev-unsubscribe@jabber.org</a></span><br><span>_______________________________________________</span><br></div></blockquote></body></html>