Can't load history of my conversation with Cyril
It is specific of my conversation with Cyril. I can load the rest of my conversations without any issue. See for yourself:
Here is the full JS console log:
community.startinblox.com-1604587178118.log
Sophie reported a similar behavior yesterday in her one-to-one converation with Sylvain
Link issues together to show that they're related. Learn more.
Activity
- Jean-Baptiste Pasquier assigned to @XaviFP
assigned to @XaviFP
- Benoit Alessandroni mentioned in issue #217 (closed)
mentioned in issue #217 (closed)
- Owner
Retrograding to bug-s2 as related to performance & #211 (closed) implementation.
Closing in favor of #199
Edited by Jean-Baptiste Pasquier - Jean-Baptiste Pasquier closed
closed
- Alex reopened
reopened
- Owner
Not related to #211 (closed) and #199 (See #199 (comment 41523) )
Reloading or logging out and back in doesn't solve the problem. If I scroll up to trigger the fetching of previous history, it doesn't bring it back. I'm only accessing new messages on the client side.
@XaviFP Any idea of what could happen here?
- Jean-Baptiste Pasquier assigned to @manv and unassigned @XaviFP
- Developer
I think i found the issue
Converse is currently fetching the latest 30 stanzas (defined in archived_messages_page_size)
So it might contain presence stanzas, showing less than 30 real messages (sometimes none)
Edited by Emmanuel Vodor - Author Maintainer
Yes, that corresponds to what @MattJ indicated a couple of times.
Our problem is that we're bloating history with such non-displayed stanzas which often proves problematic. What's the envisioned solution?
- Developer
Ah okok
One solution would be to fetch history until there's 30 rendered messages
But I'm not sure performance wise if it's a good idea
Edited by Emmanuel Vodor - Owner
Well, is there any way to not request other messages? Or not save them. Whatever, as we don't need them, we already removed a lot of them - like the presence stanza for instance - with Xavier, some may be still here.
- Author Maintainer
@MattJ Any educated guess about the way to move forward here?
- Developer
@jbpasquier I think the problem will persist anyway once we have reactions, because each count as a message
the nice thing would be to get the oldest real message (max 30) then query all the messages until that point
I didn't find anything that much interesting in the spec (https://xmpp.org/extensions/xep-0313.html)
@MattJ would it be possible to have something like this on Prosody side? Like some kind of MAM extension
Edited by Emmanuel Vodor - Owner
Reactions will get served on those 30 messages? Could we ask to not retrieve them, then retrieve them message per message?
- Developer
@jbpasquier seems like it's not supported to do some kind of filtering
I've added a new plugin into beta that forces the fetch of older messages until it meets the correct amount of messages with a body (or more)
- Author Maintainer
Sounds good at least.
Does it behaves according to plans? Does it ruin performances or is it rather transparent?
- Developer
@alexbourlier I don't feel any performance problem atm (since we are in fullscreen, it acts only on a single muc/conversation anyway
If there are performance issues, we can increase the page size too
- Author Maintainer
If there are performance issues, we can increase the page size too
I'm not sure I get what you mean. What I meant is that I fear conversations loading time will increase as we'll be loading more messages. I'm not saying it is not OK. We just need to see by how much and ensure it remains acceptable in terms of loading time. We got plagued with poor chat loading performance in the past. If we can avoid to get back to that, our users are happy
- Developer
It's because of how it's specified imo, the MAM archive retrieves messages no matter if they have a body or not
I will ask JC for feedback though
- Author Maintainer
Cool, that's the way to go I think. Keep us posted
- Please register or sign in to reply
- Emmanuel Vodor mentioned in merge request !100 (merged)
mentioned in merge request !100 (merged)
- Emmanuel Vodor mentioned in commit 001c8fea
mentioned in commit 001c8fea
- Developer
- Developer
- Author Maintainer
No, we're all having it
- Emmanuel Vodor mentioned in merge request !103 (merged)
mentioned in merge request !103 (merged)
- Jean-Baptiste Pasquier closed via merge request !103 (merged)
closed via merge request !103 (merged)
- Jean-Baptiste Pasquier mentioned in commit b2c6cfb9
mentioned in commit b2c6cfb9