mirror of https://github.com/mautrix/docs.git
50 lines
2.6 KiB
Markdown
50 lines
2.6 KiB
Markdown
# Double puppeting
|
|
You can replace the Matrix ghost of your remote account with your Matrix
|
|
account. When you do so, messages that you send from other clients will be sent
|
|
from your Matrix account instead of the default ghost user.
|
|
|
|
Also, in servers that don't support [MSC2409] (i.e. Synapse before v1.22), it is
|
|
the only way to enable bridging of ephemeral events, such as presence, typing
|
|
notifications and read receipts. If you want to use MSC2409 for ephemeral
|
|
events, make sure `appservice` -> `ephemeral_events` is set to `true` in the
|
|
bridge config and that the registration file has the appropriate flags too
|
|
(you can regenerate the registration after updating the bridge config).
|
|
|
|
[MSC2409]: https://github.com/matrix-org/matrix-doc/pull/2409
|
|
|
|
## Automatically
|
|
Instead of requiring everyone to manually enable double puppeting, you can give
|
|
the bridge access to log in on its own. This makes the process much smoother for
|
|
users, and removes problems if the access token getting invalidated, as the
|
|
bridge can simply automatically relogin.
|
|
|
|
0. Set up [matrix-synapse-shared-secret-auth] on your Synapse.
|
|
* Make sure you set `m_login_password_setup_enabled` to `true` in the config.
|
|
1. Add the login shared secret to `bridge` → `login_shared_secret_map` in the
|
|
config file under the correct server name.
|
|
* In mautrix-imessage and in past versions of other bridges, the field is
|
|
called `login_shared_secret`, as double puppeting was only supported for
|
|
local users.
|
|
2. The bridge will now automatically enable double puppeting for all local users
|
|
when they log into the bridge.
|
|
|
|
[matrix-synapse-shared-secret-auth]: https://github.com/devture/matrix-synapse-shared-secret-auth
|
|
|
|
## Manually
|
|
Double puppeting can only be enabled after logging into the bridge. As with
|
|
the normal login, you must do this in a private chat with the bridge bot.
|
|
|
|
**N.B.** This method is not supported in mautrix-imessage, as it does not
|
|
currently support any commands.
|
|
|
|
1. Log in on the homeserver to get an access token, for example with the command
|
|
```shell
|
|
$ curl -XPOST -d '{"type":"m.login.password","identifier":{"type": "m.id.user", "user": "example"},"password":"wordpass","initial_device_display_name":"a fancy bridge"}' https://example.com/_matrix/client/r0/login
|
|
```
|
|
2. Send `login-matrix <access token>` to the bridge bot. For the Telegram
|
|
bridge, send `login-matrix` without the access token, then send the access
|
|
token in a separate message.
|
|
3. After logging in, the default Matrix ghost of your remote account should
|
|
leave rooms and your account should join all rooms the ghost was in
|
|
automatically.
|