Re: [Standards] Unread syncing

On 14 December 2016 at 14:50, Kevin Smith wrote: > On 14 Dec 2016, at 11:46, Michal Piotrowski tions.com> wrote: > > > > On 2 December 2016 at 18:18, forenjunkie wrote: > >> Ah now im understanding, basically the

Re: [Standards] Unread syncing

On 14 Dec 2016, at 11:46, Michal Piotrowski wrote: > > > On 2 December 2016 at 18:18, forenjunkie > wrote: > Ah now im understanding, basically the server should give you a list of > contacts to

Re: [Standards] Unread syncing

On 2 December 2016 at 18:18, forenjunkie wrote: > Ah now im understanding, basically the server should give you a list of > contacts to query for messages. > > i would see this as a simply addition to MAM. > Would you see it as a new parameter to MAM query? or rather a

Re: [Standards] Unread syncing

Ah now im understanding, basically the server should give you a list of contacts to query for messages. i would see this as a simply addition to MAM. The Archive already could know what messages you read, because of chatmarkers. it would only need to hold the last read marker stanza id for

Re: [Standards] Unread syncing

> On 2 Dec 2016, at 16:03, forenjunkie wrote: > > Why would you querry the whole archive? Because the question isn't "do I have unread messages for contact X?" It's "in what chats do I have unread messages and how many?" on login. I don't see a way to solve this using

Re: [Standards] Unread syncing

Why would you querry the whole archive? if you open a chat with a contact you querry "Give me the last X messages for contact A" And if you open the chat window with contact B you do the same for contact B. I never did write a implementation of MAM myself, but if im reading the XEP, you

Re: [Standards] Unread syncing

On 2 Dec 2016, at 15:49, forenjunkie wrote: > > Its not written down somewhere that its up to the client, but it makes no > sense to put a selflimiting hard rule on a archiving XEP like MAM and exclude > certain messages per XEP rule. > > We have store hints, the

Re: [Standards] Unread syncing

Its not written down somewhere that its up to the client, but it makes no sense to put a selflimiting hard rule on a archiving XEP like MAM and exclude certain messages per XEP rule. We have store hints, the most prominent servers respect these. And it would make no sense to not respect it if

Re: [Standards] Unread syncing

On 2 Dec 2016, at 15:26, forenjunkie wrote: > in a single chat conversation, it makes no sense to query unread messages. I’m not sure that’s true at all, but putting that to the side for the minute... > you could just query the last 10 MAM Messages, if no readmarker comes

Re: [Standards] Unread syncing

Hi, in a single chat conversation, it makes no sense to query unread messages. you could just query the last 10 MAM Messages, if no readmarker comes with it, query another 10. such a implementation of MAM would be very weird to me, but you could do it and get only unread messages with it. So

Re: [Standards] Unread syncing

> On 2 Dec 2016, at 14:35, Christian Schudt wrote: > > >> Except that they’re not chat messages, so won’t be stored, and if they were >> you’d be potentially up to doubling the size of your archive (I guess adding >> a quarter to, on average) as you fill it with read

Re: [Standards] Unread syncing

> Except that they’re not chat messages, so won’t be stored, and if they were > you’d be potentially up to doubling the size of your archive (I guess adding > a quarter to, on average) as you fill it with read markers - unless you want > to customise the MAM service to understand unread state,

Re: [Standards] Unread syncing

> On 2 Dec 2016, at 13:42, Christian Schudt wrote: > >> I think you possibly don’t :) >> >> This is for synchronising the ‘read’ status between all of my clients, such >> that a) they’re consistent and b) when a new client comes online it can >> quickly determine

Re: [Standards] Unread syncing

Isn't MAM supposed to address the issue of "synchronizing multiple resources/clients", so that every client sees the same history of (chat) messages, even if they were originally delivered to another client?   If that syncing works for chat messages, it should work for "read receipt" messages

Re: [Standards] Unread syncing

> On 2 Dec 2016, at 13:00, Christian Schudt wrote: > > Can't XEP-0333 used for that? > > A sends a message to B with a "read request". > B reads the message and sends a "read receipt" back to A. > > The read receipt is stored in the server archive normally as any

Re: [Standards] Unread syncing

Can't XEP-0333 used for that?   A sends a message to B with a "read request". B reads the message and sends a "read receipt" back to A.   The read receipt is stored in the server archive normally as any other (chat) message.   Clients can query the archive in a normal way, e.g. all message

Re: [Standards] Unread syncing

> On 2 Dec 2016, at 11:44, Kevin Smith wrote: > > A question: > > I’ve always assumed that we would do sync of the unread (or, rather read) > status of messages between contacts via private PEP and, indeed, this is the > approach we verbally specced at a summit a while