YunoHost-Apps/mautrix_whatsapp_ynh
1
0
Fork 0
mirror of https://github.com/YunoHost-Apps/mautrix_whatsapp_ynh.git synced 2024-09-03 19:46:01 +02:00
Code Issues Activity Actions

Merge pull request #61 from YunoHost-Apps/testing

Browse source 
Testing to master
This commit is contained in:
Dante 2022-07-06 20:05:13 +01:00 • committed by GitHub
commit 2ce91d46b2
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
8 changed files with 231 additions and 147 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -24,7 +24,7 @@ Therefore, [Synapse for YunoHost](https://github.com/YunoHost-Apps/synapse_ynh)
** Attention: always backup and restore the Yunohost matrix_synapse et mautrix_whatsapp apps together!** ** Attention: always backup and restore the Yunohost matrix_synapse et mautrix_whatsapp apps together!**
**Shipped version:** 0.3.0~ynh1 **Shipped version:** 0.5.0~ynh1
## Disclaimers / important information ## Disclaimers / important information
### List of known public services ### List of known public services

2
README_fr.md
View file

@ -24,7 +24,7 @@ C'est pourquoi [Synapse for YunoHost](https://github.com/YunoHost-Apps/synapse_y
** Attention : sauvegardez et restaurez toujours les deux applications Yunohost matrix_synapse et mautrix_whatsapp en même temps!** ** Attention : sauvegardez et restaurez toujours les deux applications Yunohost matrix_synapse et mautrix_whatsapp en même temps!**
**Version incluse :** 0.3.0~ynh1 **Version incluse :** 0.5.0~ynh1
## Avertissements / informations importantes ## Avertissements / informations importantes
### Liste de passerelles publiques ### Liste de passerelles publiques

12
check_process
View file

@ -17,12 +17,12 @@
setup_private=0 setup_private=0
setup_public=0 setup_public=0
upgrade=1 upgrade=1
upgrade=1 from_commit=ede0231ac59aaa1d65a3009bcbdfe333bf5e87fd upgrade=1 from_commit=42df5b910927283241e185dcb8a62089adeb9c85
upgrade=1 from_commit=443ac4fb96297455281d9495844dde3b9a197214 upgrade=1 from_commit=23cd51919e2b09865256a21214865d798bd843f6
backup_restore=1 backup_restore=1
multi_instance=1 multi_instance=1
;;; Upgrade options ;;; Upgrade options
; commit=ede0231ac59aaa1d65a3009bcbdfe333bf5e87fd ; commit=42df5b910927283241e185dcb8a62089adeb9c85
name=0.1.8 name=0.3.0
; commit=443ac4fb96297455281d9495844dde3b9a197214 ; commit=23cd51919e2b09865256a21214865d798bd843f6
name=0.1.10 name=0.2.4

4
conf/amd64.src
View file

@ -1,5 +1,5 @@
SOURCE_URL=https://github.com/mautrix/whatsapp/releases/download/v0.3.0/mautrix-whatsapp-amd64 SOURCE_URL=https://github.com/mautrix/whatsapp/releases/download/v0.5.0/mautrix-whatsapp-amd64
SOURCE_SUM=b85afe01cb929945bcc1678db8ac80aa973c5df699eb9b68dd00236cef600a33 SOURCE_SUM=fae05ccc2c4ecf0d2d429ad701c3223483e1f644c0dd3d3b016c0eb81bc95b1b
SOURCE_SUM_PRG=sha256sum SOURCE_SUM_PRG=sha256sum
SOURCE_IN_SUBDIR=false SOURCE_IN_SUBDIR=false
SOURCE_FILENAME=mautrix-whatsapp SOURCE_FILENAME=mautrix-whatsapp

4
conf/arm64.src
View file

@ -1,5 +1,5 @@
SOURCE_URL=https://github.com/mautrix/whatsapp/releases/download/v0.3.0/mautrix-whatsapp-arm64 SOURCE_URL=https://github.com/mautrix/whatsapp/releases/download/v0.5.0/mautrix-whatsapp-arm64
SOURCE_SUM=86cfa86a3f4a3a2633f08655fc8f839fbaefbfa08debe7a81f95f1e915f90f11 SOURCE_SUM=8c9f7ebe11e5e3c4d27b0b1a48dabdada4a11405cd10192c662360a64522cc2d
SOURCE_SUM_PRG=sha256sum SOURCE_SUM_PRG=sha256sum
SOURCE_IN_SUBDIR=false SOURCE_IN_SUBDIR=false
SOURCE_FILENAME=mautrix-whatsapp SOURCE_FILENAME=mautrix-whatsapp

4
conf/armhf.src
View file

@ -1,5 +1,5 @@
SOURCE_URL=https://github.com/mautrix/whatsapp/releases/download/v0.3.0/mautrix-whatsapp-arm SOURCE_URL=https://github.com/mautrix/whatsapp/releases/download/v0.5.0/mautrix-whatsapp-arm
SOURCE_SUM=8ac11ef71fe1f88c68bd71ce9291f79a59b670dc8fdba10e3afcc0ed3416113d SOURCE_SUM=2812c2e69df23f5a716e23c2fc6152d505e6c9d8e414690cc79d3a11d2fd630c
SOURCE_SUM_PRG=sha256sum SOURCE_SUM_PRG=sha256sum
SOURCE_IN_SUBDIR=false SOURCE_IN_SUBDIR=false
SOURCE_FILENAME=mautrix-whatsapp SOURCE_FILENAME=mautrix-whatsapp

126
conf/config.yaml
View file

@ -1,4 +1,4 @@
# From v0.2.1 https://github.com/mautrix/whatsapp/blob/master/example-config.yaml # From v0.5.0 https://github.com/mautrix/whatsapp/blob/master/example-config.yaml
# Homeserver details. # Homeserver details.
homeserver: homeserver:
# The address that this appservice can use to connect to the homeserver. # The address that this appservice can use to connect to the homeserver.
@ -16,6 +16,8 @@ homeserver:
status_endpoint: null status_endpoint: null
# Endpoint for reporting per-message status. # Endpoint for reporting per-message status.
message_send_checkpoint_endpoint: null message_send_checkpoint_endpoint: null
# Does the homeserver support https://github.com/matrix-org/matrix-spec-proposals/pull/2246?
async_media: false
# Application service host/registration related details. # Application service host/registration related details.
# Changing these values requires regeneration of the registration. # Changing these values requires regeneration of the registration.
@ -47,19 +49,6 @@ appservice:
max_conn_idle_time: null max_conn_idle_time: null
max_conn_lifetime: null max_conn_lifetime: null
# Settings for provisioning API
provisioning:
# Prefix for the provisioning API paths.
prefix: /_matrix/provision
# Shared secret for authentication. If set to "generate", a random secret will be generated,
# or if set to "disable", the provisioning API will be disabled.
shared_secret: generate
# Segment API key to enable analytics tracking for web server
# endpoints. Set to null to disable.
# Currently the only events are login start, QR code retrieve, and login
# success/failure.
segment_key: null
# The unique ID of this appservice. # The unique ID of this appservice.
#id: whatsapp #id: whatsapp
id: __BOTNAME__ id: __BOTNAME__
@ -82,6 +71,9 @@ appservice:
as_token: "This value is generated when generating the registration" as_token: "This value is generated when generating the registration"
hs_token: "This value is generated when generating the registration" hs_token: "This value is generated when generating the registration"
# Segment API key to track some events, like provisioning API login and encryption errors.
segment_key: null
# Prometheus config. # Prometheus config.
metrics: metrics:
# Enable prometheus metrics? # Enable prometheus metrics?
@ -95,7 +87,7 @@ whatsapp:
os_name: Mautrix-WhatsApp bridge os_name: Mautrix-WhatsApp bridge
# Browser name that determines the logo shown in the mobile app. # Browser name that determines the logo shown in the mobile app.
# Must be "unknown" for a generic icon or a valid browser name if you want a specific icon. # Must be "unknown" for a generic icon or a valid browser name if you want a specific icon.
# List of valid browser names: https://github.com/tulir/whatsmeow/blob/2a72655ef600a7fd7a2e98d53ec6da029759c4b8/binary/proto/def.proto#L1582-L1594 # List of valid browser names: https://github.com/tulir/whatsmeow/blob/8b34d886d543b72e5f4699cf5b2797f68d598f78/binary/proto/def.proto#L38-L51
browser_name: unknown browser_name: unknown
# Bridge config # Bridge config
@ -111,21 +103,24 @@ bridge:
# {{.FullName}} - full name from contact list # {{.FullName}} - full name from contact list
# {{.FirstName}} - first name from contact list # {{.FirstName}} - first name from contact list
displayname_template: "{{if .PushName}}{{.PushName}}{{else if .BusinessName}}{{.BusinessName}}{{else}}{{.JID}}{{end}} (WA)" displayname_template: "{{if .PushName}}{{.PushName}}{{else if .BusinessName}}{{.BusinessName}}{{else}}{{.JID}}{{end}} (WA)"
# Should the bridge create a space for each logged-in user and add bridged rooms to it?
# Users who logged in before turning this on should run `!wa sync space` to create and fill the space for the first time.
personal_filtering_spaces: false
# Should the bridge send a read receipt from the bridge bot when a message has been sent to WhatsApp? # Should the bridge send a read receipt from the bridge bot when a message has been sent to WhatsApp?
delivery_receipts: false delivery_receipts: false
# Whether the bridge should send the message status as a custom com.beeper.message_send_status event.
message_status_events: false
# Whether the bridge should send error notices via m.notice events when a message fails to bridge.
message_error_notices: true
# Should incoming calls send a message to the Matrix room? # Should incoming calls send a message to the Matrix room?
call_start_notices: true call_start_notices: true
# Should another user's cryptographic identity changing send a message to Matrix? # Should another user's cryptographic identity changing send a message to Matrix?
identity_change_notices: false identity_change_notices: false
portal_message_buffer: 128 portal_message_buffer: 128
# Settings for handling history sync payloads. These settings only apply right after login, # Settings for handling history sync payloads.
# because the phone only sends the history sync data once, and there's no way to re-request it
# (other than logging out and back in again).
history_sync: history_sync:
# Should the bridge create portals for chats in the history sync payload? # Should the bridge create portals for chats in the history sync payload?
create_portals: true create_portals: true
# Maximum age of chats in seconds to create portals for. Set to 0 to create portals for all chats in sync payload.
max_age: 604800
# Enable backfilling history sync payloads from WhatsApp using batch sending? # Enable backfilling history sync payloads from WhatsApp using batch sending?
# This requires a server with MSC2716 support, which is currently an experimental feature in synapse. # This requires a server with MSC2716 support, which is currently an experimental feature in synapse.
# It can be enabled by setting experimental_features -> msc2716_enabled to true in homeserver.yaml. # It can be enabled by setting experimental_features -> msc2716_enabled to true in homeserver.yaml.
@ -140,6 +135,66 @@ bridge:
# Should the bridge request a full sync from the phone when logging in? # Should the bridge request a full sync from the phone when logging in?
# This bumps the size of history syncs from 3 months to 1 year. # This bumps the size of history syncs from 3 months to 1 year.
request_full_sync: false request_full_sync: false
# Settings for media requests. If the media expired, then it will not
# be on the WA servers.
# Media can always be requested by reacting with the ♻️ (recycle) emoji.
# These settings determine if the media requests should be done
# automatically during or after backfill.
media_requests:
# Should expired media be automatically requested from the server as
# part of the backfill process?
auto_request_media: true
# Whether to request the media immediately after the media message
# is backfilled ("immediate") or at a specific time of the day
# ("local_time").
request_method: immediate
# If request_method is "local_time", what time should the requests
# be sent (in minutes after midnight)?
request_local_time: 120
# The maximum number of initial conversations that should be synced.
# Other conversations will be backfilled on demand when the start PM
# provisioning endpoint is used or when a message comes in from that
# chat.
max_initial_conversations: -1
# Settings for immediate backfills. These backfills should generally be
# small and their main purpose is to populate each of the initial chats
# (as configured by max_initial_conversations) with a few messages so
# that you can continue conversations without loosing context.
immediate:
# The number of concurrent backfill workers to create for immediate
# backfills. Note that using more than one worker could cause the
# room list to jump around since there are no guarantees about the
# order in which the backfills will complete.
worker_count: 1
# The maximum number of events to backfill initially.
max_events: 10
# Settings for deferred backfills. The purpose of these backfills are
# to fill in the rest of the chat history that was not covered by the
# immediate backfills. These backfills generally should happen at a
# slower pace so as not to overload the homeserver.
# Each deferred backfill config should define a "stage" of backfill
# (i.e. the last week of messages). The fields are as follows:
# - start_days_ago: the number of days ago to start backfilling from.
# To indicate the start of time, use -1. For example, for a week ago, use 7.
# - max_batch_events: the number of events to send per batch.
# - batch_delay: the number of seconds to wait before backfilling each batch.
deferred:
# Last Week
- start_days_ago: 7
max_batch_events: 20
batch_delay: 5
# Last Month
- start_days_ago: 30
max_batch_events: 50
batch_delay: 10
# Last 3 months
- start_days_ago: 90
max_batch_events: 100
batch_delay: 10
# The start of time
- start_days_ago: -1
max_batch_events: 500
batch_delay: 10
# Should puppet avatars be fetched from the server even if an avatar is already set? # Should puppet avatars be fetched from the server even if an avatar is already set?
user_avatar_sync: true user_avatar_sync: true
# Should Matrix users leaving groups be bridged to WhatsApp? # Should Matrix users leaving groups be bridged to WhatsApp?
@ -150,6 +205,11 @@ bridge:
# Note that updating the m.direct event is not atomic (except with mautrix-asmux) # Note that updating the m.direct event is not atomic (except with mautrix-asmux)
# and is therefore prone to race conditions. # and is therefore prone to race conditions.
sync_direct_chat_list: false sync_direct_chat_list: false
# Should the bridge use MSC2867 to bridge manual "mark as unread"s from
# WhatsApp and set the unread status on initial backfill?
# This will only work on clients that support the m.marked_unread or
# com.famedly.marked_unread room account data.
sync_manual_marked_unread: true
# When double puppeting is enabled, users can use `!wa toggle` to change whether # When double puppeting is enabled, users can use `!wa toggle` to change whether
# presence and read receipts are bridged. These settings set the default values. # presence and read receipts are bridged. These settings set the default values.
# Existing users won't be affected when these are changed. # Existing users won't be affected when these are changed.
@ -197,9 +257,14 @@ bridge:
# Should WhatsApp status messages be bridged into a Matrix room? # Should WhatsApp status messages be bridged into a Matrix room?
# Disabling this won't affect already created status broadcast rooms. # Disabling this won't affect already created status broadcast rooms.
enable_status_broadcast: true enable_status_broadcast: true
# Should sending WhatsApp status messages be allowed?
# This can cause issues if the user has lots of contacts, so it's disabled by default.
disable_status_broadcast_send: true
# Should the status broadcast room be muted and moved into low priority by default? # Should the status broadcast room be muted and moved into low priority by default?
# This is only applied when creating the room, the user can unmute/untag it later. # This is only applied when creating the room, the user can unmute it later.
mute_status_broadcast: true mute_status_broadcast: true
# Tag to apply to the status broadcast room.
status_broadcast_tag: m.lowpriority
# Should the bridge use thumbnails from WhatsApp? # Should the bridge use thumbnails from WhatsApp?
# They're disabled by default due to very low resolution. # They're disabled by default due to very low resolution.
whatsapp_thumbnail: false whatsapp_thumbnail: false
@ -209,6 +274,17 @@ bridge:
# Whether or not created rooms should have federation enabled. # Whether or not created rooms should have federation enabled.
# If false, created portal rooms will never be federated. # If false, created portal rooms will never be federated.
federate_rooms: true federate_rooms: true
# Whether to enable disappearing messages in groups. If enabled, then the expiration time of
# the messages will be determined by the first user to read the message, rather than individually.
# If the bridge only has a single user, this can be turned on safely.
disappearing_messages_in_groups: false
# Should the bridge never send alerts to the bridge management room?
# These are mostly things like the user being logged out.
disable_bridge_alerts: false
# Should the bridge detect URLs in outgoing messages, ask the homeserver to generate a preview,
# and send it to WhatsApp? URL previews can always be sent using the `com.beeper.linkpreviews`
# key in the event content even if this is disabled.
url_previews: false
# The prefix for commands. Only required in non-management rooms. # The prefix for commands. Only required in non-management rooms.
command_prefix: "!wa" command_prefix: "!wa"
@ -248,6 +324,14 @@ bridge:
# Verification by the bridge is not yet implemented. # Verification by the bridge is not yet implemented.
require_verification: true require_verification: true
# Settings for provisioning API
provisioning:
# Prefix for the provisioning API paths.
prefix: /_matrix/provision
# Shared secret for authentication. If set to "generate", a random secret will be generated,
# or if set to "disable", the provisioning API will be disabled.
shared_secret: generate
# Permissions for using the bridge. # Permissions for using the bridge.
# Permitted values: # Permitted values:
# relay - Talk through the relaybot (if enabled), no access otherwise # relay - Talk through the relaybot (if enabled), no access otherwise

224
manifest.json
View file

@ -1,115 +1,115 @@
{ {
"name": "Matrix WhatsApp bridge", "name": "Matrix WhatsApp bridge",
"id": "mautrix_whatsapp", "id": "mautrix_whatsapp",
"packaging_format": 1, "packaging_format": 1,
"description": { "description": {
"en": "Matrix / Synapse puppeting bridge for WhatsApp", "en": "Matrix / Synapse puppeting bridge for WhatsApp",
"fr": "Passerelle Matrix / Synapse pour WhatsApp" "fr": "Passerelle Matrix / Synapse pour WhatsApp"
}, },
"version": "0.3.0~ynh1", "version": "0.5.0~ynh1",
"url": "https://github.com/mautrix/whatsapp", "url": "https://github.com/mautrix/whatsapp",
"upstream": { "upstream": {
"license": "AGPL-3.0-or-later", "license": "AGPL-3.0-or-later",
"admindoc": "https://docs.mau.fi/bridges/go/whatsapp/index.html", "admindoc": "https://docs.mau.fi/bridges/go/whatsapp/index.html",
"code": "https://github.com/mautrix/whatsapp" "code": "https://github.com/mautrix/whatsapp"
}, },
"license": "AGPL-3.0-or-later", "license": "AGPL-3.0-or-later",
"maintainer": { "maintainer": {
"name": "Gredin67", "name": "thardev",
"email": "mautrix_whatsapp_ynh@sans-nuage.fr", "email": "",
"url": "https://github.com/YunoHost-Apps/mautrix_whatsapp_ynh" "url": "https://github.com/YunoHost-Apps/mautrix_whatsapp_ynh"
}, },
"requirements": { "requirements": {
"yunohost": ">= 4.3.0" "yunohost": ">= 4.3.0"
}, },
"multi_instance": true, "multi_instance": true,
"services": [ "services": [
"postgresql" "postgresql"
], ],
"arguments": { "arguments": {
"install": [ "install": [
{ {
"name": "synapsenumber", "name": "synapsenumber",
"type": "string", "type": "string",
"ask": { "ask": {
"en": "Choose the local Synapse instance number to communicate with mautrix_whatsapp.", "en": "Choose the local Synapse instance number to communicate with mautrix_whatsapp.",
"fr": "Choisissez le numéro de l'instance Synapse qui doit communiquer avec mautrix_whatsapp." "fr": "Choisissez le numéro de l'instance Synapse qui doit communiquer avec mautrix_whatsapp."
}, },
"example": "2 (for instance synapse__2)", "example": "2 (for instance synapse__2)",
"help": { "help": {
"en": "If you installed Synapse only once time, then leave default value 1.", "en": "If you installed Synapse only once time, then leave default value 1.",
"fr": "Si vous n'avez installé qu'une fois Synapse, gardez la valeur par défaut 1." "fr": "Si vous n'avez installé qu'une fois Synapse, gardez la valeur par défaut 1."
}, },
"default": "1" "default": "1"
}, },
{ {
"name": "botname", "name": "botname",
"type": "string", "type": "string",
"ask": { "ask": {
"en": "Choose a local Synapse user name for the WhatsApp bot", "en": "Choose a local Synapse user name for the WhatsApp bot",
"fr": "Choisissez un nom d'utilisateur Synapse local pour le robot WhatsApp" "fr": "Choisissez un nom d'utilisateur Synapse local pour le robot WhatsApp"
}, },
"example": "whatsappbot", "example": "whatsappbot",
"help": { "help": {
"en": "A system user will be created. Invite @whatsappbot:localsynapse.servername from an authorized Matrix account to start bridging. Give the Matrix server_name, not the full domain/URL.", "en": "A system user will be created. Invite @whatsappbot:localsynapse.servername from an authorized Matrix account to start bridging. Give the Matrix server_name, not the full domain/URL.",
"fr": "Un utilisateur système sera créé. Inviter @whatsappbot:localsynapse.servername depuis un compte Matrix autorisé pour démarrer une passerelle. Donner le nom du serveur Matrix, pas le domaine/URL complet." "fr": "Un utilisateur système sera créé. Inviter @whatsappbot:localsynapse.servername depuis un compte Matrix autorisé pour démarrer une passerelle. Donner le nom du serveur Matrix, pas le domaine/URL complet."
}, },
"default": "whatsappbot" "default": "whatsappbot"
}, },
{ {
"name": "bot_synapse_adm", "name": "bot_synapse_adm",
"type": "boolean", "type": "boolean",
"ask": { "ask": {
"en": "Give the WhatsApp bot administrator rights to the Synapse instance?", "en": "Give the WhatsApp bot administrator rights to the Synapse instance?",
"fr": "Donner au robot WhatsApp des droits administrateur à l'instance Synapse ?" "fr": "Donner au robot WhatsApp des droits administrateur à l'instance Synapse ?"
}, },
"help": { "help": {
"en": "If true, the bot can group WhatsApp chats in a Matrix space. Not required if you set up Synapse so that non-admins are authorized to create communities.", "en": "If true, the bot can group WhatsApp chats in a Matrix space. Not required if you set up Synapse so that non-admins are authorized to create communities.",
"fr": "Si true, le robot groupera les conversations WhatsApp dans une communauté Matrix. Pas nécessaire si vous avez réglé Synapse pour qu'il autorise les non-admin à créer des communautés." "fr": "Si true, le robot groupera les conversations WhatsApp dans une communauté Matrix. Pas nécessaire si vous avez réglé Synapse pour qu'il autorise les non-admin à créer des communautés."
}, },
"default": true "default": true
}, },
{ {
"name": "encryption", "name": "encryption",
"type": "boolean", "type": "boolean",
"ask": { "ask": {
"en": "Enable end-to-bridge encryption?", "en": "Enable end-to-bridge encryption?",
"fr": "Activer le chiffrement entre Synapse et le bridge ?" "fr": "Activer le chiffrement entre Synapse et le bridge ?"
}, },
"help": { "help": {
"en": "Only activate if you know the prerequisites and constraints related to e2b.", "en": "Only activate if you know the prerequisites and constraints related to e2b.",
"fr": "N'activer que si vous connaissez les prérequis et constraintes liées à e2b." "fr": "N'activer que si vous connaissez les prérequis et constraintes liées à e2b."
}, },
"default": false "default": false
}, },
{ {
"name": "botadmin", "name": "botadmin",
"type": "string", "type": "string",
"ask": { "ask": {
"en": "Choose the Matrix account administrator of the WhatsApp bot", "en": "Choose the Matrix account administrator of the WhatsApp bot",
"fr": "Choisissez le compte Matrix administrateur du robot WhatsApp" "fr": "Choisissez le compte Matrix administrateur du robot WhatsApp"
}, },
"example": "@johndoe:localsynapse.servername or @johndoe:matrix.org", "example": "@johndoe:localsynapse.servername or @johndoe:matrix.org",
"help": { "help": {
"en": "The WhatsApp bot administrator does not need to be a local Synapse account.", "en": "The WhatsApp bot administrator does not need to be a local Synapse account.",
"fr": "Le compte administrateur du robot WhatsApp peut ne pas être un compte local Synapse." "fr": "Le compte administrateur du robot WhatsApp peut ne pas être un compte local Synapse."
}, },
"default": "Your main Matrix account" "default": "Your main Matrix account"
}, },
{ {
"name": "botusers", "name": "botusers",
"type": "string", "type": "string",
"ask": { "ask": {
"en": "Choose Matrix user(s) authorized to bridge with the WhatsApp bot.", "en": "Choose Matrix user(s) authorized to bridge with the WhatsApp bot.",
"fr": "Choisissez le/les compte(s) Matrix autorisés à utiliser la passerelle WhatsApp." "fr": "Choisissez le/les compte(s) Matrix autorisés à utiliser la passerelle WhatsApp."
}, },
"example": "admin or domain or @johndoe:server.name or server.name or *", "example": "admin or domain or @johndoe:server.name or server.name or *",
"default": "domain", "default": "domain",
"help": { "help": {
"en": "Either the administrator only (admin), all local Synapse users (domain), a remote or local user (@johndoe:server.name), a remote server (matrix.org), or all remote/local servers (*) can be authorized. Give the Matrix server_name, not the full domain/URL.", "en": "Either the administrator only (admin), all local Synapse users (domain), a remote or local user (@johndoe:server.name), a remote server (matrix.org), or all remote/local servers (*) can be authorized. Give the Matrix server_name, not the full domain/URL.",
"fr": "L'administrateur seulement (admin), tous les comptes Synapse locaux (domain), un compte local ou distant (@johndoe:server.name), un serveur distant (matrix.org), ou tous les serveurs remote/local (*). Donner le nom du serveur Matrix, pas le domaine/URL complet." "fr": "L'administrateur seulement (admin), tous les comptes Synapse locaux (domain), un compte local ou distant (@johndoe:server.name), un serveur distant (matrix.org), ou tous les serveurs remote/local (*). Donner le nom du serveur Matrix, pas le domaine/URL complet."
} }
} }
] ]
} }
} }