MSC4057: Static Room Directory #4057
Conversation
7de8694 to
8a9968a
Compare
|
Currently it links to this, which lists the homeservers in a room and requires authentication: I think you meant to link to this for the current non-static room directory: |
| of a room to a new room version, this could discourage users of using the feature in a state in which few homeservers | ||
| support it. | ||
|
|
||
| ## Alternatives |
There was a problem hiding this comment.
https://github.com/tulir/mauliasproxy already works for room aliases with no spec changes, and I'd expect room directories could be implemented easily too (but haven't checked)
There was a problem hiding this comment.
Perhaps the naming is a little unclear here. Essentially the goal of this MSC is to allow the functionality of mauliasproxy by just hosting a static file.
From my understanding that functionality would generally be regarded as room aliases (using /_matrix/federation/v1/query/directory), whereas the endpoint that whats called (public) room directory is what clients can query via their server over federation to search for rooms (using /_matrix/federation/v1/publicRooms). I'm not sure how these interact currently, but perhaps the MSC would be better off to be named "Static Room Aliases" then?
|
|
||
| ```json | ||
| { | ||
| "#hq:example.com": "!OGEhHVWSdvArJzumhm:matrix.org", |
There was a problem hiding this comment.
Just having the room ID isn't enough. To join a room, we need to know what server(s) can be used to join (like the via parameter in matrix URIs)
Rendered