-
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
MSC 1794 - Federation v2 Invite API #1794
Conversation
d71a60b
to
b0adfc6
Compare
looks eminently sane to me |
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.
modulo grammatical nitpicking, short and sweet. Looks great.
Co-Authored-By: erikjohnston <[email protected]>
Looks like a good proposal from my end too. Thanks for writing it up! |
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.
Just a couple nits.
Co-Authored-By: erikjohnston <[email protected]>
@mscbot fcp merge |
Team member @erikjohnston has proposed to merge this. The next step is review by the rest of the tagged teams: No concerns currently listed. Once a majority of reviewers approve (and none object), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
Co-Authored-By: erikjohnston <[email protected]>
🔔 This is now entering its final comment period, as per the review above. 🔔 |
The final comment period, with a disposition to merge, as per the review above, is now complete. |
extra data to be added to the request payload separately from the event. | ||
2. A required field called `"room_version"` is added that specifies the room | ||
version. | ||
3. The `"invite_room_state"` is moved from the `unsigned` section of the event |
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.
on retrospect, I don't know if this is a good idea. We spent a lot of time going through the spec to make sure the invite_room_state
was correctly documented to be under the unsigned object. Given this is for s2s communications though, this is probably fine.
Original proposal: #1794 Implementation proofs: * matrix-org/synapse#4402 * matrix-org/synapse#4496 There are no changes from the original proposal.
Original proposal: #1794 Implementation proofs: * matrix-org/synapse#4402 * matrix-org/synapse#4496 There are no changes from the original proposal.
Merged via #1820 🎉 |
Rendered
PRs: #1820