History setting implies history in encrypted, publicly joinable rooms will work

[ghost]

Steps to reproduce

1. Create a public room with E2E encryption. 2. Ensure, that you allow users to access history messages.

3. Of course, there's only two ways to add new users to that room.

• User add himself, because it's a public room (case A)
• User gets the invitation to that room (case B) 3. In the case A, user CAN'T SEE the history of conversation, but in case B, HE CAN. 4. I'd like to point out, that this misinformation not affect private encrypted rooms, only public encrypted rooms, when user joining by his own.

What happened?

User is not able to view the past messages (conversation history).

What did you expect?

User should see the past messages (conversation history) because of settings "Who can read history?" given.

Operating system

No response

Browser information

No response

URL for webapp

No response

Have you submitted a rageshake?

No

[dbkr]

Although publicly joinable, encrypted rooms are a bit of a weird case, nonetheless we should probably just make this not imply that will work, somehow.

[ghost]

Although publicly joinable, encrypted rooms are a bit of a weird case, nonetheless we should probably just make this not imply that will work, somehow.

Not so weird if we wanna set broadcast room freely joinable only from our federation - so it's important that is encrypted E2E, but at the same time freely joinable for our users. So, it has sense, if following settings are ON:

[svntp]

I think this issue is still relevant today, especially in combination with Spaces.

If an encrypted room is part of a space and has the access setting "Space member", no history is available if a space user joins directly. If he joins via invitation, the history is shown.