[WIP] MSC3348: Server-Server Room based extensible communication #3348
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…o XXXX Server-Server Room based extensible communication.md
FSG-Cat
changed the title
…ion.md to 3348 Server-Server Room based extensible communication.md
uhoreg
reviewed
Aug 18, 2021
proposals/3348 Server-Server Room based extensible communication.md
Outdated
Show resolved
Hide resolved
proposals/3348 Server-Server Room based extensible communication.md
Outdated
Show resolved
Hide resolved
proposals/3348 Server-Server Room based extensible communication.md
Outdated
Show resolved
Hide resolved
proposals/3348 Server-Server Room based extensible communication.md
Outdated
Show resolved
Hide resolved
proposals/3348 Server-Server Room based extensible communication.md
Outdated
Show resolved
Hide resolved
uhoreg
added
kind:feature
|
@FSG-Cat we'll also need sign-off on this before it's eligible for FCP. The easiest way to do this is to leave a comment or add to the PR description the following: |
…on.md Co-authored-by: Hubert Chathi <hubert@uhoreg.ca>
…on.md Co-authored-by: Hubert Chathi <hubert@uhoreg.ca>
…on.md Co-authored-by: Hubert Chathi <hubert@uhoreg.ca>
…on.md Co-authored-by: Hubert Chathi <hubert@uhoreg.ca>
…on.md Co-authored-by: Hubert Chathi <hubert@uhoreg.ca>
Removed a non needed Ack step since the Ack is in response to the accept and that accept can be treated as an ack. This brings the Round Trips needed down to 3.
With the negotiation mechanism rework sus2s upgrades only needs 2 events being sent before the Upgrade process can start with the third event being able to be sent at the same time as the upgrade process is initated.
kevincox
reviewed
Aug 28, 2021
|
|
||
| ### The identifiers that servers should use to identify the server users | ||
|
|
||
| The IDs the homeservers should use is currently recommended to be a simple @:identifier |
There was a problem hiding this comment.
This syntax is not clear. Does it mean a literal @: followed by an identifier or a literal @ followed by an identifier?
I see there are references later that seem to imply that it is the former but maybe an example right next to this would be helpful.
There was a problem hiding this comment.
The complete mxid under this proposal for the homeserver would be @:example.com in the case of example.com.
turt2live
added
the
needs-implementation
|
Closing this since it wont progress under Cat. |
turt2live
added
the
abandoned
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rendered
Room for the discussion of this MSC exists at #CatMSC3348:feline.support
Signed-off-by: Catalan Lover catalanlover@protonmail.com