Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Undefined behaviour for room directory entries when a HS is no longer present in a room #768

Open
joepie91 opened this issue Feb 10, 2021 · 0 comments
Labels
clarification An area where the expected behaviour is understood, but the spec could do with being more explicit

Comments

@joepie91
Copy link

It seems that none of the specs currently define the correct behaviour in handling room metadata (name, topic, ...) for the following situation:

  1. User A on example.com homeserver adds room to example.com's public room directory
  2. User A leaves room, and no example.com users remain, meaning the HS ceases to receive or process room updates
  3. User B on example.com views public room directory entry for the room in question

Empirically, Dendrite apparently responds to this by retaining the metadata at the moment the user left, and not reflecting any further updates to it, but still showing the stale room metadata in the directory.

Ideally, a homeserver should continue maintaining the room metadata even after the user has left, at least until the room is removed from the directory explicitly (possibly peeking-over-federation is relevant here?). Failing that, the intended behaviour should at least be specified explicitly.

@richvdh richvdh transferred this issue from matrix-org/matrix-spec-proposals Mar 1, 2022
@turt2live turt2live added the clarification An area where the expected behaviour is understood, but the spec could do with being more explicit label May 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
Projects
None yet
Development

No branches or pull requests

2 participants