element-hq / element-hq/element-web

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

Open
#18,615 3 comments 1 reaction 0 assignees View on GitHub
A-Room-Settings O-Uncommon S-Minor T-Defect
Dominant language
TypeScript
Stars
13.5k
Forks
2.8k
PR merge metrics
PR metrics pending

Description

### Steps to reproduce

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

![settings](https://user-images.githubusercontent.com/87245511/129882510-3e13f6aa-7341-4fed-ad2c-223cc6919bb7.png)

**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

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.