-
Notifications
You must be signed in to change notification settings - Fork 380
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
MSC2557: Proposal to clarify spoilers #2557
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.
Looks like reasonable clarifications.
Co-authored-by: Hubert Chathi <hubert@uhoreg.ca>
The recommended fallback format is unchanged. | ||
|
||
Additionally, this proposal opens up spoilers to any HTML-supporting message types. Currently | ||
this includes `m.text` (already included by MSC2010), `m.notice`, and `m.emote`. |
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.
With #2241 that would also include m.key.verification.request
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.
No? It doesn't require HTML.
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.
Ah, it does it's just buried in the MSC. That's probably fine still - "don't be silly" clauses start to take effect in the spec.
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.
It doesn't require it, but it is optional. Although, as you said "HTML-supporting message types" that would be covered, too
I'm not super convinced this needs an implementation proof given the limited complexity and obvious benefits it provides. @mscbot fcp merge |
Team member @turt2live has proposed to merge this. The next step is review by the rest of the tagged people: Once at least 75% of reviewers approve (and there are no outstanding concerns), 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 information about what commands tagged team members can give me. |
🔔 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. |
Merged 🎉 |
MSC2557: Proposal to clarify spoilers
MSC2557: Proposal to clarify spoilers
Original MSC: #2010
Per the proposal process, MSC2010 has been modified to match this MSC.
Rendered