From 1c21f3d53d268564e932a1b06ae5ef59795aade2 Mon Sep 17 00:00:00 2001
From: Rae McKelvey <633012+okdistribute@users.noreply.github.com>
Date: Mon, 9 Feb 2026 16:50:10 -0800
Subject: [PATCH] be more specific bout topic ids

---
 connecting/gossip.mdx | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/connecting/gossip.mdx b/connecting/gossip.mdx
index 7ff7dd2..dc0be9e 100644
--- a/connecting/gossip.mdx
+++ b/connecting/gossip.mdx
@@ -35,6 +35,15 @@ application. Similar to a router in webserver library, it runs a loop accepting
 incoming connections and routes them to the specific protocol handler, based on
 ALPN.
 
+### Structuing your application
+
+Every gossip network should have a `TopicID`. This `TopicId` should be a string
+shared between all endpoints that want to take part in the broadcast group.
+
+There are different ways to structure your application around topics, depending on your use case:
+- **One topic for all peers** – Use a single topic ID when everyone should receive all messages. Scales to a few thousand peers.
+- **Scoped topics** – Use separate topic IDs (or hashes derived from them) for distinct groups, spaces, or documents.
+
 ### Example
 
 ```rust