Hi, Holger. This is actually a subject we know very much about. From our
experience, the absence of mandatory stable message IDs is the biggest
design flaw of XMPP as a protocol (resource priorities take the second
place), and fixing this was the first thing we did when we started
implementing our
On 22 Sep 2020, at 17:05, Jonas Schäfer wrote:
>
> Re: https://github.com/xsf/xeps/pull/983
>
> I have a very simple technical question: Why do this instead of ensuring that
> special characters are URL-encoded for the node ID in the PubSub URIs? This
> seems to be fixing the issue at the
https://logs.xmpp.org/council/2020-09-23?p=h#2020-09-23-d48e1db20c2de925
1) Roll Call
Present: Jonas, Zash, Daniel, Dave
Apologies: Georg
2) Agenda Bashing
Zash wonders about Reactions.
3) (No) Editor's Update
Jonas is still catching up on things.
4a) PR #983 (XEP-0060: Disallow '=' and ';' in
On Mon, 28 Sep 2020 at 15:44, Holger Weiß wrote:
> * Dave Cridland [2020-09-28 09:51]:
> > The implication here is that the MAM messages returned are redundant
> data,
> > and what we're looking to do is optimize for that case.
> >
> > However, for all outgoing messages from a session which are
* Dave Cridland [2020-09-28 09:51]:
> The implication here is that the MAM messages returned are redundant data,
> and what we're looking to do is optimize for that case.
>
> However, for all outgoing messages from a session which are not the last
> messages of that session, any "ack" purely to
On Mon, 28 Sep 2020 at 11:03, Ruslan N. Marchenko wrote:
> Am Montag, den 28.09.2020, 09:51 +0100 schrieb Dave Cridland:
> >
> >
> > On Sun, 27 Sep 2020 at 16:46, Holger Weiß
> > wrote:
> > >
> > > I think it would be good to find a better solution.
> >
> > OK, just out of curiosity, why?
>
> I
Am Montag, den 28.09.2020, 09:51 +0100 schrieb Dave Cridland:
>
>
> On Sun, 27 Sep 2020 at 16:46, Holger Weiß
> wrote:
> >
> > I think it would be good to find a better solution.
>
> OK, just out of curiosity, why?
I for one want that to be formalized.
So far the formal response to that
On Sun, 27 Sep 2020 at 16:46, Holger Weiß wrote:
> When opening a new session, MAM clients might want to use the
> most-recent known XEP-0359 stanza ID to sync messages. One problem they
> face is that there's no way to figure out the stanza ID of outgoing
> messages, short of actually querying