From 72f8eb30f7d5e2f896080bf64786fa1e44591576 Mon Sep 17 00:00:00 2001 From: DontBlameMe Date: Thu, 19 Nov 2026 22:36:32 +0100 Subject: [PATCH 1/4] docs: make selvaged optional and point to host-run relay Rooms no longer need a deployed server. Host clients run the relay role for their own room. selvaged stays as the conformance server and an optional standalone relay. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index bd25a5d..0afa76c 100644 --- a/README.md +++ b/README.md @@ -3,7 +3,7 @@ A Rust workspace for the Selvage Session Protocol. `selvaged` is a memory-only reference server that seats peers in a room and relays sealed frames it cannot read; the client library the protocol is proved with lives beside it. This -repository is the protocol's reference implementation. +repository is the protocol's reference implementation. Rooms do not need this process: a host client runs the same relay role for its own room. `selvaged` is kept as the conformance server the wire vectors replay against and as an optional standalone relay for testing. See the specification's `docs/peer-host-relay.md`; guests reach a host-run relay over Tailscale or a LAN. ## Get it working From ea42a92898fc14eb60ef57f763ace69a211555ad Mon Sep 17 00:00:00 2001 From: DontBlameMe Date: Thu, 19 Nov 2026 22:44:06 +0100 Subject: [PATCH 2/4] docs: link the host-run relay guide Name the specification repository so readers can find the guide. Keep the document path visible as its location. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 0afa76c..e660f5d 100644 --- a/README.md +++ b/README.md @@ -3,7 +3,7 @@ A Rust workspace for the Selvage Session Protocol. `selvaged` is a memory-only reference server that seats peers in a room and relays sealed frames it cannot read; the client library the protocol is proved with lives beside it. This -repository is the protocol's reference implementation. Rooms do not need this process: a host client runs the same relay role for its own room. `selvaged` is kept as the conformance server the wire vectors replay against and as an optional standalone relay for testing. See the specification's `docs/peer-host-relay.md`; guests reach a host-run relay over Tailscale or a LAN. +repository is the protocol's reference implementation. Rooms do not need this process: a host client runs the same relay role for its own room. `selvaged` is kept as the conformance server the wire vectors replay against and as an optional standalone relay for testing. See the [specification](https://github.com/selvage-protocol/specification)'s `docs/peer-host-relay.md`; guests reach a host-run relay over Tailscale or a LAN. ## Get it working From c0b6a6f717b34d6602dd00917393f1046f113df1 Mon Sep 17 00:00:00 2001 From: DontBlameMe Date: Thu, 19 Nov 2026 23:11:57 +0100 Subject: [PATCH 3/4] docs: qualify the host-run relay statement The editor clients documented in docs/rooms.md still start selvaged. A host-run relay is a property of the client that hosts. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index e660f5d..e4e9644 100644 --- a/README.md +++ b/README.md @@ -3,7 +3,7 @@ A Rust workspace for the Selvage Session Protocol. `selvaged` is a memory-only reference server that seats peers in a room and relays sealed frames it cannot read; the client library the protocol is proved with lives beside it. This -repository is the protocol's reference implementation. Rooms do not need this process: a host client runs the same relay role for its own room. `selvaged` is kept as the conformance server the wire vectors replay against and as an optional standalone relay for testing. See the [specification](https://github.com/selvage-protocol/specification)'s `docs/peer-host-relay.md`; guests reach a host-run relay over Tailscale or a LAN. +repository is the protocol's reference implementation. A client with a host-run relay does not need this process for its own room. The editor clients documented in `docs/rooms.md` still start `selvaged` and need its address. `selvaged` is kept as the conformance server the wire vectors replay against and as an optional standalone relay for testing. See the [specification](https://github.com/selvage-protocol/specification)'s `docs/peer-host-relay.md`; guests reach a host-run relay over Tailscale or a LAN. ## Get it working From 65049c5da1fa4c4bc1a702988d7fc614f465e2ed Mon Sep 17 00:00:00 2001 From: DontBlameMe Date: Thu, 19 Nov 2026 23:25:36 +0100 Subject: [PATCH 4/4] docs: say the host starts selvaged The editor clients are given a server address. The host starts selvaged separately or joins an existing server. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index e4e9644..fd7c468 100644 --- a/README.md +++ b/README.md @@ -3,7 +3,7 @@ A Rust workspace for the Selvage Session Protocol. `selvaged` is a memory-only reference server that seats peers in a room and relays sealed frames it cannot read; the client library the protocol is proved with lives beside it. This -repository is the protocol's reference implementation. A client with a host-run relay does not need this process for its own room. The editor clients documented in `docs/rooms.md` still start `selvaged` and need its address. `selvaged` is kept as the conformance server the wire vectors replay against and as an optional standalone relay for testing. See the [specification](https://github.com/selvage-protocol/specification)'s `docs/peer-host-relay.md`; guests reach a host-run relay over Tailscale or a LAN. +repository is the protocol's reference implementation. A client with a host-run relay does not need this process for its own room. With the editor clients documented in `docs/rooms.md`, the host starts `selvaged` separately or joins an existing server, then gives the editor its address. `selvaged` is kept as the conformance server the wire vectors replay against and as an optional standalone relay for testing. See the [specification](https://github.com/selvage-protocol/specification)'s `docs/peer-host-relay.md`; guests reach a host-run relay over Tailscale or a LAN. ## Get it working