Inform in-band that encrypted chats are not supported #80

Open
opened 2026-03-07 10:01:32 +00:00 by cadence · 0 comments
Owner

Solution A:

  • Refuse to join invited-to rooms if encrypted. (Encryption status is apparently available as is_encrypted in SSS API, m.room.encryption in stripped state, and encryption in hierarchy API. This theoretically covers all supported homeserver implementations.)
  • AND, refuse to link with existing Matrix rooms in space if encrypted. (Apparently available as encryption in hierarchy API.)

Solution B:

  • In a chat, the first time an encrypted message is sent, inform that encrypted messages are not supported
    • Possibly offer to upgrade the room to an unencrypted one?

Implement either or both.

Solution A: - Refuse to join invited-to rooms if encrypted. (Encryption status is apparently available as `is_encrypted` in SSS API, `m.room.encryption` in stripped state, and `encryption` in hierarchy API. This theoretically covers all supported homeserver implementations.) - AND, refuse to link with existing Matrix rooms in space if encrypted. (Apparently available as `encryption` in hierarchy API.) Solution B: - In a chat, the first time an encrypted message is sent, inform that encrypted messages are not supported - Possibly offer to upgrade the room to an unencrypted one? Implement either or both.
cadence added the
moderately approachable
label 2026-03-07 10:01:32 +00:00
cadence added this to the v3.x milestone 2026-03-07 10:13:11 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: cadence/out-of-your-element#80
No description provided.