You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Currently if a room has no explicit name (e.g. Matrix HQ) it's up to the client to synthesise one by looking at the membership list, etc. This is not ideal, because:
It means we have to xfer the whole membership list just to display the Recents index
It means clients have to get the logic right, and be consistent across multiple different implementations (which currently we fail abjectly at).
So let's do it serverside instead. We can even internationalise it if needed
matrixbot
changed the title
We should generate sensible default names for rooms serverside rather than relying on clients to get it right. (SYN-265)
We should generate sensible default names for rooms serverside rather than relying on clients to get it right. (https://github.com/matrix-org/synapse/issues/1283)
Nov 7, 2016
matrixbot
changed the title
We should generate sensible default names for rooms serverside rather than relying on clients to get it right. (https://github.com/matrix-org/synapse/issues/1283)
We should generate sensible default names for rooms serverside rather than relying on clients to get it right. (SYN-265)
Nov 7, 2016
matrix-org/matrix-spec-proposals#688 was the spec issue tracking this, and it got resolved via the room summary. It's surprisingly hard to do better than that, and if we ever wanted to, it would be primarily a spec issue, so I'm going to consider this resolved.
Currently if a room has no explicit name (e.g. Matrix HQ) it's up to the client to synthesise one by looking at the membership list, etc. This is not ideal, because:
So let's do it serverside instead. We can even internationalise it if needed
(Imported from https://matrix.org/jira/browse/SYN-265)
(Reported by @ara4n)
The text was updated successfully, but these errors were encountered: