[Standards] Re: UPDATED: XEP-0333 (Displayed Markers (was: Chat Markers))

2024-03-26 Thread Daniel Gultsch
On Tue, Mar 26, 2024 at 1:40 PM Andrew Nenakhov wrote: > > Well, on the other hand, since the only scenario I can imagine using > in the wild has significantly different semantics from > readdisplayed markers, I think that this is not really necessary in this XEP. The part I was considering

[Standards] Re: UPDATED: XEP-0333 (Displayed Markers (was: Chat Markers))

2024-03-26 Thread Andrew Nenakhov
Well, on the other hand, since the only scenario I can imagine using in the wild has significantly different semantics from readdisplayed markers, I think that this is not really necessary in this XEP. On Tue, 26 Mar 2024 at 17:34, Daniel Gultsch wrote: > On Tue, Mar 26, 2024 at 1:11 PM Dave

[Standards] Re: UPDATED: XEP-0333 (Displayed Markers (was: Chat Markers))

2024-03-26 Thread Daniel Gultsch
On Tue, Mar 26, 2024 at 1:11 PM Dave Cridland wrote: > 3) It's really not. Some clients and intermediaries need to know whether they > should expect a marker or not. No need to check this prior to sending a > , true, but useful to track missing markers afterward. > > Where was the discussion

[Standards] Re: UPDATED: XEP-0333 (Displayed Markers (was: Chat Markers))

2024-03-26 Thread Andrew Nenakhov
As I said earlier, some day down the road can actually be useful: > But I could see this feature useful for something like voice/video messages to indicate that it has been played by the recipient. At least, Telegram does have such feature (not in group chats though, there it makes no sense and

[Standards] Re: UPDATED: XEP-0333 (Displayed Markers (was: Chat Markers))

2024-03-26 Thread Dave Cridland
I entirely missed this, and have no understanding of the rationale, but: 1) I'm somewhat ambivalent about removing , but it's certainly well implemented by my anecdotological studies. 2) Removing seems OK, but I've considered various use-cases for which an explicit, user-driven, acknowledgement