mirror of
https://github.com/42wim/matterbridge.git
synced 2024-11-25 05:29:40 +01:00
Updated Section Telegram (basic) (markdown)
parent
d526faf712
commit
dbbe925ae3
@ -63,7 +63,7 @@ This basic example will guide you through getting started on your first Telegram
|
||||
|
||||
Message the [BotFather](https://t.me/BotFather) bot and run the `/newbot` command to get started. Once you pick a name it will provide you with a `token` used to access the HTTP API.
|
||||
|
||||
**Set Privacy:**
|
||||
**Disable bot privacy**
|
||||
|
||||
> **You**: /setprivacy
|
||||
>
|
||||
@ -80,8 +80,9 @@ Message the [BotFather](https://t.me/BotFather) bot and run the `/newbot` comman
|
||||
>
|
||||
> **BotFather**: Success! The new status is: DISABLED. /help
|
||||
|
||||
Now add this newly created bot to the Telegram chat you're trying to bridge.
|
||||
|
||||
### 2. Add your config
|
||||
### 2. Add your config to Matterbridge.
|
||||
|
||||
Here is an example gateway bridging `Discord`<>`Telegram`
|
||||
|
||||
@ -119,4 +120,8 @@ The easiest way to retrieve your channel id is to navigate to https://web.telegr
|
||||
|
||||
To add more nodes to this bridge, you simply need to add additional `[[gateway.inout]]` fields.
|
||||
|
||||
Make sure to test your config with the `-debug` flag after each change.
|
||||
Make sure to test your config with the `-debug` flag after each change.
|
||||
|
||||
### Limitations
|
||||
|
||||
- The Telegram API does not report any changes **when messages are deleted** so Matterbridge is unable to remove any bridged messages after they've been sent (This will render many common spam solutions useless). Use regexp with the `IgnoreMessages=` field to remove any common spam messages.
|
Loading…
Reference in New Issue
Block a user