@ -190,11 +192,12 @@ The format is each message contains:
- An RFC3339 time-stamp in UTC to the second
- The Identity of the sender
- The contents of the actual message
- Newlines in Message(s) are encoded as unicode LINE SEPARATOR (\u2028)
- Newlines in Message(s) are encoded as unicode LINE SEPARATOR (`\u2028`)
**NOTE:**
> It is important that the time-stamp be in UTC so that Messages have a
> Consistent time and it is the responsibility of Clients to represent the time-stamp appropriately (for example in local time).
> consistent time and it is the responsibility of Clients to represent the time-stamp appropriately (for example in local time).
The Identity of the sender is simply the Sender's `user@domain.tld` used as part of the Discovery process and bares no meaning to the User's actual identity or in any way carries any personal identifiable information about the user (other than they are `nick` at `domain.tld`).
@ -219,7 +222,7 @@ The support Events are currently:
## Delivery
Once a Message has been Signed and Encrypted to all intended recipients, those recipients are looked up using the Discovery process. Then reach message is sent to the recipient's Endpoint(s).
Once a Message has been Signed and Encrypted to all intended recipients, those recipients are looked up using the Discovery process. Then each message is sent to the recipient's Endpoint(s).
At this point the exact serialisation of the Signed and Encrypted Message is not important, however it is recommended to use the Saltpack Armour encoding.