logos-messaging/specs
1
0
Fork 0
mirror of https://github.com/logos-messaging/specs.git synced 2026-01-02 14:13:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update message types

Browse Source
This commit is contained in:
Jazz Turner-Baggs 2025-09-25 22:19:43 -07:00 committed by GitHub
parent da323c9c17
commit f9b9464988
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
informational/chatdefs.md
View File

@ -49,13 +49,13 @@ Terms are organized into the following categories for clarity and ease of refere
**Payload**: The encoded bytes as produced by a chat protocol. The term `message` is avoided due to conlicts with other layers.
**Frame**: [TODO]
**Frame**: A datastructure which is required to implement a chat protocol. Frames are used to disambiguate the objects defined by chat protocols from transport 'messages' and application `content`.
**Content**: The information that is intended for end-users or applications. This is in contrast with a `frame` which is
**Content**: The data that is intended for end-users or applications. Chat protocols transmit and route content between clients.
**ContentType**: [TODO]
**ContentType**: The structured format of content. These datastructures represent specific encodings of Text, Image, Audio data.
**Delivery Acknowledgement**: [TODO]
**Delivery Acknowledgement**: A notification from a receiving client to sender that their message was successfully received. While similar to a read-receipt delivery acknowledgements differ in that the acknowledgement originates based on the client, where read-receipts are fired when they are displayed to a user.
**Invite**: [TODO]