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
MSC2874: Single SSSS #2874
MSC2874: Single SSSS #2874
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.
seems generally sensible to me
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
Implementation:
|
@mscbot fcp merge |
Team member @uhoreg 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. |
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.
This seems sensible to me, though I can't really picture the client asking the user which key to use to unlock their SSSS, unless we were storing something other than messages in there. Maybe that's the point. It's nice that that is left as an option for implementations if they choose to though.
Generally it all seems sensible and backwards compatible.
🔔 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. |
We need a codename for this, because people will think we are randomly hissing :) |
Merged! 🎉 |
Rendered