41 lines
1.3 KiB
Plaintext
41 lines
1.3 KiB
Plaintext
A bot to synchronise chat between an NMDC/ADC hub and a Telegram supergroup.
|
|
|
|
Tags: NMDC
|
|
Written in Go
|
|
|
|
## FEATURES
|
|
|
|
- NMDC/ADC support
|
|
- Exclude messages from multiple hub nicks (e.g. hub-security, any helper bots that are unnecessary given telegram's features)
|
|
- Standalone binary
|
|
|
|
## SETUP
|
|
|
|
Create a new telegram bot
|
|
- Use BotFather to create a new bot
|
|
- Use BotFather to disable its privacy mode for group chats
|
|
- Use BotFather to add commands (that appear in the groupchat). Recommendation:
|
|
|
|
`
|
|
userlist - List native online users
|
|
`
|
|
|
|
Create a telegram group
|
|
- Manually create a group chat and add the bot to it
|
|
- Convert group chat to supergroup
|
|
- Grant bot to be an administrator (including ability to add more administrators)
|
|
- Settings > "Who can add members" > Only administrators
|
|
- Create an invite link
|
|
|
|
Handover to nmdc-telegramfrontend
|
|
- Run this bot with no -GroupChatID, to learn the groupchat ID
|
|
- Post a test message in the group chat, to discover the groupchat ID
|
|
- Leave the group chat (long press on mobile, can't do it on desktop)
|
|
- Run this bot with -GroupChatID for normal operation
|
|
|
|
## USAGE
|
|
|
|
Chat with the bot to enter/leave the synchronised channel.
|
|
|
|
Sometimes the telegram invite links can take a few minutes to activate, especially if there has been unusual activity (e.g. frequent join/parts)
|