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.
This commit is contained in:
@@ -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.
|
> 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**
|
**3. Run**
|
||||||
|
|||||||
@@ -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 Behavior
|
||||||
|
|
||||||
Retry is intentionally simple.
|
Retry is intentionally simple.
|
||||||
|
|||||||
Reference in New Issue
Block a user