From 220092f08f56d3c561a891a141b84ea348def4b3 Mon Sep 17 00:00:00 2001 From: epoberezkin Date: Sun, 25 Oct 2026 18:03:58 +0000 Subject: [PATCH] deploy: 7810fc47529f24735f681d4e921e2ef2ee2aa7fc --- docs/protocol/simplex-chat.html | 1 + docs/protocol/simplex-chat.md | 2 ++ docs/protocol/simplex-chat.schema.json | 1 + 3 files changed, 4 insertions(+) diff --git a/docs/protocol/simplex-chat.html b/docs/protocol/simplex-chat.html index 87b6793d5b..c50569e6bd 100644 --- a/docs/protocol/simplex-chat.html +++ b/docs/protocol/simplex-chat.html @@ -1056,6 +1056,7 @@ eventWord = 1* ALPHA

x.grp.leave message is sent to all members by the member leaving the group. If the only group owner leaves the group, it will not be possible to delete it with x.grp.del message - but all members can still leave the group with x.grp.leave message and then delete a local copy of the group.

x.grp.del message is sent to all members by the member who deletes the group. Clients who received this message SHOULD keep a local copy of the deleted group, until it is deleted by the user. This message MUST only be sent by members with owner role. Receiving clients MUST ignore this message if it is received from member other than with owner role.

x.grp.info message is sent to all members by the member who updated group profile. Only group owners can update group profiles. Clients MAY implement some conflict resolution strategy - it is currently not implemented by SimpleX Chat client. This message MUST only be sent by members with owner role. Receiving clients MUST ignore this message if it is received from member other than with owner role.

+

Group profile can include optional chatLayout property (classic or terminal) set by a group owner. Clients use it as the layout of the group chat, also after it is changed by x.grp.info, unless the user chose another layout for this chat. Clients MUST treat unknown values as absent.

x.grp.direct.inv message is sent to a group member to propose establishing a direct connection between members, thus creating a contact with another member.

x.grp.msg.forward message is sent by inviting member to forward messages between introduced members, while they are connecting. This message MUST NOT contain another x.grp.msg.forward message.

Channels: relay-mediated groups

diff --git a/docs/protocol/simplex-chat.md b/docs/protocol/simplex-chat.md index ff9fcfa7e1..bc3922a35f 100644 --- a/docs/protocol/simplex-chat.md +++ b/docs/protocol/simplex-chat.md @@ -260,6 +260,8 @@ Currently members can have one of four roles - `owner`, `admin`, `member` and `o `x.grp.info` message is sent to all members by the member who updated group profile. Only group owners can update group profiles. Clients MAY implement some conflict resolution strategy - it is currently not implemented by SimpleX Chat client. This message MUST only be sent by members with `owner` role. Receiving clients MUST ignore this message if it is received from member other than with `owner` role. +Group profile can include optional `chatLayout` property (`classic` or `terminal`) set by a group owner. Clients use it as the layout of the group chat, also after it is changed by `x.grp.info`, unless the user chose another layout for this chat. Clients MUST treat unknown values as absent. + `x.grp.direct.inv` message is sent to a group member to propose establishing a direct connection between members, thus creating a contact with another member. `x.grp.msg.forward` message is sent by inviting member to forward messages between introduced members, while they are connecting. This message MUST NOT contain another `x.grp.msg.forward` message. diff --git a/docs/protocol/simplex-chat.schema.json b/docs/protocol/simplex-chat.schema.json index a9bb2d8735..095e7207be 100644 --- a/docs/protocol/simplex-chat.schema.json +++ b/docs/protocol/simplex-chat.schema.json @@ -61,6 +61,7 @@ "type": "string", "metadata": {"comment": "group purpose / short description (160 characters)"} }, + "chatLayout": {"enum": ["classic", "terminal"]}, "groupPreferences": { "optionalProperties": { "commands": {