Refs #330. This adds the warning. The issue's other suggestion, an "Include original sender" toggle, is a product choice and stays open.
Forwarding a message from an encrypted room into an unencrypted one posts the text, and a re-uploaded plaintext attachment, where the server and everyone in that room can read it, together with the original author's ID. The dialog said nothing.
Change: when the source room is encrypted and any picked destination isn't, a note above Send says:
Zebra Lounge isn't encrypted. The forwarded message (and any attachment) will be readable by the server and everyone in that room, along with who originally wrote it.
With several unencrypted picks it reads "N of the rooms you picked aren't encrypted…". It uses the room name the user sees, including "Rename for me" names.
Verified in Chromium: sent a message in the encrypted e2ee-lab room, chose Forward, and picked Zebra Lounge, which is unencrypted. The note above appears (screenshot below). Unit tests cover the cases: no note from an unencrypted source, none with no unencrypted destination, and the one- and many-room wording.
Refs #330. This adds the warning. The issue's other suggestion, an "Include original sender" toggle, is a product choice and stays open.
Forwarding a message from an **encrypted** room into an **unencrypted** one posts the text, and a re-uploaded plaintext attachment, where the server and everyone in that room can read it, together with the original author's ID. The dialog said nothing.
**Change:** when the source room is encrypted and any picked destination isn't, a note above **Send** says:
> Zebra Lounge isn't encrypted. The forwarded message (and any attachment) will be readable by the server and everyone in that room, along with who originally wrote it.
With several unencrypted picks it reads "N of the rooms you picked aren't encrypted…". It uses the room name the user sees, including "Rename for me" names.
**Verified** in Chromium: sent a message in the encrypted e2ee-lab room, chose Forward, and picked Zebra Lounge, which is unencrypted. The note above appears (screenshot below). Unit tests cover the cases: no note from an unencrypted source, none with no unencrypted destination, and the one- and many-room wording.
`tsc` clean · unit tests pass · ESLint clean.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5
Forwarding from an encrypted room into an unencrypted one posts the text
(and a re-uploaded plaintext attachment) where the server can read it,
with the original author attached, and the dialog said nothing. Show a
note above Send naming the unencrypted destination(s).
Refs #330
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Refs #330. This adds the warning. The issue's other suggestion, an "Include original sender" toggle, is a product choice and stays open.
Forwarding a message from an encrypted room into an unencrypted one posts the text, and a re-uploaded plaintext attachment, where the server and everyone in that room can read it, together with the original author's ID. The dialog said nothing.
Change: when the source room is encrypted and any picked destination isn't, a note above Send says:
With several unencrypted picks it reads "N of the rooms you picked aren't encrypted…". It uses the room name the user sees, including "Rename for me" names.
Verified in Chromium: sent a message in the encrypted e2ee-lab room, chose Forward, and picked Zebra Lounge, which is unencrypted. The note above appears (screenshot below). Unit tests cover the cases: no note from an unencrypted source, none with no unencrypted destination, and the one- and many-room wording.
tscclean · unit tests pass · ESLint clean.🤖 Generated with Claude Code
https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5