MSC3919: Matrix Message Format (IETF/MIMI) #3919
Open
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
turt2live
changed the title
turt2live
added
proposal
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 (latest IETF draft)
This MSC is slightly different to other proposals in the Matrix spec process. Instead of proposing changes to Matrix, it is proposing adoption of Matrix at the IETF level. Comments raised against this MSC will be taken into consideration in two places: under the MIMI working group and within the Matrix spec process where appropriate.
This MSC serves to show what the Spec Core Team/Matrix.org Foundation is thinking about with respect to modern messenger interoperability in the context of IETF.