-
Notifications
You must be signed in to change notification settings - Fork 384
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MSC4233: Remembering which server a user knocked through #4233
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Implementation requirements:
- Client(?)
- Server
{"type": "m.room.name", "state_key": "", "content": {"name": "My Room"}} | ||
] | ||
}, | ||
"knock_servers": [ // new property |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i wonder if via
might be clearer?
Servers may not have already tracked this, so information will be lacking for already-knocked rooms. | ||
Clients should expect errors, per usual, when attempting to call the summary API or any other endpoint. | ||
|
||
## Alternatives |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
presumably another option would be for the server to silently remember the knock server on behalf of the client and add an implicit via when they provide a raw room id?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This MSC also applies to rescinding knocks: servers don't know what server to make/send_leave
through remotely.
Rendered
I am Director of Standards Development at The Matrix.org Foundation C.I.C., Matrix Spec Core Team (SCT) member, employed by Element, and operate the t2bot.io service. This proposal is written and published with my role as a member of the SCT.