diff --git a/docs/guides/js-waku/index.md b/docs/guides/js-waku/index.md index 4a4d652..ea0fc57 100644 --- a/docs/guides/js-waku/index.md +++ b/docs/guides/js-waku/index.md @@ -88,6 +88,7 @@ Have a look at the quick start guide and comprehensive tutorials to learn how to | [Bootstrap Nodes and Discover Peers](/guides/js-waku/configure-discovery) | Learn how to bootstrap your node using [Static Peers](/overview/concepts/static-peers) and discover peers using [DNS Discovery](/overview/concepts/dns-discovery) | | [Run @waku/sdk in a NodeJS Application](/guides/js-waku/run-waku-nodejs) | Learn our suggested approach for using the `@waku/sdk` package within a NodeJS application | | [How to Debug Your Waku DApp and WebSocket](/guides/js-waku/debug-waku-dapp) | Learn how to troubleshoot your Waku DApp using debug logs and check [WebSocket](/overview/concepts/transports) connections in [nwaku](/guides/run-nwaku-node) | +| [Manage Your Filter Subscription](/guides/js-waku/manage-filter) | Learn how to manage [filter subscriptions](/overview/concepts/protocols#filter) and handle node disconnections in your application | :::tip Until [node incentivisation](/overview/reference/research-in-progress#prevention-of-denial-of-service-dos-and-node-incentivisation) is in place, you should [operate extra nodes](/guides/nodes-and-sdks#run-a-waku-node) alongside the ones provided by the Waku Network. When running a node, we recommend using the [DNS Discovery and Static Peers](/guides/js-waku/configure-discovery#configure-dns-discovery-and-static-peers) configuration to connect to both the Waku Network and your node. diff --git a/docs/guides/js-waku/manage-filter.md b/docs/guides/js-waku/manage-filter.md new file mode 100644 index 0000000..211fede --- /dev/null +++ b/docs/guides/js-waku/manage-filter.md @@ -0,0 +1,5 @@ +--- +title: Manage Your Filter Subscription +--- + +This guide provides detailed steps to manage [filter subscriptions](/overview/concepts/protocols#filter) and handle node disconnections in your application. Have a look at the [Filter guide](/guides/js-waku/light-send-receive) for receiving messages with the `Filter protocol`. \ No newline at end of file diff --git a/docs/guides/nwaku/configure-nwaku.md b/docs/guides/nwaku/configure-nwaku.md index 1a5635d..30aae3b 100644 --- a/docs/guides/nwaku/configure-nwaku.md +++ b/docs/guides/nwaku/configure-nwaku.md @@ -242,7 +242,7 @@ For example, consider a `nwaku` node that requests lightpush of published messag ./build/wakunode2 --lightpushnode=/dns4/node-01.ac-cn-hongkong-c.wakuv2.prod.statusim.net/tcp/30303/p2p/16Uiu2HAm4v86W3bmT1BiH6oSPzcsSr24iDQpSN5Qa992BCjjwgrD ``` -## Run a Node Behind a Reverse Proxy +## Run Nwaku Behind a Reverse Proxy When using a reverse proxy server for SSL/TLS encryption, you only want to announce the proxy server's IP or domain. Nwaku provides the `ext-multiaddr-only` and `ext-multiaddr` options for specifying published multiaddr: diff --git a/sidebars.js b/sidebars.js index c806cbe..118fea1 100644 --- a/sidebars.js +++ b/sidebars.js @@ -78,6 +78,7 @@ const sidebars = { "guides/js-waku/configure-discovery", "guides/js-waku/run-waku-nodejs", "guides/js-waku/debug-waku-dapp", + "guides/js-waku/manage-filter", { type: 'html', value: '@waku/sdk Examples',