mirror of
https://github.com/simplex-chat/simplex-chat.git
synced 2026-10-25 19:03:18 +00:00
deploy: 7810fc4752
This commit is contained in:
1 parent
744335987b
commit
220092f08f
3 files changed
+4
No files matched your search
@@ -1056,6 +1056,7 @@ eventWord = 1* ALPHA
|
||||
<p><code>x.grp.leave</code> message is sent to all members by the member leaving the group. If the only group <code>owner</code> leaves the group, it will not be possible to delete it with <code>x.grp.del</code> message - but all members can still leave the group with <code>x.grp.leave</code> message and then delete a local copy of the group.</p>
|
||||
<p><code>x.grp.del</code> 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 <code>owner</code> role. Receiving clients MUST ignore this message if it is received from member other than with <code>owner</code> role.</p>
|
||||
<p><code>x.grp.info</code> 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 <code>owner</code> role. Receiving clients MUST ignore this message if it is received from member other than with <code>owner</code> role.</p>
|
||||
<p>Group profile can include optional <code>chatLayout</code> property (<code>classic</code> or <code>terminal</code>) set by a group owner. Clients use it as the layout of the group chat, also after it is changed by <code>x.grp.info</code>, unless the user chose another layout for this chat. Clients MUST treat unknown values as absent.</p>
|
||||
<p><code>x.grp.direct.inv</code> message is sent to a group member to propose establishing a direct connection between members, thus creating a contact with another member.</p>
|
||||
<p><code>x.grp.msg.forward</code> message is sent by inviting member to forward messages between introduced members, while they are connecting. This message MUST NOT contain another <code>x.grp.msg.forward</code> message.</p>
|
||||
<h3 id="channels-relay-mediated-groups" tabindex="-1">Channels: relay-mediated groups</h3>
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -61,6 +61,7 @@
|
||||
"type": "string",
|
||||
"metadata": {"comment": "group purpose / short description (160 characters)"}
|
||||
},
|
||||
"chatLayout": {"enum": ["classic", "terminal"]},
|
||||
"groupPreferences": {
|
||||
"optionalProperties": {
|
||||
"commands": {
|
||||
|
||||
Reference in new issue
Block a user