Arto Jantunen

``` req_body={"com.beeper.read.extra":{"ts":1734090916841},"m.read":"$fake::oBYGilVUDg4UskeKOIY4AfDbf7BeP6buHutU1"} ``` Based on the error message on the Conduit side I'd guess the problem might be with parsing the m.read field which doesn't to my eye match the...

Wouldn't the simple solution be just ignoring the sender field in ement-room--event-mentions-user-p and/or ement-notify--event-mentions-session-user-p? It doesn't seem like matching on that would be correct in any situation.

ement-notify--event-mentions-session-user-p has a separate check for that, (unless (equal (ement-user-id user) (ement-user-id sender)). The problem is indeed that ement-room--event-mentions-user-p doesn't check for that, and acts as if the user mentioned...

Excluding the sender field from the matching wouldn't have any of the mentioned issues.

> I think we must be miscommunicating. If the message body has one of these bridged MXIDs in it, that is causing this false mention. Unless I'm just totally misunderstanding...

There are two bridged rooms where I always see this issue, one of them (the one I ran this test in) is bridged by someone else between Matrix, Discord and...

I re-did this with the other room that takes long to open. It currently has 642 members, opening the buffer took almost exactly 15 minutes and the function returned 2533...

> @viiru- Please try this branch, which limits each group of coalesced events to 100: https://github.com/alphapapa/ement.el/tree/wip/247-rendering-many-membership-events I feel like that's a reasonable starting value, but it may need to be...

Perhaps 100 is a bit low, as the buffers opened at that setting don't tend to have much context (actual messages by actual people) visible when I open them. It's...

I'm not sure if this is all that excellent but here's how I'm handling this: ``` (defun viiru/ement-connect (host) (if (ement--read-sessions) (call-interactively #'ement-connect) (let* ((found (auth-source-search :max 1 :host host...