From f60b3c7920d9bc5de2eaf950eef1b9175ac00ba7 Mon Sep 17 00:00:00 2001 From: chengyongru Date: Thu, 25 Jun 2026 10:23:36 +0800 Subject: [PATCH] docs: explain Telegram rich messages opt-in maintainer edit: document that richMessages defaults to false, when to enable it, and why Telegram Web users should leave it disabled. --- docs/chat-apps.md | 2 ++ docs/configuration.md | 2 ++ 2 files changed, 4 insertions(+) diff --git a/docs/chat-apps.md b/docs/chat-apps.md index a76fd1a2..9fb787ce 100644 --- a/docs/chat-apps.md +++ b/docs/chat-apps.md @@ -79,6 +79,8 @@ If `nanobot channels status` does not show the channel as enabled, the config sn ``` > You can find your **User ID** in Telegram settings. It is shown as `@yourUserId`. Copy this value **without the `@` symbol** and paste it into the config file. +> +> `richMessages` defaults to `false`. Set it to `true` only if your Telegram client supports Bot API 10.1 rich messages and you want richer markdown rendering; keep it disabled for Telegram Web, which may show unsupported-message errors for rich messages. **3. Run** diff --git a/docs/configuration.md b/docs/configuration.md index 32a81d08..e32d23cd 100644 --- a/docs/configuration.md +++ b/docs/configuration.md @@ -1482,6 +1482,8 @@ Global settings that apply to all channels. Configure under the `channels` secti } ``` +Telegram `richMessages` defaults to `false`. Enable it only to opt in to Bot API 10.1 `sendRichMessage` rendering; leave it disabled for Telegram Web clients that show unsupported-message errors for rich messages. + ### Retry Behavior Retry is intentionally simple.