Thanks Matthew, Very cool. I actually hadn't seen XEP-0313 until this thread. We've been using a subset a subset of XEP-0136 but, it looks like XEP-0313 is what we really want.
This could definitely work off of message ID and as an extension of XEP-0313 I think as long as message ID's conveyed some sort of order. Otherwise, it could just go by timestamp. Whats the process for extending or creating new XEPs? Noah On Tue, Apr 2, 2013 at 11:13 AM, Matthew Wild <[email protected]> wrote: > On 2 April 2013 14:33, Noah Schwartz <[email protected]> wrote: > > 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. > > > > I think that would be a simple enough XEP, if it re-used XEP-0313 or > such, for each client to indicate its last read message id. > > XEP-0280 and XEP-313 are still under development, so we're open to any > suggestions you might have to make this possible (though I think the > mechanism itself belongs in another XEP). > > Regards, > Matthew > -- Noah
