-
Notifications
You must be signed in to change notification settings - Fork 378
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
MSC3368: Message Content Tags #3368
base: main
Are you sure you want to change the base?
Conversation
This is probably up to a decent standard now so will mark as ready for review |
The metadata object should (but does not have to) contain a `reason` key, mapping to a human-readable string value describing | ||
why the content has this tag. This is to allow users to decide if they wish to see a message on an individual basis. | ||
|
||
Other keys in the tag metadata object may be defined by future MSCs. |
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.
Does it make sense to mention that implementations may add their own extensions using the org.example.foo
syntax?
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 think that's implied anyway and I haven't seen it in any other MSCs as far as I remember. If you have an example of where that has been added to an MSC I'll be happy to add it.
Implemented in officialdakari/Extera |
Initially I suggested most of this in a comment under MSC3286 but that MSC has been inactive for over a month now and I felt like my suggested changes were big enough to warrant a separate MSC.
Rendered
Signed-off-by: 0x1a8510f2 <admin@0x1a8510f2.space>