MSC4133: Extending User Profile API with Key:Value Pairs#4133
MSC4133: Extending User Profile API with Key:Value Pairs#4133turt2live merged 57 commits intomatrix-org:mainfrom
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
|
Looks great, thanks! |
|
Seems we discuss here a key-value CRDT, as keys would need to be updated over time. Personally, I'm all in favor. Matrix Event Graph is isomorphic to Merkle-CRDT that powers OrbitDB (key-value DB is one of the supported CRDT). |
|
|
Spec PR: matrix-org/matrix-spec#2071 |
| - Guest access follows the same rules as existing profile endpoints - guests may view profiles but | ||
| not modify them |
There was a problem hiding this comment.
This isn't fully correct -- guests can set only their display name. I'm assuming this implies that they can still modify their display name (Which for this MSC implies set & now delete), while other fields cannot be modified.
There was a problem hiding this comment.
Agreed, the intention was "We don't change what guests are allowed to do/access" 🙂
Rendered
Signed-off-by: Tom Foster tom@tcpip.uk
Known Implementations:
FCP tickyboxes
MSC checklist
Note that this proposal was lightly edited by #4327 after FCP.