-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: improvements on docs #24
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
ac17ef3
to
c891cc3
Compare
5ec4692
to
753d4ed
Compare
Can we move away from the I wonder if it's possible to set the page order via header metadata like in Hugo? |
Co-authored-by: fryorcraken.eth <[email protected]>
Co-authored-by: fryorcraken.eth <[email protected]>
Co-authored-by: fryorcraken.eth <[email protected]>
Co-authored-by: fryorcraken.eth <[email protected]>
Co-authored-by: fryorcraken.eth <[email protected]>
Great point. |
Smaller PRs in the future please. This is too cumbersome to review. |
@@ -1,46 +1,49 @@ | |||
--- | |||
title: Content Topic and How to Choose One | |||
title: Protocols Overview by Example |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd rather delete this page and re-write from scratch in a different PR.
On principle, the schema is a good idea but it's not readable in the current state. The mental load to read the diagram is too high:
- TMI: we can exclude pubsub topic and encryption from it
- Terminology is a bit too specialized, ie "history query" for a store query
- too many participants: may make sense to split the diagram to illustrate different points.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
made a note!
can we merge this for now, and I can followup with the refactoring in another PR.
this would also allow the existing #27 to not encounter any merge conflicts.
docs/Concepts/6.md
Outdated
|
||
Waku includes a number of protocol covering the following domains like privacy preservation, censorship resistance, portability/runs anywhere. | ||
- `/supercrypto/1/notification/proto` | ||
- `/supercrypto/1/private-message/proto` | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kaiserd I believe we are looking in strategy to improve anonymity around content topic usage, similarly to what Status protocol does with their content topic (4 bytes of the hash of a key).
Am I correct? Should we mention that recommendation that are more privacy minded are in the works? Do we ahve an issue that tracks the work?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is part of the pubsub Topic milestone, part of vacp2p/research#154
We do not have anything concrete at this point though. I am not sure, it will involve having specific content topic names. Most likely, deciding on content topics (including naming) will be up to applications. Waku will make sure the mapping of content topics to pubsub Topics preserves anonymity properties.
Agreed! Documentations have been hard to track, with very unreadable diff. |
The recommended format for content topics is as follows: | ||
|
||
Waku offers incentivization mechanisms to run nodes, whereas libp2p does not. | ||
`/{dapp-name}/{version}/{content-topic-name}/{encoding}` | ||
|
||
Additionally, a user or a developer does not have to deploy own infra as a prerequisite to use Waku, it is a service network. | ||
However, it is encouraged to [run your own node](https://github.com/status-im/nwaku/tree/master/docs/operators) to support and decentralize the network. | ||
- `dapp-name`: The name of your dApp, it must be unique to avoid conflict with other dApps. | ||
- `version`: We usually start at `1`, useful when introducing breaking changes in your messages. | ||
- `content-topic-name`: The actual content topic name to use for filtering. | ||
If your dApp uses Waku for several features, | ||
you should use a content topic per feature. | ||
- `encoding`: The encoding format of the message, [Protobuf](https://developers.google.com/protocol-buffers) is most often used: `proto`. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@danisharora099 let's remove pubsub topics from the doc for now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well done
* add: security features * add: protocols overview by example * add: different protocols * add: spell check on CI * rm: yarn.lock to avoid inconsistencies * Update docs/Concepts/1.md Co-authored-by: fryorcraken.eth <[email protected]> * Update docs/Concepts/2.md Co-authored-by: fryorcraken.eth <[email protected]> * Update docs/Concepts/2.md Co-authored-by: fryorcraken.eth <[email protected]> * Update docs/Concepts/7.md Co-authored-by: fryorcraken.eth <[email protected]> * Update docs/Concepts/7.md Co-authored-by: fryorcraken.eth <[email protected]> * convert mscgen sequence to mermaid * partially adress review comments * address: comments * fix: ci * chore: address minor typos/changes in docs * add: pros/cons for discv5 and peer-exchange * fix: minor typo * chore: address refactoring Co-authored-by: fryorcraken.eth <[email protected]>
* Use Logos plugins and theme. * Upgrade dependencies. * feat: improvements on docs (#24) * add: security features * add: protocols overview by example * add: different protocols * add: spell check on CI * rm: yarn.lock to avoid inconsistencies * Update docs/Concepts/1.md Co-authored-by: fryorcraken.eth <[email protected]> * Update docs/Concepts/2.md Co-authored-by: fryorcraken.eth <[email protected]> * Update docs/Concepts/2.md Co-authored-by: fryorcraken.eth <[email protected]> * Update docs/Concepts/7.md Co-authored-by: fryorcraken.eth <[email protected]> * Update docs/Concepts/7.md Co-authored-by: fryorcraken.eth <[email protected]> * convert mscgen sequence to mermaid * partially adress review comments * address: comments * fix: ci * chore: address minor typos/changes in docs * add: pros/cons for discv5 and peer-exchange * fix: minor typo * chore: address refactoring Co-authored-by: fryorcraken.eth <[email protected]> * chore: refactor ordering/naming of markdown files (#29) * chore: rename md files and use config ordering it is unfeasible to track the changes in files labelled as '1.md', '2.md', etc and way easier when the files are named after their contents. * fix: hint box render * fix: markdown links * finish merge * push yarn.lock Co-authored-by: Hossein Mehrabi <[email protected]> Co-authored-by: fryorcraken.eth <[email protected]>
Addresses #15
Followup:
Protocols Overview by Example
to be more readable for the end user