Skip to content

MSC4461: Storing per-message profiles for users - #4461

Open
tulir wants to merge 12 commits into
mainfrom
tulir/per-message-profile-storage
Open

MSC4461: Storing per-message profiles for users#4461
tulir wants to merge 12 commits into
mainfrom
tulir/per-message-profile-storage

Conversation

@tulir

@tulir tulir commented May 5, 2026

Copy link
Copy Markdown
Member

Signed-off-by: Tulir Asokan <tulir@maunium.net>
@tulir tulir 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 May 5, 2026

@tulir tulir May 6, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Implementation requirements:

  • Client that can create reusable profiles
  • Client that can use reusable profiles when sending messages

@tulir tulir May 9, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

gomuks/gomuks@2e5489a (+ gomuks/gomuks@4daa127 and gomuks/gomuks@fbe6fdb) is an implementation of sending profiles, no UI for creating yet

gomuks/gomuks@951bac5 updates the implementation to the v2 format added in 61aec70

gomuks/gomuks@c416f43 updates it to v3

Comment thread proposals/4461-per-message-profile-storage.md Outdated
charm-cloudhub-social Bot pushed a commit to CloudHub-Social/Charm-1.0 that referenced this pull request Aug 3, 2026
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->

### Description

<!-- Please include a summary of the change. Please also include
relevant motivation and context. List any dependencies that are required
for this change. -->

Migrates PMP account data to the format described in
[MSC4461](matrix-org/matrix-spec-proposals#4461).
Extensions to the format are defined in my informal
[MSCF002](https://github.com/j0lol/matrix-spec-proposals/blob/mscf/proposals/F0002-PK-proxy-tags.md).
(Though ambiguity behavior defined in this spec have not been
implemented just yet.)

Part of SableClient#1279

#### Type of change
breaking change on an experimental feature, with migrations

- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update

### Checklist:

- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings

### AI disclosure:

- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
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