mirror of
https://github.com/matrix-org/matrix-spec
synced 2025-12-28 19:48:37 +01:00
Move "via" problem to a "potential issue"
This commit is contained in:
parent
8a61ce9032
commit
c0c51383e9
|
|
@ -184,10 +184,6 @@ encountered, and ignore the relationship rather than recursing infinitely.
|
|||
XXX: we need to deterministically specify where the cycles get cut.
|
||||
I think kegan found a solution for this when implementing MSC2946 in Dendrite.
|
||||
|
||||
XXX: we need to specify how vias are updated as time goes on (perhaps servers
|
||||
with sufficient permission could automatically add themselves into the via event
|
||||
via the bot from MSC2962?)
|
||||
|
||||
## Future extensions
|
||||
|
||||
The following sections are not blocking parts of this proposal, but are
|
||||
|
|
@ -300,6 +296,10 @@ None at present.
|
|||
link when there is a corresponding `m.room.child` event, however it remains
|
||||
a problem for "secret" rooms.
|
||||
|
||||
* The `via` servers listed in the `m.room.child` and `m.room.parent` events
|
||||
could get out of date, and will need to be updated from time to time. This
|
||||
remains an unsolved problem.
|
||||
|
||||
## Rejected alternatives
|
||||
|
||||
### Use a separate state event for type of room
|
||||
|
|
|
|||
Loading…
Reference in a new issue