Open Arcsion opened 1 year ago
Perhaps you've resolved it at this point, but it's probably that the namespaces for the two bridges are overlapping.
If your first bridge uses @twitter_.*:example\.com''
, that's going to overlap with @twitter_s1_.*:example\.com'
I have two Twitter accounts and I want to manage their messages together.
However, mautrix-twitter’s Twitter Bridge Bot can only login one account ones. So I started thinking whether I could start 2 mautrix-twitter bridges to catch all messages.
I think I’m 90% done: I could login using the second twitter bot, however, I could not receive messages because there’re still some conflicts.
Here is how I deploy the second bridge:
Creating the second database
Making a new directory and config for new bridge
In
mautrix-twitter-s1/config.yaml
(only listing changes)Register the new bridge
After editing the config, I run
again to get
registration.yaml
:Then I register the bridge to synapse:
And in
synapse/homeserver.yaml
:Start the container
Then I edit the docker-compose.yml, adding lines below. I have already set another bridge by then, so here I show thier config together.
Encounter problems
Then I use
docker-compose up -d
to start my service, start a chat with@twitterbot-s1:example.com
.I could successfully login:
...but when the brige try to sync msgs, it encounter such problems:
I tried to change displayname_template from
"{displayname} (Twitter)"
to"{displayname} (Twitter-s1)"
in order to solve possible conflicts, but problem remains.Could anyone give me some ideas on how should I solve this? Or, should I attach the configration of my first twitter brige (which works fine)?