Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

On 13/09/2021 16.15, Kim Alvefur wrote: On Thu, Sep 09, 2021 at 04:29:37PM +0100, Kevin Smith wrote: To summarise what I’ve said before: MUC in MAM kinda sucks, but groupchat doesn’t (necessarily) mean MUC. Sometimes people want groupchat messages in their archive because they want their

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

Hi, On Thu, Sep 09, 2021 at 04:29:37PM +0100, Kevin Smith wrote: To summarise what I’ve said before: MUC in MAM kinda sucks, but groupchat doesn’t (necessarily) mean MUC. Sometimes people want groupchat messages in their archive because they want their archive to represent all those messages

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

To summarise what I’ve said before: MUC in MAM kinda sucks, but groupchat doesn’t (necessarily) mean MUC. Sometimes people want groupchat messages in their archive because they want their archive to represent all those messages they received on any client, either for online searching, or

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

* Dave Cridland [2021-09-08 10:50]: [Spoofing of the Forwarded element] > I can agree with this in principle, though the query id within MAM > queries dramatically lessens the scope for an attack here. I'm aware of this point. However, many implementations process stanzas in callback functions

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

On Tue, 7 Sept 2021 at 16:23, Georg Lukas wrote: > Hello everyone, > > given that XEP-0313 is up for recall in tomorrow's Council meeting, I'd > like to sort my long list of issues into blocking and non-blocking. > Fixing the blocking ones is a requirement for me to change my vote to > something

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

* Kevin Smith [2021-09-07 18:41]: > At the risk of repeating myself, I think that storing groupchat messages in > the user archives is helpful, and people do this in the wild. Right, I remember hearing that before, and IIRC the reason for that was to allow for server-side message search? Now I

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

* Georg Lukas [2021-09-07 17:22]: Furthermore, I'm not sure if messages received by a client from offline history are supposed to contain the respective MAM-ID, so deduplicating here might be very adventurous, as the same message might arrive from offline history without a MAM ID and from MAM

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

On 7 Sep 2021, at 16:22, Georg Lukas wrote: >> §6.1.1: the business rules for user archives are inadequate: >> >> MUC messages in user archive: I think that implementation practice has >> clearly shown that storing MUC messages in the user archive is a Bad >> Idea, and nobody is doing it anyway.

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

Hello everyone, given that XEP-0313 is up for recall in tomorrow's Council meeting, I'd like to sort my long list of issues into blocking and non-blocking. Fixing the blocking ones is a requirement for me to change my vote to something different than -1. Two blocking (non-Editorial) issues: *

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

On 20 Apr 2021, at 11:22, Kevin Smith wrote: > > Somewhat belatedly... > >> On 16 Mar 2021, at 20:20, Jonas Schäfer (XSF Editor) >> wrote: >> >> This message constitutes notice of a Last Call for comments on >> XEP-0313. >> >> Title: Message Archive Management >> Abstract: >> This document

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

Somewhat belatedly... > On 16 Mar 2021, at 20:20, Jonas Schäfer (XSF Editor) > wrote: > > This message constitutes notice of a Last Call for comments on > XEP-0313. > > Title: Message Archive Management > Abstract: > This document defines a protocol to query and control an archive of >

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

* Jonas Schäfer [2021-03-16 21:23]: > 1. Is this specification needed to fill gaps in the XMPP protocol > stack or to clarify an existing protocol? Yes. > 2. Does the specification solve the problem stated in the introduction > and requirements? Mostly yes. > 3. Do you plan to implement this

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

On Tue, Mar 16, 2021 at 08:20:06PM -, Jonas Schäfer wrote: This message constitutes notice of a Last Call for comments on XEP-0313. Title: Message Archive Management Abstract: This document defines a protocol to query and control an archive of messages stored on a server. URL:

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

On Tue, 16 Mar 2021 at 20:21, Jonas Schäfer wrote: > This message constitutes notice of a Last Call for comments on > XEP-0313. > > Title: Message Archive Management > Abstract: > This document defines a protocol to query and control an archive of > messages stored on a server. > > URL:

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

On Tue, Mar 16, 2021, at 16:20, Jonas Schäfer wrote: > This message constitutes notice of a Last Call for comments on > XEP-0313. Thank you! > 1. Is this specification needed to fill gaps in the XMPP protocol >stack or to clarify an existing protocol? Yes, this specification is already

[Standards] LAST CALL: XEP-0313 (Message Archive Management)

