MSC4133: Extending User Profile API with Key:Value Pairs

[tcpipuk]

Rendered

Signed-off-by: Tom Foster [email protected]

[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!

[tcpipuk]

Thanks to feedback from Travis in #matrix-spec:matrix.org, I've clarified my intention that this MSC is freetext for both keys and values - I'd love for the community to be inspired and have certain fields "promoted" to full per-room member events, but this is intended to keep timelines clean while allowing users to communicate small pieces of information about themselves in their profile that may be interesting to other users.

[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.

[clokep]

See also #3754.

[tcpipuk]

That seems mainly for the existing avatar and name fields - are you suggesting I should be integrating it into this to make the existing MSC redundant?

[clokep]

I had just forgotten it existed, so figured it should be referenced somewhere. There's a few options:

• Consider it a partial alternative.
• Add a dependency.
• Remove the deletes and let the other MSC handle it.

I'd suggest not the second option as decoupling is preferred where possible.