Skip to content

be more specific bout topic ids #19

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.

Sign up for GitHub

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

Merged
okdistribute merged 1 commit into from
Feb 10, 2026
Merged

be more specific bout topic ids #19

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions connecting/gossip.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading