[jdev] Message Read Receipts

Spencer MacDonald spencer.macdonald.other at gmail.com
Tue May 14 07:57:37 UTC 2013


Out of interest how does one propose or suggest a XEP?

Although the usefulness of read receipts is debatable, it would make sense
for all clients to implement them in the same way.

Spencer


On Fri, May 10, 2013 at 11:02 AM, Philipp Hancke
<fippo at goodadvice.pages.de>wrote:

> On Fri, 10 May 2013, Dave Cridland wrote:
>
>  On Fri, May 10, 2013 at 2:11 AM, Peter Saint-Andre <stpeter at stpeter.im>
>> wrote:
>>       Thanks for sending your message. Unfortunately, I've only had time
>> to
>>       glance at the subject and haven't actually read it.
>>
>>
>> Right - true "read" receipts are impossible. But receipts are generally
>> about moving responsibility; hence XEP-0198 acks
>> move it to the next hop, XEP-0184 moves it to the client, and a read
>> receipt spec would move it to the user with an
>> explicit ack.
>>
>> I suspect there's actually little practical advantage to most people
>> above a simple response of "OK", but in military and
>> other critical environments it could well be useful, since then a client,
>> or server, can see messages have been
>> acknowledged - or have been missed.
>>
>
> This might be useful for offline messages, where you typically don't have
> an active conversation.
>
> ______________________________**_________________
> JDev mailing list
> Info: http://mail.jabber.org/**mailman/listinfo/jdev<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/79d86a4b/attachment.html>


More information about the JDev mailing list