jdev - 2025-01-10

> I wanted to make a client like telegram in that it lets you properly search chat history (e.g. if you find a message, you can scroll up to that message, no matter if it's on the server or already cached). The mam xep hasn't turned out that friendly to partial, arbitary archive parts fetches, because it lacks sortable message ids, and neither can you rely on time alone. So I'm not sure how msg cache could even work then, it'd have to be a linked list? lol. In recent Cheogram versions, if I reply to a message like I am doing in this message, I am able to click on the replying message and it will jump to the message being replied to. What xep is that and how should the client behave if it doesn't have that message in cache? Fetching it from mam directly can create a hole. Fetching mam all the way up to that message? Would be fun if that message was a year old ↺

A XEP describes how data is transmitted. Not what a click in a client on a UI element does

If you want to know how cheogram is doing it you will need to read the source code or ask the developer

If a message is not there Gajim simply shows message is not available. No fetching will happen

If you always fetch mam since last message you will not get into this situation

Or only in rare edge cases