Re: [Standards] MAM Sync Strategies

I may have misunderstood, but if we're only fetching the last message the first time, do you start out with no history? Also, why set "before" at all if it's only one message, the direction won't matter, no? —Sam On Fri, Aug 27, 2021, at 09:34, Thilo Molitor wrote: > When the user first sets up

Re: [Standards] MAM Sync Strategies

Am Freitag, 27. August 2021, 17:20:17 CEST schrieb Andrew Nenakhov: > пт, 27 авг. 2021 г. в 18:08, Thilo Molitor : > > That's not quite right, you can use XEP-0353 together with XEP-0198 and/or > > XEP-0313 to make VoIP work on iOS. > > No. You can not. > > In a sense that the call recipient has

Re: [Standards] MAM Sync Strategies

пт, 27 авг. 2021 г. в 18:08, Thilo Molitor : > > That's not quite right, you can use XEP-0353 together with XEP-0198 and/or > XEP-0313 to make VoIP work on iOS. > > No. You can not. In a sense that the call recipient has several devices, which all start ringing when the call is incoming and stop

Re: [Standards] MAM Sync Strategies

Am Freitag, 27. August 2021, 13:12:44 CEST schrieb Sam Whited: > Thanks JC! > > You're right, I should have mentioned gaps. It's still possible to > have them in a desktop client because it could always close before it > finishes paging through catching up on history. I had planned to solve >

Re: [Standards] MAM Sync Strategies

Am Freitag, 27. August 2021, 16:03:19 CEST schrieb Philipp Hörist: > Thilo Molitor schrieb am Fr., 27. Aug. 2021, 15:35: > > every MUC catchup delays only "live" message stanzas for that MUC, not > > other MUCs or 1:1). > > How can you delay live messages from a muc ? I filter them by

Re: [Standards] Renaming XEP "Draft" stage to "Stable"

Hi Le 2021-08-26 18:45, Matthew Wild a écrit : In practice a XEP only reaches "Draft" stage when it has a bunch of implementation experience, and Council believes it looks ready for broad adoption. I don't think (and checking XEP-0001 tends to confirm) that any implementation is needed to

Re: [Standards] MAM Sync Strategies

Thilo Molitor schrieb am Fr., 27. Aug. 2021, 15:35: > > every MUC catchup delays only "live" message stanzas for that MUC, not > other MUCs or 1:1). > How can you delay live messages from a muc ? Lovetox > ___ Standards mailing list Info:

Re: [Standards] MAM Sync Strategies

Hi Sam et al, for Monal we do something a bit different (a mixture of what you wrote and what JC wrote): When the user first sets up a new account, we query the archive with end= and RSM {max=1, before=""} The stanza-id of this message is then used as sync point the next time Monal has to do

Re: [Standards] MAM Sync Strategies

> Not quite. XEP-0430 is a (rather weak) imitation of the XEP-SYNC which was > already done (and implemented) when Inbox was proposed. It supports > delivered/read/unread messages, active calls in chat (without it, VoIP > calls won't work on iOS) That's not quite right, you can use XEP-0353

Re: [Standards] MAM Sync Strategies

On 27.08.21 13:12, Sam Whited wrote: Thanks JC! You're right, I should have mentioned gaps. It's still possible to have them in a desktop client because it could always close before it finishes paging through catching up on history. I had planned to solve that by either switching to committing

Re: [Standards] MAM Sync Strategies

On 27.08.21 13:12, Andrew Nenakhov wrote: пт, 27 авг. 2021 г. в 16:03, JC Brand >: If the site allows users to show multiple chats side-by-side then you can't discard chat history. Ok, so you have users that use so many simultaneous chats and scroll

Re: [Standards] MAM Sync Strategies

Thanks JC! You're right, I should have mentioned gaps. It's still possible to have them in a desktop client because it could always close before it finishes paging through catching up on history. I had planned to solve that by either switching to committing the entire query in one transaction, or

Re: [Standards] MAM Sync Strategies

пт, 27 авг. 2021 г. в 16:03, JC Brand : > > If the site allows users to show multiple chats side-by-side then you > can't discard chat history. > Ok, so you have users that use so many simultaneous chats and scroll them up and down that fast, so you can't ever dump the messages starting from,

Re: [Standards] MAM Sync Strategies

On 27.08.21 12:56, Andrew Nenakhov wrote: пт, 27 авг. 2021 г. в 15:53, JC Brand >: I know from professional experience that you can reach the 5MB limit with an integrated webchat of the type I mentioned. then just discard chat history (bar the last

Re: [Standards] MAM Sync Strategies

пт, 27 авг. 2021 г. в 15:53, JC Brand : > > I know from professional experience that you can reach the 5MB limit with > an integrated webchat of the type I mentioned. > then just discard chat history (bar the last message) you haven't touched in a while. Loading history from the archive again is

Re: [Standards] MAM Sync Strategies

пт, 27 авг. 2021 г. в 14:52, Holger Weiß : > * Andrew Nenakhov [2021-08-27 14:45]: > >our quick sync protocol that loads every first message from all chats, > > This sounds like a non-standard replacement for XEP-0430: Inbox? > Not quite. XEP-0430 is a (rather weak) imitation of the XEP-SYNC

Re: [Standards] MAM Sync Strategies

On 27.08.21 12:20, Andrew Nenakhov wrote: пт, 27 авг. 2021 г. в 14:52, JC Brand >: Converse is made so that it can be integrated into a website where the user might be clicking many links and navigate throughout the site, thereby causing the page to

Re: [Standards] MAM Sync Strategies

пт, 27 авг. 2021 г. в 14:52, JC Brand : > Converse is made so that it can be integrated into a website where the > user might be clicking many links and navigate throughout the site, thereby > causing the page to regularly refresh/reload. If you don't cache/store the > messages somewhere, you'll

Re: [Standards] MAM Sync Strategies

On 27.08.21 11:45, Andrew Nenakhov wrote: пт, 27 авг. 2021 г. в 12:59, JC Brand >: Webclients have restrictions that others don't, so while what you wrote makes sense, I do something a bit different with Converse. Web clients do not need to store

Re: [Standards] MAM Sync Strategies

* Andrew Nenakhov [2021-08-27 14:45]: our quick sync protocol that loads every first message from all chats, This sounds like a non-standard replacement for XEP-0430: Inbox? Holger ___ Standards mailing list Info:

Re: [Standards] MAM Sync Strategies

пт, 27 авг. 2021 г. в 12:59, JC Brand : > > Webclients have restrictions that others don't, so while what you wrote > makes sense, I do something a bit different with Converse. > Web clients do not need to store messages locally at all, they can just load everything when a user goes to a dialog

Re: [Standards] MAM Sync Strategies

Hi Sam et al Webclients have restrictions that others don't, so while what you wrote makes sense, I do something a bit different with Converse. First, depending on the type of storage used (sessionStorage vs localStorage vs IndexedDB), a webclient can easily run into a storage limit (around