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.
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.