Repository navigation
Switch default signaling to reachable public relays - #10
Merged
Merged
Conversation
Contributor
Author
|
Merged. The new default relays are verified locally (two isolated Chrome contexts showed 2 in room and synced edits both ways), but write.subscript.to serves a prebuilt embed bundle that still has Manual verification
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Root cause
Write's default signaling relay,
wss://y-webrtc-eu.fly.dev, is offline (hostname resolves, connections time out). The hosted embed on write.subscript.to sets nosignaling-url, so browsers opening a Share Draft link never find each other.Change
Per the instruction on #7 ("find another public signaling server"), I probed public y-webrtc relays with a live two-client
subscribe/publishrelay test (2026-10-03):wss://y-webrtc-signaling.fly.devwss://y-webrtc.fly.devwss://y-webrtc-eu.fly.dev(old default)wss://signaling.yjs.dev,y-webrtc-signaling-{eu,us}.herokuapp.com,y-webrtc-signaling-{eu,us}.fly.dev,y-webrtc-us.fly.devapp/src/lib/config.ts: defaultsignalingUrlis nowwss://y-webrtc-signaling.fly.dev,wss://y-webrtc.fly.dev. Write already accepts a comma-separated list and y-webrtc connects to every relay concurrently, so either one being down doesn't break sharing.signalingUrls()helper so it can be tested.app/.env.example,signaling/README.md, and the root README no longer describewss://y-webrtc-eu.fly.dev; they document the new defaults (the root README's config table previously listed the wrong default too).signaling/README.mdnow notes these are community relays with no uptime guarantee.User impact
Share Draft links connect peers again without any self-hosted signaling. The hosted write.subscript.to page picks this up once it's rebuilt with this version of the embed bundle (it currently bakes in the old default).
Tests
app/src/lib/config.test.ts: default relays, old relay absent, comma-separated override parsing.pnpm run lintandpnpm run test(16 files, 47 tests) pass locally.pnpm devwith no.env.local(so only the new defaults), opened/#room=<random>in two isolated headless Chrome contexts. Both showed 2 in room, and edits synced A→B and B→A.Changelog
No changelog entry: the project has no changelog.
Screenshots
Not applicable: no UI code changed.
Closes #7
Agents: claude-code (claude-opus-5-5)