add community page
This commit is contained in:
parent
d12297918f
commit
61e6d92633
|
@ -0,0 +1,21 @@
|
||||||
|
---
|
||||||
|
title: Join Our Community
|
||||||
|
---
|
||||||
|
|
||||||
|
Welcome to the Waku Community! Whether you're interested in building with Waku, contributing to the network, expanding your knowledge, or staying up-to-date with our progress, we have something for everyone.
|
||||||
|
|
||||||
|
## [Discourse](https://forum.vac.dev/)
|
||||||
|
|
||||||
|
Have you got questions, or are you eager to discuss Waku? Head to the [Vac Discourse forum](https://forum.vac.dev/) and join the conversation!
|
||||||
|
|
||||||
|
## [Discord](https://discord.gg/Nrac59MfSX)
|
||||||
|
|
||||||
|
Connect with like-minded individuals in the Waku ecosystem! Introduce yourself, join developer conversations, or seek assistance. Join the [Vac Discord](https://discord.gg/Nrac59MfSX) today!
|
||||||
|
|
||||||
|
## [Twitter](https://twitter.com/waku_org)
|
||||||
|
|
||||||
|
Stay informed and updated with the latest news and insights from Waku. [Follow us on Twitter](https://twitter.com/waku_org) now for all the exciting updates!
|
||||||
|
|
||||||
|
## [Telegram](https://t.me/waku_org)
|
||||||
|
|
||||||
|
Join the [Waku Telegram group](https://t.me/waku_org) now and become part of the thriving community! Stay informed, share ideas, and connect with fellow enthusiasts.
|
|
@ -1,12 +1,12 @@
|
||||||
---
|
---
|
||||||
title: Network Interaction Domains
|
title: Network Domains
|
||||||
---
|
---
|
||||||
|
|
||||||
Waku is a unified and cohesive entity that offers a rich ecosystem with three distinct network interaction domains. These domains serve specialized purposes and contribute to the robust functionality of Waku, forming its foundation.
|
Waku is a unified and cohesive entity that offers a rich ecosystem with three distinct network interaction domains. These domains serve specialized purposes and contribute to the robust functionality of Waku, forming its foundation.
|
||||||
|
|
||||||
## Discovery Domain
|
## Discovery Domain
|
||||||
|
|
||||||
Node discovery in Waku facilitates locating other nodes within the network. As a modular protocol, Waku incorporates various discovery mechanisms, such as [`Discv5`](/overview/concepts/node-discovery#discv5) and [`Peer Exchange`](/overview/concepts/node-discovery#peer-exchange). These mechanisms allow developers to choose the most suitable option(s) for their specific use cases and user environments, including mobile phones, desktop browsers, servers, and more.
|
Peer discovery in Waku facilitates locating other nodes within the network. As a modular protocol, Waku incorporates various discovery mechanisms, such as [`Discv5`](/overview/concepts/peer-discovery#discv5) and [`Peer Exchange`](/overview/concepts/peer-discovery#peer-exchange). These mechanisms allow developers to choose the most suitable option(s) for their specific use cases and user environments, including mobile phones, desktop browsers, servers, and more.
|
||||||
|
|
||||||
## Gossip Domain
|
## Gossip Domain
|
||||||
|
|
||||||
|
|
|
@ -1,10 +1,10 @@
|
||||||
---
|
---
|
||||||
title: Node Discovery Mechanisms
|
title: Peer Discovery
|
||||||
---
|
---
|
||||||
|
|
||||||
When initializing a Waku node, it must connect with other nodes to enable message sending, receiving, and retrieval. To achieve this, a discovery mechanism is employed to locate and connect with other nodes. This process is known as bootstrapping.
|
When initializing a Waku node, it must connect with other peers to enable message sending, receiving, and retrieval. To achieve this, a discovery mechanism is employed to locate and connect with other peers. This process is known as bootstrapping.
|
||||||
|
|
||||||
After establishing a connection, the node must actively seek out additional peers to have:
|
Once a connection is established, the node must actively seek out additional peers to have:
|
||||||
|
|
||||||
- Sufficient peers in the [Relay](/overview/concepts/protocols#relay) mesh: The goal is to have at least 6 peers in the mesh. This ensures a robust network where messages can be efficiently relayed.
|
- Sufficient peers in the [Relay](/overview/concepts/protocols#relay) mesh: The goal is to have at least 6 peers in the mesh. This ensures a robust network where messages can be efficiently relayed.
|
||||||
- Reserve peers for backup: It is essential to have a surplus of peers available as reserves. These reserves are backups when the current peers become overloaded or experience unexpected disconnections.
|
- Reserve peers for backup: It is essential to have a surplus of peers available as reserves. These reserves are backups when the current peers become overloaded or experience unexpected disconnections.
|
|
@ -10,7 +10,7 @@ The `Relay` protocol employs a Pub/Sub architecture to facilitate message routin
|
||||||
|
|
||||||
## [Filter](https://rfc.vac.dev/spec/12/)
|
## [Filter](https://rfc.vac.dev/spec/12/)
|
||||||
|
|
||||||
The `Filter` protocol allows nodes to selectively subscribe to specific messages transmitted by other nodes. It is designed to be a lightweight alternative to the `Relay` protocol, particularly tailored for devices with limited bandwidth.
|
The `Filter` protocol allows light nodes to selectively subscribe to specific messages transmitted by other nodes. It is designed to be a lightweight alternative to the `Relay` protocol, particularly tailored for devices with limited bandwidth.
|
||||||
|
|
||||||
## [Store](https://rfc.vac.dev/spec/13/)
|
## [Store](https://rfc.vac.dev/spec/13/)
|
||||||
|
|
||||||
|
|
|
@ -93,7 +93,7 @@ const config = {
|
||||||
footer: {
|
footer: {
|
||||||
links: [
|
links: [
|
||||||
{
|
{
|
||||||
title: "Waku Clients",
|
title: "Clients",
|
||||||
items: [
|
items: [
|
||||||
{
|
{
|
||||||
to: "/overview/clients",
|
to: "/overview/clients",
|
||||||
|
|
|
@ -16,7 +16,7 @@ const sidebars = {
|
||||||
items: [
|
items: [
|
||||||
"overview/concepts/protocols",
|
"overview/concepts/protocols",
|
||||||
"overview/concepts/network-domains",
|
"overview/concepts/network-domains",
|
||||||
"overview/concepts/node-discovery",
|
"overview/concepts/peer-discovery",
|
||||||
"overview/concepts/content-topics",
|
"overview/concepts/content-topics",
|
||||||
"overview/concepts/transports"
|
"overview/concepts/transports"
|
||||||
]
|
]
|
||||||
|
@ -35,6 +35,9 @@ const sidebars = {
|
||||||
],
|
],
|
||||||
js: [
|
js: [
|
||||||
"clients/js-waku/index"
|
"clients/js-waku/index"
|
||||||
|
],
|
||||||
|
community: [
|
||||||
|
"community"
|
||||||
]
|
]
|
||||||
};
|
};
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue