Sending events in encrypted rooms is broken without error #28127
Labels
A-E2EE
O-Frequent
Affects or can be seen by most users regularly or impacts most users' first experience
S-Major
Severely degrades major functionality or product features, with no satisfactory workaround
T-Defect
Comments
|
Note: I assume this is due to the same buggy assumption element X is using of having unsinged devices. Element (as in the product) seems to be forgetting that there exist developers in their customerbase which by nature of matrix will always have unverified devices since not even all clients can do that. As long as this is not possible to happen network wide, I do consider this behaviour both broken and actively hostile to their userbase. Even worse there exist devices which are unsigned due to element X... |
dosubot
bot
added
A-E2EE
O-Frequent
|
Ok turns out there is in labs a hidden "disable" button for globally disabling it... |
|
Fixed by element-hq/matrix-react-sdk#104 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce
Outcome
What did you expect?
Able to send messages.
What happened instead?
It fails with a failure and retry which also fails. No request is being sent. It works in all other non e2ee rooms.
Operating system
Fedora Silverblue 40
Browser information
Firefox 130.0.1 (64-Bit)
URL for webapp
develop.element.io
Application version
Version von Element: e428a1e-react-33c900e3070a-js-866fd6f4a3ee Krypto-Version: Rust SDK 0.7.2 (517d99b), Vodozemac 0.7.0
Homeserver
matrix.midnightthoughts.space
Will you send logs?
No
The text was updated successfully, but these errors were encountered: