XSF Discussion - 2023-06-14

https://dev.gajim.org/gajim/gajim/uploads/a21f0d387ed20da39ee462d95284629f/image.png

MattJ, ^

This is a first draft what a reply rendererd in Gajim could look like

Imagine under the "Look nice" further quotes, i dont find this weird looking at all

Is there a draft of a xep about "sync'ing incoming msg read state between clients"? AFAIU, this is done via <displayed> message markers but it's not optimal because (a) that's too much traffic in large MUCs and (b) you might want to "mark something as read" without the other party(ies) being notified that you've read. Are there other reasons why clients don't just send <displayed> markers all the time?

i think there was some talks about it, but you are right, markers are not intended for that and are only a bad workaround

i imagine something via PEP is probably better suited for the task

so you think it would need a new XEP? I was wondering if an update on markers wouldn't be an option, along the lines of `<msg to="myself"><displayed id="the id" jid="the_muc_or_the_contact@somewhere">`

Sounds like another workaround

if you design this from ground up, i would say flooding your MAM Archive with thousands of read markers who are irrelevant, and only the last 10 are relevant is probably not a good solution

There could be something server side that helps us keep track of read states, if one would design this new, or at least with pubsub we do this with a lot of other things already

i care about the current omemo devicelist, i care about the current running music track

i care about the current readstate of chats

sounds like something i would start with .. but i think others already had thoughts about this, and maybe better ideas

https://xmpp.org/extensions/xep-0430.html

maybe this here

Yeah, I'm expecting to work on stuff in this area soon

But I want to do a get a few MUC improvements done first

MAM is also not optimal for the normal display markers, for its usecase of mark something as read

i wonder percentage wise how much of a archive consists of message markers

if the server could store markers in some other archive, and keep only the most current one, and clients could simply query this other archive independent from MAM

Prosody already has a module for that 🙂

Well, it currently only does MUC, but it would be easy enough to do normal messages

whats the name?

I see, filling MAM with markers does not sound optimal indeed. FWIW, in the walled gardens (at least telegram and whatsapp), you don't receive markers for other people's messages, just your own. And in telegram, in groups, you don't even know who has read your message, just that "someone has read it". I don't think I have time to start working o nthat, I was mostly curious,

i feel its useless in bigger MUCs

even the "someone has read your message"

like if i post something to a MUC with 100 people, i can expect someone will read it, no need to tell me about it

lovetox [09:13]: > whats the name? https://modules.prosody.im/mod_muc_markers.html

We use it in https://modules.prosody.im/mod_muc_rai to make an efficient way to find out which MUC rooms have unread messages without needing to join them