matrix-org / matrix-org/matrix-spec
Should the homeserver overwrite m.room.member (per-room) profiles when a user changes their 'global' profile?
Open
Nobody has claimed this yet.
A-Client-Server
enhancement
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
Currently in synapse the m.room.member event gets overwritten regardless of what was there. Maybe the homeserver should check the m.room.member event to see if it is different from the old global profile before running over it?
See also:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading matrix-doc PRs 1302 and 1367, then review the linked discussion on matrix-doc issue 545. Determine whether the specification should require preserving per-room m.room.member profile fields when a global profile changes; done means the open question has a decided, documented protocol behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100