element-hq
Element puts rooms into archived section
Steps to reproduce
On a Conduit Matrix server:
- Join a room
- Let someone else send messages so none of your events are in the recent timeline anymore
- Clear cache
Outcome
What did you expect?
The room displays normally
What happened instead?
Room is in archived section
My theory is that Element expects the user's own member event to be in the initial sync, but Conduit omits it due to lazy loading.
Operating system
Browser information
URL for webapp
app.element.io
Application version
No response
Homeserver
Conduit
Will you send logs?
No
Z-Spec-Compliance because this involves determining how lazy loading works and potentially advising on what can be done about it.
Has there been any progress on this? It is causing a lot of confusion to Conduit users who think they have been kicked
Not currently - there's not really anyone on the team with enough bandwidth to debug lazy loading at the moment. If you're able to clarify things from the spec side then we might be able to take a closer look.
Similar to https://github.com/vector-im/element-web/issues/21034, I believe enabling redundant members would fix this. EDIT: No this would not fix it. Element should just query the member event itself or not rely on it at all. Or there needs to be an MSC
I've added a workaround for this to Conduit which just always sends the user's own member event on initial sync.