Allow to use telegram Bridge Bot multiple times
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
In Matterbridge this is not a issue. I think the problem is that talk_matterbridge starts for every conversation a new matterbridge instance.
Problem
At the moment it is only possible to use a telegram Bridge bot for one single Group Bridge (e.g. group1_telegram <-> group1_nc) I can't use the same bot the same time for another group (e.g. group2_telegram <-> group2_nc). This is because talk_matterbridge creates second stream for fetching the messages from the telegram API. But there is only one stream allowed, so a Telegram Bridge Bot configured for two Groups will fail.
Solution:
talk_matterbridge should only start one single matterbridge instance. With this using the same bot a second time should work. Furthermore this consumes less resources.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the talk_matterbridge entry point and inspect how Matterbridge instances and Telegram API message streams are created for each conversation. Verify the lifecycle needed for one instance to serve multiple group bridges, then confirm that the same bot can be configured for two groups without creating a second stream and that resource use is reduced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100