MSC4208: Adding User-Defined Custom Fields to User Global Profiles #4208
Conversation
tcpipuk
changed the title
|
This needs a little work done to it. I've exported the custom field requirements from MSC4133 and am updating this to reflect that it is a new/separate MSC. |
turt2live
added
proposal
| @@ -0,0 +1,227 @@ | |||
| # MSC4208: Adding User-Defined Custom Fields to User Global Profiles | |||
There was a problem hiding this comment.
For reference, conduwuit still has the initial implementation of custom fields that was initially in MSC4133. Will review and validate to this new MSC some time in the next few days.
| ### Client-Server API Changes | ||
|
|
There was a problem hiding this comment.
There don't seem to be any actual client-server API changes in this MSC, so this entire section should probably just be deleted? The only real change is defining the u. namespace, the endpoints defined by MSC4133 work without any changes.
|
|
||
| A new capability `m.custom_profile_fields` is introduced to control the ability to set custom | ||
| profile fields. It is advertised on the `GET /_matrix/client/v3/capabilities` endpoint. Clients | ||
| should check for this capability before attempting to create or modify custom fields. |
There was a problem hiding this comment.
I'm not sure if this really needs a whole new capability. If m.profile_fields can use globs, it could just have u.* in the disallowed list to block user-defined fields
Rendered
Signed-off-by: Tom Foster [email protected]
Known Implementations: