... | ... | @@ -18,7 +18,7 @@ The signature covers a BDF list with three elements: `timestamp` (int), `contact |
|
|
|
|
|
The creator sets the private group's visibility to VISIBLE when sending an invite message.
|
|
|
|
|
|
**1: JOIN** - Sent by an invitee in response to an invite, or by a peer to a contact who is also a member of the private group. The message body is a BDF list with three elements: `messageType` (int), `privateGroupId` (unique ID), and `previousMessageId` (unique ID).
|
|
|
**1: JOIN** - Sent by an invitee in response to an invite, or by a peer when sharing the private group with a contact who is also a member. The message body is a BDF list with three elements: `messageType` (int), `privateGroupId` (unique ID), and `previousMessageId` (unique ID).
|
|
|
|
|
|
`previousMessageId` is the ID of the previous message in this session.
|
|
|
|
... | ... | @@ -26,7 +26,7 @@ An invitee sets the private groups's visibility to SHARED when sending a join me |
|
|
|
|
|
A peer sets the private group's visibility to VISIBLE or SHARED when sending or receiving a join message, depending on the state machine.
|
|
|
|
|
|
**2: LEAVE** - Sent by an invitee in response to an invite, or when leaving the private group, or by a peer to a contact who is also a member of the private group. The message body is a BDF list with three elements: `messageType` (int), `privateGroupId` (unique ID), and `previousMessageId` (unique ID).
|
|
|
**2: LEAVE** - Sent by an invitee in response to an invite, or by an invitee or a peer when leaving the private group, or by the creator when dissolving the private group. The message body is a BDF list with three elements: `messageType` (int), `privateGroupId` (unique ID), and `previousMessageId` (unique ID).
|
|
|
|
|
|
`previousMessageId` is the ID of the previous message in this session.
|
|
|
|
... | ... | @@ -38,7 +38,7 @@ The sender sets the private group's visibility to INVISIBLE when sending an abor |
|
|
|
|
|
### Validity policy
|
|
|
|
|
|
* An invite message is valid if it is well-formed, it is sent by the group creator, and it has a valid signature from the group creator.
|
|
|
* An invite message is valid if it is well-formed, is sent by the group creator, and has a valid signature from the group creator.
|
|
|
* A join, leave or abort message is valid if it is well-formed and its previous message (if any) is a valid message in the same session.
|
|
|
|
|
|
### Storage policy
|
... | ... | |