matrix-spec-proposals
matrix-spec-proposals copied to clipboard
matrix-org
MSC3015: Room state personal overrides
Related issues:
- Personal ('pet name') room name for chats
- Ability to override the displayname for users & rooms that get served to you (SPEC-427)
Signed-off-by: Alexey Korepov [email protected]
After much thought I decided to rework this MSC to allow override not only room name, but avatar, topic and maybe other room state values too, also reworked the storage format to match the state event content.
I think it would be better (IMHO essential) to have a custom m.room.name only encrypted on the server. It might contain highly sensitive data.
This similarly applies to m.room.avatar.
Hey @MurzNN, because I did not know this MSC exists, I began writing MSC3864 and MSC3865, which kind of overlap with this MSC.
I separated overriding room attributes and user attributes, so overriding user attributes can happen on a global scope and a room scope (got the idea from a discussion). However, as I see it, yours seems more reviewed and so more ready to implement. So I'm unsure if both approaches shall be decided upon or if we could merge both. If you (or others as well) have time to discuss this, I created a public room for that: #mscs-3015-3864-3865:matrix.org
This seems to have stalled, is there a reason? I'm really surprised with the popularity of the Discord bridge that people don't have more use for this since you end up with 10 rooms all named #general.
This seems to have stalled, is there a reason? I'm really surprised with the popularity of the Discord bridge that people don't have more use for this since you end up with 10 rooms all named
#general.
From what I can tell, the next step is to edit the proposal to not use a top-level override. namespace for the data, as mentioned by @KitsuneRal at https://github.com/matrix-org/matrix-spec-proposals/pull/3015#pullrequestreview-699603731.
Until this is merged, I'm considering implementing it in my client using the unstable prefix mentioned: org.matrix.msc3015.[m.state.type].override.
FWIW, I've implemented this in Ement.el: https://github.com/alphapapa/ement.el/commit/7c12e04d769bc8696bec89730729ac12083aeee3 It seems to work nicely. Finally I can give rooms names that are meaningful to me. I hope this proposal will be merged so all clients can use it.
Is @MurzNN interested in continuing to push the PR forwards? Alternatively, is anyone else interested in picking it up? (Or forking it? I don't know the proper procedure here).
This proposal has been open for a while (seems like it's even targeting a stale branch), so would it need a lot more changes to be viable? Or has it been superseded by a newer proposal?
There were discussion chat created by @Zocker1999NET #mscs-3015-3864-3865:matrix.org
we can jump in.
I would really like it to be moved through.
