Gateway's own messages turn red as "Not encrypted" after unlinking Telegram #60

New issue

Closed

opened 2026-10-27 02:55:11 +00:00 by bmt · 1 comment

bmt commented

2026-10-27 02:55:11 +00:00

Member

After unlinking Telegram, all messages in the chat with the Telegram gateway are shown as red bubbles marked "Not encrypted".
After linking again they look normal.

steps:

Unlink Telegram
Open the chat with the Telegram gateway

expected: the gateway's messages look normal, without a red warning

actual: they are red and marked "Not encrypted"

(not sure if this is a bug by design)

After unlinking Telegram, all messages in the chat with the Telegram gateway are shown as red bubbles marked "Not encrypted". After linking again they look normal. steps: 1. Unlink Telegram 2. Open the chat with the Telegram gateway expected: the gateway's messages look normal, without a red warning actual: they are red and marked "Not encrypted" (not sure if this is a bug by design)

bug29-2026-10-27-shlyuz-krasnye.png

108 KiB

bug29-2026-10-27-posle-privyazki-obychnye.png

134 KiB

bmt added the

needsinfo

ui/ux

telegram_gw

labels

2026-10-27 02:55:11 +00:00

ann referenced this issue from a commit

2026-10-27 08:56:51 +00:00

The chat with a gateway itself reads as no end-to-end chat, linked or not (#60, bmt: "After unlinking Telegram, all messages in the chat with the Telegram gateway are shown as red bubbles marked "Not encrypted". After linking again they look normal."): state/gateway-chat.ts knew a person behind a gateway by their domain but took the gateway's own bare JID (telegram.another.im) for a server, so that chat went by libtacky's OMEMO default, which with no OMEMO list from the gateway on record is on, and every line of the gateway in the clear was drawn red as "Not encrypted" (exposed). GatewayChats gains gatewayItself (a bare domain JID other than our server's that is a gateway, by the server's listing or its own disco info identity, category gateway, asked once, never by the registration, which is gone once unlinked), encryptionGateway (either) and wantEncryption; OmemoChats reads such a chat as THROUGH_GATEWAY, switches libtacky off for it once and never on, and the chat header's padlock and menu, the closable card, the contact page's tile and the Encryption information window say "No end-to-end encryption" there as for a gateway's users. gatewayFor is unchanged, so what else reads "behind a gateway" (names, last seen, bot commands, forwarding, notices) does not take the gateway for one of its users. No tackygram change: the component answers disco#info to anyone, linked or not. No new strings. Tests: gateway-chat.test.ts, 3 (the listed gateway named for its own JID linked and unlinked, nobody else; libtacky's default on read as off, switched off once, never on; a gateway on another server found by its own disco info and a plain server left plain), chat-view.test.ts 1 (the gateway's own chat with libtacky on: padlock "No end-to-end encryption", libtacky switched off, no exposed row); all four fail without the OmemoChats change. CHANGELOG Unreleased: Fixes #60. make check STRICT=1 clean (2039 keys), make test-ui 367 files, 4001 passed, 8 skipped, make test-shell ok.

ann closed this issue

2026-10-27 08:56:51 +00:00

ann commented

2026-10-27 08:56:58 +00:00

Owner

Fixed in the app. The chat with the gateway itself (telegram.another.im) is now known as a gateway chat from the gateway's own identity, not from whether you are linked, so it always shows "No end-to-end encryption" as a neutral note and its messages are never red. Before, the app only knew Telegram contacts behind the gateway, so after unlinking the gateway's own chat fell back to "encrypted by default" and every message in it was marked "Not encrypted".

No gateway change was needed: tackygram already answers who it is to anyone, linked or not.

On develop in 25eaaba8, for app 0.7.7. Works with any tackygram version.

Fixed in the app. The chat with the gateway itself (telegram.another.im) is now known as a gateway chat from the gateway's own identity, not from whether you are linked, so it always shows "No end-to-end encryption" as a neutral note and its messages are never red. Before, the app only knew Telegram *contacts* behind the gateway, so after unlinking the gateway's own chat fell back to "encrypted by default" and every message in it was marked "Not encrypted". No gateway change was needed: tackygram already answers who it is to anyone, linked or not. On `develop` in 25eaaba8, for app 0.7.7. Works with any tackygram version.