MSC4461: Storing per-message profiles for users#4461
Conversation
Signed-off-by: Tulir Asokan <tulir@maunium.net>
tulir
added
proposal
There was a problem hiding this comment.
Implementation requirements:
- Client that can create reusable profiles
- Client that can use reusable profiles when sending messages
There was a problem hiding this comment.
gomuks/gomuks@2e5489a (+ gomuks/gomuks@4daa127 and gomuks/gomuks@fbe6fdb) is an implementation of sending profiles, no UI for creating yet
| something like `m.direct`, which clients may update in the background). | ||
|
|
||
| ## Alternatives | ||
| There are various other places where profiles could be stored, like |
There was a problem hiding this comment.
I think in room profiles (probably as state events) might be a better idea, as these could then also be shown in the user list. That would make MSC4144/non-appservice bridges nicer to use.
There was a problem hiding this comment.
That wouldn't help normal users at all since users can't send state events in most rooms. It'd also mean profiles have to be added to every room instead of just once in global account data. Definitely not an option for this MSC, but I guess I should go into more detail in the alternatives section
3 participants
Rendered