MSC4401: Publishing client capabilities via profiles#4401
MSC4401: Publishing client capabilities via profiles#4401Johennes wants to merge 5 commits intomatrix-org:mainfrom
Conversation
Signed-off-by: Johannes Marbach <[email protected]>
Johennes
force-pushed
the
johannes/profile-capabilities
branch
from
f0bd9e9 to
dfb76d7
Compare
Johennes
changed the title
turt2live
added
proposal
There was a problem hiding this comment.
Implementation requirements:
- Client
- Server
Signed-off-by: Johannes Marbach <[email protected]>
Signed-off-by: Johannes Marbach <[email protected]>
Signed-off-by: Johannes Marbach <[email protected]>
Signed-off-by: Johannes Marbach <[email protected]>
| @@ -0,0 +1,96 @@ | |||
| # MSC4401: Publishing client capabilities via profiles | |||
There was a problem hiding this comment.
I like the concept of client capabilities and wish we had it for MSC4428 / MSC4430 so clients could advertise "I support room versions 1-12" such that servers could filter out unsupported rooms in /sync.
I'm not convinced using profiles is the right place for this data though. I see your use case with needing other clients to have visibility on the capabilities, but profiles are per-user data structures (so you've got book-keeping in this MSC to namespace by device ID, which feels inelegant).
There was a problem hiding this comment.
Yes, proper per-device profiles would be better, agreed. It's the same problem with device-specific features that build on account data such as #3890.
5 participants
Rendered