664dd1c9df
Introduces Waku in to the relevant places in the specs.
* First draft changes to 1-client.md
* initial waku replace work on 2-account.md
* Rename 3-whisper-usage to waku
There may be broken links after this change
* Initial update for 3-waku-usage.md
* Adjustment to use WHISPER concurrently with WAKU
* Converting 'moving away from whisper' section to `why use waku`
* Added clarification about Open Whisper Systems X3DH usage
* Updated transport privacy, include both whisper and waku
* Updated 1-client, language supports concurrent whisper and waku
* Updated 2-account.md to be whisper/waku concurrent
* Reverted 3-whisper-usage changes, added 9-waku-usage
* Complete revert of 3-whisper-usage
* revert 3-whisper-usage.md
* Fix to 3-whisper-usage.md links
* Update docs/stable/1-client.md
Co-authored-by: Dean Eigenmann <7621705+decanus@users.noreply.github.com>
* Removal of personal pronouns from 1-client.md
* Update to 5-secure-transport.md
* Implemented combined 'whispe/ waku relayer' role
* Addressed ambiguous and stale links in 6-payloads
* Updated 6-payloads
* Fix broken / stale links in 7-group-chat.md
* Fixed stale link 8-eips
* link fix and todo resolved for 1-client.md
* Added 10-waku-mailserver document
* Added gitignore
* Minor tweaks and fixes
* Added Whisper / Waku briding section to 3-whisper-usage
* Updated 10-waku-mailserver
* Updated 9-waku-usage.md
* Made changes to keep Mailserver term consistent
* Removed some redundant comments
* Removed seemingly vistigual '???'
* Including large payload PoW
See
|
||
---|---|---|
.github/workflows | ||
assets | ||
docs | ||
.remarkrc | ||
CNAME | ||
README.md | ||
_config.yml | ||
default.html | ||
home.html | ||
package.json | ||
post.html | ||
spellcheck.yaml | ||
wordlist.txt |
README.md
layout | permalink | nav_exclude |
---|---|---|
default | / | true |
Specifications for Status clients
This repository contains a list of specifications for implementing Status and its various capabilities.
How to contribute
- Create an issue for a new Status Improvement Proposal (SIP) or some bug that you'd like to address
- Create a corresponding PR and ping some existing SIP editors for review
If you need help, ask in #protocol at Status / Discord.
Spellcheck
To run the spellchecker locally, you must install pyspelling.
It can then be run with the following command:
pyspelling -c spellcheck.yml
Words that should be ignored or are unrecognized must be added to the wordlist.
Markdown Verification
We use remark to verify our markdown. You can easily run this tool simply by using our npm
package:
npm install
npm run lint
Spec lifecycle
Every spec has its own lifecycle that shows its maturity. We indicate this in a similar fashion to COSS Lifecycle:
At present (March 30, 2020) this means stable specs are what is in v1 of the Status App. Drafts and raw are work in progress specs.
Status Improvement Proposals (SIPs)
The main specification for writing a Status client is 1/CLIENT.
For all full index of all specs, see specs.status.im, especially stable specs.
Protocol Research
These are protocols that are currently being researched. These are designed to be useful outside of Status as well. To the extent that these protocols are used within Status clients, they will show up as SIPs in the future.
To see more on this, please visit the current home: vac protocol.