status-im
/
specs
mirror of https://github.com/status-im/specs.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Commented out code not in V1

This commit is contained in:
Corey 2019-10-08 16:00:48 -04:00
parent 62e7eb0287
commit 76d2332c3e
No known key found for this signature in database
GPG Key ID: 65CAB2A922CDF343
1 changed files with 13 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
status-whisper-usage-spec.md
View File

@ -18,6 +18,14 @@
- [One-to-one topic](#one-to-one-topic) - [One-to-one topic](#one-to-one-topic)
- [Group chat topic](#group-chat-topic) - [Group chat topic](#group-chat-topic)
- [Message encryption](#message-encryption) - [Message encryption](#message-encryption)
- [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) - [Whisper V6 extensions](#whisper-v6-extensions)
- [Request historic messages](#request-historic-messages) - [Request historic messages](#request-historic-messages)
- [shhext_requestMessages](#shhextrequestmessages) - [shhext_requestMessages](#shhextrequestmessages)
@ -145,9 +153,10 @@ for i = 0; i < topicLen; i++ {
} }
``` ```
<!-- NOTE: commented out as it is currently not used. In code for potential future use. - C.P. Oct 8, 2019
### Personal discovery topic ### Personal discovery topic
Personal discovery topic is used to ??? Personal discovery topic is used to ???
A client MUST implement it following the algorithm below: A client MUST implement it following the algorithm below:
```golang ```golang
@ -166,13 +175,14 @@ for i = 0; i < topicLen; i++ {
} }
``` ```
Each Status Client SHOULD listen to this topic in order to receive ??? Each Status Client SHOULD listen to this topic in order to receive ??? -->
<!-- NOTE: commented out as it is no longer valid as of V1. - C.P. Oct 8, 2019
### Generic discovery topic ### Generic discovery topic
Generic discovery topic is a legacy topic used to handle all one-to-one chats. The newer implementation should rely on [Partitioned Topic](#partitioned-topic) and [Personal discovery topic](#personal-discovery-topic). Generic discovery topic is a legacy topic used to handle all one-to-one chats. The newer implementation should rely on [Partitioned Topic](#partitioned-topic) and [Personal discovery topic](#personal-discovery-topic).
Generic discovery topic MUST be created following [Public chats](#public-chats) topic algorithm using string `contact-discovery` as a name. Generic discovery topic MUST be created following [Public chats](#public-chats) topic algorithm using string `contact-discovery` as a name. -->
### One-to-one topic ### One-to-one topic