7432d254c6
incorporate travis feedback
4 years ago
0d71150424
remove confusing mention of peeking & dependent MSCs
4 years ago
1e2ed52b7e
add more justification for immutable room types
4 years ago
37e04f72ae
tiebreak ordered spaces sensibly
4 years ago
f07e82e34b
clarify the charsets of our lexicographic orderings
4 years ago
00912f9c1e
clarify how to deterministically cut cycles
4 years ago
cb7bbf3787
I don't think this is a concern
4 years ago
2c817cb1c5
Add another advantage
4 years ago
c9b7e9f22d
Reword need for token
4 years ago
7a3b7b38a5
Add implementations section
4 years ago
12d08ca83d
Consistency and update links.
4 years ago
6d007e83ca
Defer a TODO to the future.
4 years ago
609641636d
decouple from MSC1849/MSC2674
4 years ago
8935503470
Fix a left-over spotted in the last moment
4 years ago
d27ea07bcb
Minor brush-ups and cleanup
4 years ago
67635b0dd7
Be even clearer about user confirmations
4 years ago
037ebbf1ca
Be even clearer about the authority part
4 years ago
9dd0854aee
Add a link to CS API
4 years ago
e7041525bf
Include `create` in invite_room_state
4 years ago
a8f4ada8a8
Make join_rules field of PublicRoomChunk an optional value
4 years ago
9ebfd98a7a
Apply suggestions from code review
...
Co-authored-by: Alexey Rusakov <Kitsune-Ral@users.sf.net>
4 years ago
10267df76e
Add missing 403/404 response codes
4 years ago
11996fb436
clarify some words
4 years ago
0841f31ce4
Apply suggestions from code review
...
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
4 years ago
a1a40c6346
Be consistent about event auth rules
4 years ago
7f0b2d66a0
Update unstable endpoints from i.e xyz.amorgan/knock -> xyz.amorgan.knock
...
I'm doing this for two reasons:
1) If I ever wanted to create another knock-related MSC, it would be nice to be able
to give it a different namespace for endpoints, such as xyz.amorgan.knock2/knock. If
we were only using xyz.amorgan as the namespace for endpoints, that restricts that
namespace to only work for one MSC which attempts to use /knock as part of an endpoint.
2) I accidentally made the implementation use xyz.amorgan.knock/knock :)
4 years ago
52dfaaabd4
Update proposals/2801-untrusted-event-data.md
...
Co-authored-by: Jonathan de Jong <jonathandejong02@gmail.com>
4 years ago
065b0990e6
Update proposals/1772-groups-as-rooms.md
4 years ago
5e7ed2b9c4
Tweak wording about lexicographic ordering
4 years ago
9ca94235c6
Suggested rooms
4 years ago
c0c51383e9
Move "via" problem to a "potential issue"
4 years ago
8a61ce9032
remove 'present' flag
4 years ago
6c9d469d56
add an issue about lost parent links
4 years ago
0bdbec238b
Accept m.space.parent links if there is a reverse link
4 years ago
2e6d7d1c54
spaces are *primarily* referred to by their room ID.
4 years ago
acdb6f1c3d
Move "auto-join" out to "future extensions"
...
we're not doing this bit yet.
4 years ago
7d757ce8fa
minor wording tweaks
4 years ago
dcb18f03dc
Move security consideration to MSC2962
...
I think the peeking thing is specific to access control.
4 years ago
469b64c5cd
rip out m.room.description
...
if/when we need it, we should follow MSC2875
4 years ago
62b9154fa7
Remove lost footnotes
...
These should have been part of MSC2962.
4 years ago
bc1466206d
related MSCs
4 years ago
1cfe6bc0ae
MSC1840 is out again.
4 years ago
a8a7acce1e
update UIA
4 years ago
49f7624d55
update brand descriptions
4 years ago
d5166ebc1a
Update proposals/2858-Multiple-SSO-Identity-Providers.md
4 years ago
68d2d7cfdb
Note that homeservers should pass down invites to the client if they fail on autojoin
4 years ago
7871da7565
Update proposals/2858-Multiple-SSO-Identity-Providers.md
...
Co-authored-by: Hubert Chathi <hubert@uhoreg.ca>
4 years ago
1ba0c39b14
Change the brand identifiers again
4 years ago
178cbe1c3a
Update proposals/2858-Multiple-SSO-Identity-Providers.md
...
Co-authored-by: Travis Ralston <travpc@gmail.com>
4 years ago
8bfef19a39
Remove further traces of old /rooms/roomId/knock CS endpoint
4 years ago
Matthew Hodgson