Skip to content

MSC4529: Client-side profile overrides - #4529

Open
nvnvnvnvnvnvnv wants to merge 1 commit into
matrix-org:mainfrom
nvnvnvnvnvnvnv:profile-overrides
Open

MSC4529: Client-side profile overrides#4529
nvnvnvnvnvnvnv wants to merge 1 commit into
matrix-org:mainfrom
nvnvnvnvnvnvnv:profile-overrides

Conversation

@nvnvnvnvnvnvnv

Copy link
Copy Markdown

Signed-off-by: nv <nvnvnvnvnvnvnvnv@protonmail.com>
so the event grows with the number of users overridden rather than without limit. In practice the
feature is used for a handful of users at a few dozen bytes each.

An override is a snapshot and does not track later changes to the real profile. That is largely the

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Considering for names, pfps and per-room colors, a user would likely see them still as most clients show m.room.member changes by default so this would likely be less of a potential issue than this would anticipate

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, they would be shown in timeline, but would be less obvious to you I suppose. I don't see it as a meaningful problem either.

@turt2live turt2live added proposal A matrix spec change proposal. Process state. A-Client Server Client-Server API kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. labels Aug 16, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Implementation requirements:

  • Client (setting)
  • Client (showing)

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, I need implementation in a client before this proposal has the possibility of being merged?

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nvnvnvnvnvnvnv yes:

This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-Client Server Client-Server API kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal. Process state.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants