<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><base href="x-msg://2683/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hello;<div><div><blockquote type="cite"><div lang="DE" link="blue" vlink="purple" style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div class="WordSection1" style="page: WordSection1; "><p style="margin-right: 0cm; margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', serif; "><b><i><span lang="EN-US" style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">[JH] I do think another interesting case is where the message is in fact “read” by a agent/bot/program (e.g. service bots or even M2M messaging), a timestamped receipt request is in fact helpful as there is a temporal difference between the reception, processing and response to a message – would be a real-world case 1 example.<o:p></o:p></span></i></b></p></div></div></blockquote><br></div><div>I can see the value, and would propose that really means some "tangible" action must occur for it to be a valid "receipt". No different than in the human world where I sign for an envelope at the front door. I say this because what you are saying is that the "value" here is to show the "forensic" data, that "time-stamp" you mention. It should in fact be the record of when the button was pushed, or the app "signed off" on receipt. It could include a variety of things, the other side can see a display (client side) of "read", but the data around that transaction could be stored as a "receipt" which could be used in a lot of business or forensic applications. All of which in theory could have tremendous value in a variety of usage model cases. </div><div><br></div><div>I think all of us that have used Skype or iMessage know about the challenges of "message receipt" in a multi-cleint scenario. </div><div><br></div><div>Regards,</div><div><br></div><div>Jon</div><br></div></body></html>