<div dir="ltr">Any thoughts either way on my "Chat Marker" proposal?<div><br></div><div style>The more I think about it the more it seems to be the correct solution.</div><div style><br></div><div style>The implementation is independent of Message Archiving and as it is only a marker the amount of storage and bandwidth required is minimal.</div>
<div style><br></div><div style>If people thing it is a good idea I can draft an XEP.</div><div style><br></div><div style>Regards</div><div style><br></div><div style>Spencer</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Thu, May 16, 2013 at 11:58 AM, Spencer MacDonald <span dir="ltr"><<a href="mailto:spencer.macdonald.other@gmail.com" target="_blank">spencer.macdonald.other@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div>So my suggestion is "Chat Markers", where you mark a given message with a Chat Maker.</div><div><br></div><div>So you could retrieve your chat makers between you and a given jid:</div><div><br>
</div><div><iq type='get' id='chat-marker-1'></div><div><span style="white-space:pre-wrap"> </span><query xmlns='urn:xmpp:chat-marker:tmp'></div><div><span style="white-space:pre-wrap"> </span><with><a href="mailto:juliet@example.com" target="_blank">juliet@example.com</a></with></div>
<div><span style="white-space:pre-wrap"> </span></query></div><div></iq></div><div><br></div><div>You would then receive the 'read' and 'received' chat marker between the you and the other jid.</div>
<div><br></div><div><iq to='<a href="http://romeo@example.com/phone" target="_blank">romeo@example.com/phone</a>' type='result' id='chat-marker-1'></div><div><span style="white-space:pre-wrap"> </span><query xmlns='urn:xmpp:chat-marker:tmp'></div>
<div><span style="white-space:pre-wrap"> </span><read to='<a href="mailto:juliet@example.net" target="_blank">juliet@example.net</a>' id='message-3' xmlns="urn:xmpp:chat-marker:tmp"/></div>
<div><span style="white-space:pre-wrap"> </span><received to='<a href="mailto:juliet@example.net" target="_blank">juliet@example.net</a>' id='message-3' xmlns="urn:xmpp:chat-marker:tmp"/></div>
<div><span style="white-space:pre-wrap"> </span></div><div><span style="white-space:pre-wrap"> </span><read from='<a href="mailto:juliet@example.net" target="_blank">juliet@example.net</a>' id='message-1' xmlns="urn:xmpp:chat-marker:tmp"/></div>
<div><span style="white-space:pre-wrap"> </span><received from='<a href="mailto:juliet@example.net" target="_blank">juliet@example.net</a>' id='message-2' xmlns="urn:xmpp:chat-marker:tmp"/></div>
<div>
<span style="white-space:pre-wrap"> </span></query></div><div></iq></div><div><br></div><div>You can update you Chat Markers like so:</div><div><br></div><div> <iq type='set' id='chat-marker-2'></div>
<div> <span style="white-space:pre-wrap"> </span><chat-markers xmlns='urn:xmpp:chat-marker:tmp'></div><div><span style="white-space:pre-wrap"> </span> <span style="white-space:pre-wrap"> </span><with><a href="mailto:juliet@example.net" target="_blank">juliet@example.net</a></with></div>
<div><span style="white-space:pre-wrap"> </span><read>message-4</read></div><div><span style="white-space:pre-wrap"> </span><received>message-4</read></div><div> <span style="white-space:pre-wrap"> </span></chat-markers></div>
<div> </iq></div><div> </div><div>These would be pushed to your other devices</div><div> </div><div><iq to='<a href="http://romeo@example.com/tablet" target="_blank">romeo@example.com/tablet</a>' type='set' id='chat-marker-3'></div>
<div><span style="white-space:pre-wrap"> </span><query xmlns='urn:xmpp:chat-marker:tmp'></div><div><span style="white-space:pre-wrap"> </span><read to='<a href="mailto:juliet@example.net" target="_blank">juliet@example.net</a>' id='message-4' xmlns="urn:xmpp:chat-marker:tmp"/></div>
<div><span style="white-space:pre-wrap"> </span><received to='<a href="mailto:juliet@example.net" target="_blank">juliet@example.net</a>' id='message-4' xmlns="urn:xmpp:chat-marker:tmp"/></div>
<div><span style="white-space:pre-wrap"> </span></query></div>
<div></iq></div><div><br></div><div>and to other user's devices</div><div><br></div><div><iq to='<a href="http://juliet@example.com/phone" target="_blank">juliet@example.com/phone</a>' type='set' id='chat-marker-3'></div>
<div><span style="white-space:pre-wrap"> </span><query xmlns='urn:xmpp:chat-marker:tmp'></div><div><span style="white-space:pre-wrap"> </span><read from='<a href="mailto:romeo@example.net" target="_blank">romeo@example.net</a>' id='message-4' xmlns="urn:xmpp:chat-marker:tmp"/></div>
<div><span style="white-space:pre-wrap"> </span><received from='<a href="mailto:romeo@example.net" target="_blank">romeo@example.net</a>' id='message-4' xmlns="urn:xmpp:chat-marker:tmp"/></div>
<div><span style="white-space:pre-wrap"> </span></query></div>
<div></iq></div><div><br></div><div>Regards</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Spencer</div><div><br></div><div><br></div></font></span></div><div class="gmail_extra"><br><br><div class="gmail_quote">
<div><div class="h5">On Thu, May 16, 2013 at 9:59 AM, Jon Doyle <span dir="ltr"><<a href="mailto:jdoyle@communigate.com" target="_blank">jdoyle@communigate.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div style="word-wrap:break-word">Hello;<div><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;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<div><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.<u></u><u></u></span></i></b></p>
</div></div></blockquote><br></div></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></div><br></div></div><div class="im">_______________________________________________<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" target="_blank">JDev-unsubscribe@jabber.org</a><br>
_______________________________________________<br>
<br></div></blockquote></div><br></div>
</blockquote></div><br></div>