Explorar el Código

Replace "Enabling Appservice Double Puppet" with "This"

Enabling Appservice Double Puppet is contrasted with "Enabling double puppeting by enabling the Shared Secret Auth service", therefore it can be just called as "this" if Shared Secret Auth service is not mentioned below.

Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
pull/3837/head
Suguru Hirahara hace 1 año
padre
commit
e14443bcc5
No se encontró ninguna clave conocida en la base de datos para esta firma ID de clave GPG: E4F9743DAB4B7B75
Se han modificado 3 ficheros con 3 adiciones y 3 borrados
  1. +1
    -1
      docs/configuring-playbook-bridge-mautrix-gmessages.md
  2. +1
    -1
      docs/configuring-playbook-bridge-mautrix-meta-instagram.md
  3. +1
    -1
      docs/configuring-playbook-bridge-mautrix-meta-messenger.md

+ 1
- 1
docs/configuring-playbook-bridge-mautrix-gmessages.md Ver fichero

@@ -36,7 +36,7 @@ To set it up, you have 2 ways of going about it.


The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook. The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook.


Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.
This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.


#### Method 2: manually, by asking each user to provide a working access token #### Method 2: manually, by asking each user to provide a working access token




+ 1
- 1
docs/configuring-playbook-bridge-mautrix-meta-instagram.md Ver fichero

@@ -84,7 +84,7 @@ To set it up, you have 2 ways of going about it.


The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook. The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook.


Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.
This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.


#### Method 2: manually, by asking each user to provide a working access token #### Method 2: manually, by asking each user to provide a working access token




+ 1
- 1
docs/configuring-playbook-bridge-mautrix-meta-messenger.md Ver fichero

@@ -102,7 +102,7 @@ To set it up, you have 2 ways of going about it.


The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook. The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook.


Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.
This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.


#### Method 2: manually, by asking each user to provide a working access token #### Method 2: manually, by asking each user to provide a working access token




Cargando…
Cancelar
Guardar