Re: [Standards] Confusing Language in XEP-0261 (Jingle In-Band Bytestreams Transport Method)

On 1/12/19 1:01 PM, Jonas Schäfer wrote: > On Montag, 17. Dezember 2018 16:50:17 CET Sebastian Riese wrote: >> XEP-0261 uses "bytestream" >> for the overall Jingle session and "session" for the IBB session (at >> least it does so consistently). This is *e

Re: [Standards] Proposed XMPP Extension: XMPP Compliance Suites 2019

* ??? ?? [2019-01-14 14:16]: > > If you don't do this, read markers will sometimes work and sometimes > > not. You'd accept this UX breakage in order to save the server operator > > some disk space? > > Problem is not inefficient disk space utilization. Problem is that > instead of devel

Re: [Standards] Proposed XMPP Extension: XMPP Compliance Suites 2019

> If you don't do this, read markers will sometimes work and sometimes > not. You'd accept this UX breakage in order to save the server operator > some disk space? Problem is not inefficient disk space utilization. Problem is that instead of developing a proper solution, this ad-hoc approach is p

Re: [Standards] Proposed XMPP Extension: XMPP Compliance Suites 2019

* ??? ?? [2018-12-25 00:32]: > Actually biggest issue are offline clients. Some developers even spam > message archive with empty messages to 'mark' previous messages as read. > Not a good idea. If you don't do this, read markers will sometimes work and sometimes not. You'd accept this U

Re: [Standards] XMPP Council Minutes 2018-12-19

On 13 Jan 2019, at 11:29, Jonas Schäfer wrote: > > On Dienstag, 25. Dezember 2018 17:43:28 CET Kevin Smith wrote: >>> On 20 Dec 2018, at 20:27, Tedd Sterr wrote: >>> Dave noticed that Jonas pushed through XEP-0412 (XMPP Compliance Suites >>> 2019) before all votes have been made, and has literal