diff --git a/status-spec.md b/status-spec.md index 808224c..8145f4e 100644 --- a/status-spec.md +++ b/status-spec.md @@ -219,7 +219,10 @@ Transport Spec](status-secure-tansport-spec.md) for more. ## Payloads and clients - +On top of secure transport, we have various types of data sync clients and +payload formats for things like 1:1 chat, group chat and public chat. These have +various degrees of standardization. Please refer to [Initial Message Payload +Specification](x8.md) for more details. ## Design Rationale diff --git a/x4.md b/x4.md index b18a436..1fe1775 100644 --- a/x4.md +++ b/x4.md @@ -1,12 +1,3 @@ - - Data Sync Clients - -Data Sync Clients specify a format of payloads exchanged between clients communicating using the Status Protocol. The robust and well-defined format is required in order to provide some security guarantees, for example, clients should not display messages that do not conform to the format, and allow the clients to upgrade the protocol safely in the future. - -The well-defined format also makes it possible to support multiple types of conversations as well as multiple types of content. - -Please refer to [Initial Message Payload Specification](x8.md) for more details. - # Data Sync Layer [MVDS](https://specs.vac.dev/mvds.html) is used for 1:1 and group chats, however it is currently not in use for public chats.