Currently, when a new room is created with EX, and the Private room option is selected, then:
E2EE encryption of the room is turned on.
History visibility (m.room.history_visibility) is set to shared (meaning that members who join are supposed to see messages that were sent before they were invited).
In practice, this combination is not supported yet - meaning that the messages before a user was invited are visible, but can not be decrypted. Thus, for sake of clarity, it is desired that when E2EE encryption is turned on, the history visibility defaults to invited instead of shared.
As a user creating a new E2EE room,
I want the history visibility of such room to be defaulted to invited
So that the members who join the room would not be confused why they can't read the content of the past messages.
Acceptance criteria
When a new room with E2EE is created, its history visibility defaults to invited.
Description
Background
Currently, when a new room is created with EX, and the Private room option is selected, then:
m.room.history_visibility
) is set toshared
(meaning that members who join are supposed to see messages that were sent before they were invited).In practice, this combination is not supported yet - meaning that the messages before a user was invited are visible, but can not be decrypted. Thus, for sake of clarity, it is desired that when E2EE encryption is turned on, the history visibility defaults to
invited
instead ofshared
.As a user creating a new E2EE room, I want the history visibility of such room to be defaulted to
invited
So that the members who join the room would not be confused why they can't read the content of the past messages.Acceptance criteria
invited
.Leads
Size estimate
None
Dependencies
Out of scope
Open questions
Subtasks
Sign-off
Android
iOS