Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Missed MAM messages beyond a number of 50 are permanently lost #1548
This is similar to #1534, but I think it's different enough to warrant a separate issue.
The problem is triggered as follows:
Messages "52" through "100" are now permanently lost. Even if the user refreshes/rejoins, Converse will only query MAM for messages created after message "101".
I propose the short-term fix of actually implementing paging in
In the long term, this might not be very sustainable though. In case of a long absence from a MUC, this method will query for all messages left since the user was last online, which could be quite a lot in case of an active MUC. Ideally, Converse would request only the 50 most recent messages then page upwards/backwards as needed. However, implementing that in the current architecture would cause even more missed messages because of #1534 (Converse would request messages "50" through "100", but then messages "1" through "49" would be permanently lost, as it's not aware that there might be more unretrieved messages between "1" and "50")