OpenCloud
/
MatrixSynapse
mirror of https://github.com/matrix-org/synapse
1
0
Fork 0
Code Issues Releases Wiki Activity

Merge pull request #7 from matrix-org/paul/doc 

Clarify that room alias domain names will be server-scoped; nonlocal edi...
pull/9/head
Erik Johnston 2014-10-07 16:35:32 +01:00
parent 9ac53ef8cf 917af4705b
commit 5b096cc3db
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/specification.rst
View File

@ -805,6 +805,11 @@ no content. Only some privileged users may be able to delete room aliases, e.g.
server admins, the creator of the room alias, etc. This specification does not server admins, the creator of the room alias, etc. This specification does not
outline the privilege level required for deleting room aliases. outline the privilege level required for deleting room aliases.
As room aliases are scoped to a particular home server domain name, it is
likely that a home server will reject attempts to maintain aliases on other
domain names. This specification does not provide a way for home servers to
send update requests to other servers.
Rooms store a *partial* list of room aliases via the ``m.room.aliases`` state Rooms store a *partial* list of room aliases via the ``m.room.aliases`` state
event. This alias list is partial because it cannot guarantee that the alias event. This alias list is partial because it cannot guarantee that the alias
list is in any way accurate or up-to-date, as room aliases can point to list is in any way accurate or up-to-date, as room aliases can point to
@ -823,6 +828,9 @@ Room aliases can be checked in the same way they are resolved; by sending a
"servers": [ <domain>, <domain2>, <domain3> ] "servers": [ <domain>, <domain2>, <domain3> ]
} }
Home servers can respond to resolve requests for aliases on other domains than
their own by using the federation API to ask other domain name home servers.
Permissions Permissions
----------- -----------