archive
/
matrix-spec-proposals
mirror of https://github.com/matrix-org/matrix-spec-proposals
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix typo.

Browse Source 
Co-authored-by: Matthew Hodgson <matthew@matrix.org>
pull/3083/head
Patrick Cloke 4 years ago committed by GitHub
parent 30372321b3
commit 2c65a03d59
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File

2
proposals/3083-restricted-rooms.md
Unescape Escape View File

@ -128,7 +128,7 @@ as the `restricted` join rule value do not need unstable prefixes.
It may seem that just having the `allow` key with `public` join rules is enough It may seem that just having the `allow` key with `public` join rules is enough
(as originally suggested in [MSC2962](https://github.com/matrix-org/matrix-doc/pull/2962)), (as originally suggested in [MSC2962](https://github.com/matrix-org/matrix-doc/pull/2962)),
but there are concerns that changing the behaviour of a pre-existing a `public` but there are concerns that changing the behaviour of a pre-existing `public`
join rule may cause security issues in older implementations (that do not yet join rule may cause security issues in older implementations (that do not yet
understand the new behaviour). This could be solved by introducing a new room understand the new behaviour). This could be solved by introducing a new room
version, thus it seems clearer to introduce a new join rule -- `restricted`. version, thus it seems clearer to introduce a new join rule -- `restricted`.

Write Preview
Loading…
Cancel
Save