minor spelling and formatting on whisper specs

This commit is contained in:
Corey 2019-10-08 16:07:48 -04:00
parent 76d2332c3e
commit dc5f4330e2
No known key found for this signature in database
GPG Key ID: 65CAB2A922CDF343
1 changed files with 9 additions and 17 deletions

View File

@ -21,14 +21,6 @@
- [Whisper V6 extensions](#whisper-v6-extensions)
- [Request historic messages](#request-historic-messages)
- [shhext_requestMessages](#shhext_requestmessages)
<!-- - [Personal discovery topic](#personal-discovery-topic) C.P. Oct 8, 2019 -->
<!-- - [Generic discovery topic](#generic-discovery-topic) C.P. Oc8, 2019 -->
- [One-to-one topic](#one-to-one-topic)
- [Group chat topic](#group-chat-topic)
- [Message encryption](#message-encryption)
- [Whisper V6 extensions](#whisper-v6-extensions)
- [Request historic messages](#request-historic-messages)
- [shhext_requestMessages](#shhextrequestmessages)
## Abstract
@ -204,9 +196,9 @@ One-to-one messages are encrypted using asymmetric encryption.
### Request historic messages
Sends a request for historic messages to a Mailserver. The Mailserver node MUST be a direct peer and MUST be marked a trusted (using `shh_markTrustedPeer`).
Sends a request for historic messages to a Mailserver. The Mailserver node MUST be a direct peer and MUST be marked as trusted (using `shh_markTrustedPeer`).
The request does not wait for the response. It marely sends a peer-to-peer message to the Mailserver and it's up to Mailserver to process it and start sending historic messages.
The request does not wait for the response. It merely sends a peer-to-peer message to the Mailserver and it's up to Mailserver to process it and start sending historic messages.
The drawback of this approach is that it is impossible to tell which historic messages are the result of which request.