MSC4133: Extending User Profile API with Key:Value Pairs

[tcpipuk]

Rendered

Signed-off-by: Tom Foster tom@tcpip.uk

---

Known Implementations:

• Clients:
  • Complete: Add timezone to user profile element-hq/matrix-react-sdk#20
  • Complete: Add timezones and pronouns gomuks/gomuks#574
• Servers:
  • Complete: Implement MSC4133 to support custom profile fields. element-hq/synapse#17488
  • Complete: girlbossceo/conduwuit#571
• SDKs:
  • Complete: MSC4133 - Extended profiles matrix-js-sdk#4391
  • Complete: Implement arbitrary fields for RespUserProfile mautrix/go#337

---

FCP tickyboxes

MSC checklist

[turt2live]

@tcpipuk when you get a chance, please sign off on your changes to allow the MSC to eventually be eligible for acceptance.

[turt2live]

Looks great, thanks!

[andrewzhurov]

Seems we discuss here a key-value CRDT, as keys would need to be updated over time. Personally, I'm all in favor.
With no regard be those events a part of a (messaging) Room or be in its own Profile Room (#1769) (which would be neat),
we need a mechanism to get the latest key-value pairs.

Matrix Event Graph is isomorphic to Merkle-CRDT that powers OrbitDB (key-value DB is one of the supported CRDT).
Taking an inspiration from how key-value CRDT works may be of help to spec it for those Servers wishing to opt-in.

[richvdh]

The final comment period, with a disposition to merge, as per the review above, is now complete.

No it isn't

[turt2live]

I'm not sure how the bot will respond to this, but the SCT is resolving the outstanding concern on addressing the recent feedback. Under normal process, this would cause FCP to finish immediately, however it feels valuable for this MSC to have an opportunity for final thoughts to be raised.

FCP will resume until 15:00 UTC on Friday, January 31st, 2025.

@mscbot resolve Feedback during FCP needs consideration.

[turt2live]

The final comment period, with a disposition to merge, as per the review above, is now complete.

No it isn't

Now it is

[tulir]

Spec PR: matrix-org/matrix-spec#2071

[clokep]

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.

[tcpipuk]

Agreed, the intention was "We don't change what guests are allowed to do/access" 🙂