-
Notifications
You must be signed in to change notification settings - Fork 375
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] MSC2802: Full Room Abstraction #2802
base: old_master
Are you sure you want to change the base?
[WIP] MSC2802: Full Room Abstraction #2802
Conversation
I created a room specifically discussing this MSC, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would have to re-read this in detail. Generally, I like this MSC. I just object to PSS not being in a room.
Going forward, I can see "everything-as-a-room", with Matrix servers providing base room functionality, and implementing IM-specific functionality with appservices. Not sure if someone else agrees with that vision?
The Personal Server State refers to a `(target, type)` Key-Value data structure persisted on the | ||
server, personal to the user, which can be manipulated by the corresponding user at any time. This | ||
"state" has analogies with "room state" in the way that room state is also a Key-Value mapping. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't that PSS be a better fit for a private room?
Think "profiles-as-rooms", but with a public as well as a private room.
Private rooms could still federate (portable identities). They could contain that kind of mappings as room events. Other stuff such as key backup, etc could be part of the room state.
Rendered
Signed-off-by: Jonathan de Jong <jonathan@automatia.nl>