[jdev] Message Read Receipts

Noah Schwartz noah.schwartz1 at gmail.com
Tue May 14 13:20:17 UTC 2013


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.

Sent from my iPhone

On May 14, 2013, at 9:02 AM, Spencer MacDonald <spencer.macdonald.other at gmail.com> wrote:

> 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 <stpeter at stpeter.im> wrote:
>> On 5/14/13 4:07 AM, Matthew Wild wrote:
>> > On 14 May 2013 08:57, Spencer MacDonald
>> > <spencer.macdonald.other at gmail.com> 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: JDev-unsubscribe at jabber.org
>> _______________________________________________
> 
> _______________________________________________
> JDev mailing list
> Info: http://mail.jabber.org/mailman/listinfo/jdev
> Unsubscribe: JDev-unsubscribe at jabber.org
> _______________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/jdev/attachments/20130514/1f4afe99/attachment.html>


More information about the JDev mailing list