c915b6442b
Update alternatives section
4 years ago
09018be96c
Link to existing spec documentation on the public rooms directory
4 years ago
53ad7e3f66
Ensure we return the room_id after knocking via the CS API
4 years ago
c575f88d13
Move endpoint extras under endpoint's header
4 years ago
c9f34e818e
Link to /join/roomIdOrAlias
4 years ago
49a72862a9
Allow knock->knock transitions
4 years ago
e790ad2120
Apply suggestions from code review
...
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
4 years ago
24f61c283c
Note that implementations may choose to auto-accept knock-related invites
4 years ago
eda65847a3
Comment on push rules
4 years ago
248a3da5ca
Switch /send_knock/ from v2 to v1; leave a note as to why
4 years ago
74f3b12a17
Note experimental room version ID
4 years ago
04cd6b3d3e
fix typo
...
Co-authored-by: Hubert Chathi <hubert@uhoreg.ca>
4 years ago
337c87b949
Add 404 on make_knock if unknown room ID
4 years ago
8400877574
Make ver a required parameter for make_knock
4 years ago
d5a2a284c5
Note clients should try to prevent impersonation attacks during knocking
4 years ago
5c620de273
typo fix
4 years ago
6a0d07c799
Public rooms directory backwards compatibility note
4 years ago
51a7778217
typo
4 years ago
e99649cb84
Foreshadow power level requirements for approval/denial of knock
4 years ago
42e01b8e91
Add join_rules to room chunks returned on a public room dir query
4 years ago
7dcff8f2e1
Disallow invite->knock membership changes
4 years ago
6c75b83b99
Address Travis and Patrick's feedback
4 years ago
815dae6eae
Note that redactions of knocks are not a concern
4 years ago
a924f5b3d5
Fix incorrect assumptions about the sender field of a knock event
...
Got a bit confused with the sender and state_key being different in invite
membership events. In case of a knock, even if the knock event is being
inserted into the room by another homeserver over federation, the sender
of the event is still the knocking user, just like the state_key.
4 years ago
525d1d33e0
Some clarifications and wording fixes
4 years ago
6f7bcb6052
Explicitly state what changes to the auth rules are necessary
4 years ago
5097fad4e7
Fix unstable prefix bullet points
4 years ago
6b99228386
Remove section duplicated by membership change section
4 years ago
fd8176b93d
Clarify endpoint calls clients and servers need to use to handle knocks
4 years ago
9e5ac042ac
Explicitly state that the hs that received the knock must put in the room
4 years ago
e58e207bbf
Go into more depth about membership changes surrounding knocking
4 years ago
340f888de3
Mention unstable prefixes for sync, join_rules and membership events
4 years ago
6e47e86f01
Add unstable endpoint replacements
4 years ago
fd9d57b8c4
Match state events sent to a remote server when inviting a user
4 years ago
630f7c458c
Allow users to knock over and over, removing CS complexity
4 years ago
61fea58ce0
Merge branch 'soru/knock' of github.com:sorunome/matrix-doc into soru/knock
4 years ago
703fa07028
Remove extraneous text
4 years ago
58cb299dde
Update proposals/2403-knock.md
...
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
4 years ago
c9a7b442ff
Merge branch 'soru/knock' of github.com:sorunome/matrix-doc into soru/knock
...
* 'soru/knock' of github.com:sorunome/matrix-doc:
Federation knock_room_state and minor cleanup
4 years ago
e93a19f62d
Indicate that this proposal requires a new room version
4 years ago
5bfd65c59f
Federation knock_room_state and minor cleanup
4 years ago
ae8ec6603c
Spec how a client is notified of pending knock progress
4 years ago
965c47ba08
Remove unnecessary sentence
4 years ago
651e73b2db
It's possible to fight against spam
4 years ago
f3fc5399fc
Move client recommendations into its own section
...
Hopefully leading to less duplication in recommendations as well
4 years ago
aad6ff4a05
Remove remaining traces of [200, {}] response format
4 years ago
bc90f1ce47
Fix typo
4 years ago
105108428f
Switch from Power Levels -> Join Rules
4 years ago
d6d5858b67
knock->knock and rescinding of knocks are not allowed
4 years ago
716db4e656
Spell out some possible abuse vectors and how to mitigate them
4 years ago
Andrew Morgan