This message constitutes notice of a Last Call for comments on XEP-0313. Title: Message Archive Management Abstract: This document defines a protocol to query and control an archive of messages stored on a server. URL: https://xmpp.org/extensions/xep-0313.html This Last Call begins today and

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

  24.11.2017, 18:36, "Matthew Wild" :On 19 November 2017 at 16:54, Konstantin Kozlov wrote: The main problem I see so far is inability to determine for which dates message archive is available without reading the whole archive. Author of Vacuum IM (which is an

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

On 19 November 2017 at 16:54, Konstantin Kozlov wrote: > The main problem I see so far is inability to determine for which dates > message archive is available without reading the whole archive. > Author of Vacuum IM (which is an upstream of my client) tried to implement >

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

Hello!17 нояб. 2017 г. 20:22 пользователь Matthew Wild написал:On 15 November 2017 at 17:32, Kozlov Konstantin wrote: > That's nice! > This XEP is still too raw. Just out of curiosity, care to share your thoughts on what needs polish? I don't disagree

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

On 18.11.2017 17:14, Philipp Hörist wrote: Why would a server allow that if it has no use case and leads to problems? When a client sets the preferences the server replies with the full pref list, this gives the server the possibility to refuse some entries. The XEP also states note that

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

Why would a server allow that if it has no use case and leads to problems? When a client sets the preferences the server replies with the full pref list, this gives the server the possibility to refuse some entries. The XEP also states note that due to server policies these MAY be different to

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

On 05.11.2017 19:21, Ruslan N. Marchenko wrote: Hi, On 16.10.2017 20:38, Jonas Wielicki (XSF Editor) wrote: 5. Is the specification accurate and clearly written? The first thing I stumbled upon while starting drafting implementation is - empty result. ? ? 0? Or perhaps even ? Some more

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

That's nice!This XEP is still too raw.15.11.2017, 19:58, "Sam Whited" :Given the feedback on this thread, the council voted today NOT toadvance XEP-0313 to draft.The XEP will return to experimental until some of the feedback isaddressed.—SamOn Mon, Oct 16, 2017, at 12:38, Jonas

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

* Jonas Wielicki [2017-10-16 18:38]: > 4. Do you have any security concerns related to this specification? As I understood it, the reasoning for the last namespace bump to mam:2 was to offer the guarantee that stanza IDs are added to live messages as per XEP-0359. So if the

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

Given the feedback on this thread, the council voted today NOT to advance XEP-0313 to draft. The XEP will return to experimental until some of the feedback is addressed. —Sam On Mon, Oct 16, 2017, at 12:38, Jonas Wielicki wrote: > This message constitutes notice of a Last Call for comments on >

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

On 14.11.2017 16:38, Kim Alvefur wrote: > On Mon, Oct 16, 2017 at 06:38:45PM -, Jonas Wielicki wrote: >> This message constitutes notice of a Last Call for comments on >> XEP-0313. >> 5. Is the specification accurate and clearly written? > > I also think that the way preferences are returned

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

On Mon, Oct 16, 2017 at 06:38:45PM -, Jonas Wielicki wrote: > This message constitutes notice of a Last Call for comments on > XEP-0313. > > Abstract: > This document defines a protocol to query and control an archive of > messages stored on a server. > > This Last Call begins today and

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

[XEP-0313 for LC] I have three points to make. a) What to store: As already mentioned by Jonas and Kevin, the business rules in §5.1.1 are only a first approximation of what we want to persist, and we need to figure out better / more explicit ways to determine persistent / transient messages.

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

Hi, On 16.10.2017 20:38, Jonas Wielicki (XSF Editor) wrote: This message constitutes notice of a Last Call for comments on XEP-0313. Abstract: This document defines a protocol to query and control an archive of messages stored on a server. This Last Call begins today and shall end at the

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

On 03.11.2017 21:35, Kevin Smith wrote: >> On 27 Oct 2017, at 12:19, Florian Schmaus wrote: >> On 16.10.2017 20:38, Jonas Wielicki (XSF Editor) wrote: >>> This message constitutes notice of a Last Call for comments on >>> XEP-0313. >>> >>> Abstract: >>> This document defines a

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

> On 27 Oct 2017, at 12:19, Florian Schmaus wrote: > > On 16.10.2017 20:38, Jonas Wielicki (XSF Editor) wrote: >> This message constitutes notice of a Last Call for comments on >> XEP-0313. >> >> Abstract: >> This document defines a protocol to query and control an archive

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

On 26 Oct 2017, at 09:58, Jonas Wielicki wrote: > > On Montag, 16. Oktober 2017 18:38:45 CEST Jonas Wielicki wrote: >> This message constitutes notice of a Last Call for comments on >> XEP-0313. >> >> Abstract: >> This document defines a protocol to query and control an

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

On Montag, 16. Oktober 2017 18:38:45 CET Jonas Wielicki wrote: > This message constitutes notice of a Last Call for comments on > XEP-0313. > > Abstract: > This document defines a protocol to query and control an archive of > messages stored on a server. > > This Last Call begins today and shall

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

On 27 October 2017 at 12:19, Florian Schmaus wrote: > I think references to PubSub in XEP-0313 should either be removed or > clarified before this XEP should advance. > > I'd also like to encourage the authors to strip XEP-0313 to a minimum of > what is requirement to perform

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

On Montag, 16. Oktober 2017 18:38:45 CEST Jonas Wielicki wrote: > This message constitutes notice of a Last Call for comments on > XEP-0313. > > Abstract: > This document defines a protocol to query and control an archive of > messages stored on a server. > > This Last Call begins today and

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

Hi, On 16 October 2017 at 20:38, Jonas Wielicki wrote: > This message constitutes notice of a Last Call for comments on > XEP-0313. > > Abstract: > This document defines a protocol to query and control an archive of > messages stored on a server. > > This Last Call begins

[Standards] LAST CALL: XEP-0313 (Message Archive Management)

This message constitutes notice of a Last Call for comments on XEP-0313. Abstract: This document defines a protocol to query and control an archive of messages stored on a server. This Last Call begins today and shall end at the close of business on 2017-10-30. Please consider the following