Those would definitely do the job of keeping your conversations in sync across devices. We currently use message archiving.
Read status of a message is a separate problem though. How does a user know which messages need their attention? I'm suggesting a simple solution that tracks the last time you selected a conversation (similar to selecting an email). That timestamp can be matched up against the timestamp of individual messages to give you a good indication of which are unread. Example: 12:00 PM - You and I are chatting at noon. I am on my laptop. Client tells the server that 12:00 is the now the latest time I've viewed messages from you. 12:01 PM - I open my browser and begin browsing the web, inactivating my chat window. 12:05 PM - You send me a message. 12:30 PM - I step out to lunch and bring my phone with me. My phone knows that the last time we spoke was noon and displays the 12:05 messages as unread. On Mon, Apr 1, 2013 at 10:24 PM, Peter Saint-Andre <[email protected]>wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 4/1/13 7:48 PM, Noah Schwartz wrote: > > Unless I am missing something, those XEPs seem to solve different > > problems. 0085 tells you whats happening on the other end and 0184 > > seemingly by design is only delivery confirmation -- its beneficial > > to the sender, not the recipient. I am looking for something that > > helps the recipient know which of their messages still need their > > attention. With a user base switching between devices and > > potentially logging in and out very frequently, this can be very > > important. > > Oh, you're talking about managing my own incoming messages across > multiple devices under my control. Yes, that's a different problem. In > that case, consider the intersection of carbons and message archive > management: > > http://xmpp.org/extensions/xep-0280.html > > http://xmpp.org/extensions/xep-0313.html > > They are more recent and they don't necessarily explain how they work > together, but I think they might provide the building blocks you need. > > Peter > > - -- > Peter Saint-Andre > https://stpeter.im/ > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.18 (Darwin) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQIcBAEBAgAGBQJRWkFSAAoJEOoGpJErxa2pxL0P/3UMWauZim46lXCgTZzStTp6 > hpeRsYVHykiTSaBADzUn6FBkaLwxic8Kwg8dNW+KyxaIclBTr6AdjSuUNrFbFWny > viuWmNVyZBmMoY7JjI3Dcom30+L+9RNz9XTN/rTygthq122X21OO7EiWnrCeh8Bv > 4lJWE30tz5IdeROmAnupMIW4vV4H6qWzuL/7dDJ949iIpYjBUiocf9OLx/UaLnGd > cwfViFBdLrm2To7XQjxzxcRpESlwqP+6CrjuIpS0Jc0tiv4M6WIrTpiz1mH17wia > +LUcXn+iKFCBL9/GFX/0pm/ajVbxFB+UXEivwU7D8BTz7ra9OtlNVVv2grxisPpt > eo66rKjwBcjCcE3eLiQI7AQD98qBcqYpLSN3Ed02wmixanYu03oAMEgp10+yHeKG > q1vxgHOgBiWnDyXTGiH2VDgGHSCjnr9YhpEnmqR5t9wS6pYkWmTail9pZ7qs8Mt2 > oQFu934XEmZWT/XoDKaTC71K93tIMBMS60iftw19y88wI4U426PKiF8Ct62C5AA4 > jKQTZM2/4PmmjOzo4aJ7VIh+g2Cki9+PsNTrzKDJCHkUL9P78zqpRdRyNAdN79T5 > PYYjDrlmHTUD63SDwhEdbRvY54UqlPntud7+n655kynw27xpb99d//dg+rDqkHnF > 38SlCBhLW78ta+l5tppZ > =FbUS > -----END PGP SIGNATURE----- > -- Noah
