From f5e333b51380ce5beacc0e847f50f6e6fde3e7ee Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 1 Nov 2024 21:36:40 +0900 Subject: [PATCH 1/2] Update docs/configuring-playbook-bridge-mautrix-meta-messenger.md: add a note about user ID of the new bridge's bot The user ID of the new bridge (mautrix-meta) is different from that of the old bridge (mautrix-facebook). It is slightly confusing, and the note should help migration. Signed-off-by: Suguru Hirahara --- .../configuring-playbook-bridge-mautrix-meta-messenger.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md index 927475d90..571805bbe 100644 --- a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md +++ b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md @@ -11,12 +11,12 @@ This documentation page only deals with the bridge's ability to bridge to Facebo If you've been using the [mautrix-facebook](./configuring-playbook-bridge-mautrix-facebook.md) bridge, it's possible to migrate the database using [instructions from the bridge documentation](https://docs.mau.fi/bridges/go/meta/facebook-migration.html) (advanced). -Then you may wish to get rid of the Facebook bridge. To do so, send a `clean-rooms` command to the management room with the old bridge bot (`@facebookbot:example.com`). - -This would give you a list of portals and groups of portals you may purge. Proceed with sending commands like `clean recommended`, etc. +Then you may wish to get rid of the Facebook bridge. To do so, send a `clean-rooms` command to the management room with the old bridge bot (`@facebookbot:example.com`). It gives you a list of portals and groups of portals you may purge. Proceed with sending commands like `clean recommended`, etc. Then, consider disabling the old bridge in your configuration, so it won't recreate the portals when you receive new messages. +**Note**: the user ID of the new bridge bot is `@messengerbot:example.com`, not `@facebookbot:example.com`. After disabling the old bridge, its bot user will stop responding to a command. + ## Adjusting the playbook configuration To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: @@ -102,7 +102,7 @@ When using this method, **each user** that wishes to enable Double Puppeting nee ## Usage -You then need to start a chat with `@messengerbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). +You then need to start a chat with `@messengerbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). Note that the user ID of the bridge's bot is not `@facebookbot:example.com`. You then need to send a `login` command and follow the bridge bot's instructions. From 8f7a723b37235c4ff4c0d3466c51564e5594c2a5 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Fri, 1 Nov 2024 21:59:20 +0900 Subject: [PATCH 2/2] Update docs/configuring-playbook-bridge-mautrix-meta-instagram.md: the same paragraph as docs/configuring-playbook-bridge-mautrix-meta-messenger.md Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-bridge-mautrix-meta-instagram.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/configuring-playbook-bridge-mautrix-meta-instagram.md b/docs/configuring-playbook-bridge-mautrix-meta-instagram.md index f7809090d..9b2b44313 100644 --- a/docs/configuring-playbook-bridge-mautrix-meta-instagram.md +++ b/docs/configuring-playbook-bridge-mautrix-meta-instagram.md @@ -14,9 +14,7 @@ If you've been using the [mautrix-instagram](./configuring-playbook-bridge-mautr - both trying to use `@instagrambot:example.com` as their username. This conflict may be resolved by adjusting `matrix_mautrix_instagram_appservice_bot_username` or `matrix_mautrix_meta_instagram_appservice_username` - both trying to bridge the same DMs -To do so, send a `clean-rooms` command to the management room with the old bridge bot (`@instagrambot:example.com`). - -This would give you a list of portals and groups of portals you may purge. Proceed with sending commands like `clean recommended`, etc. +To do so, send a `clean-rooms` command to the management room with the old bridge bot (`@instagrambot:example.com`). It gives you a list of portals and groups of portals you may purge. Proceed with sending commands like `clean recommended`, etc. Then, consider disabling the old bridge in your configuration, so it won't recreate the portals when you receive new messages.