-
Notifications
You must be signed in to change notification settings - Fork 376
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
MSC3282: Expose enable_set_displayname in capabilities response #3282
Conversation
Co-authored-by: Alexey Rusakov <Kitsune-Ral@users.sf.net>
Co-authored-by: Alexey Rusakov <Kitsune-Ral@users.sf.net>
…-enable_set_displayname-capabilities.md
@@ -0,0 +1,25 @@ | |||
# MSC3279: Expose enable_set_displayname in capabilities response |
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.
But now this is MSC3282
…-enable_set_displayname-capabilities.md
```javascript | ||
{ | ||
"capabilities": { | ||
"m.enable_set_displayname": false, |
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.
Here, I think that can_set_displayname
is a better name from a client point of view.
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 PR is not up to date. The current PR is: #3283
Rendered