wt: use cdn relay defaults and native setup before overrides

This commit is contained in:
every.channel 2026-02-21 01:34:51 -08:00
parent 0c76f33333
commit 5bce56ee79
No known key found for this signature in database
5 changed files with 20 additions and 10 deletions

View file

@ -8,7 +8,7 @@ Adopt Cloudflare's MoQ relay preview as the default "global" distribution layer
Concrete changes:
1. `ec-node` gains a WebTransport MoQ publisher path that can publish a live CMAF (fMP4) stream to a relay URL (default: `https://interop-relay.cloudflare.mediaoverquic.com/`).
1. `ec-node` gains a WebTransport MoQ publisher path that can publish a live CMAF (fMP4) stream to a relay URL (default: `https://cdn.moq.dev/anon`).
2. `every.channel` (the deployed static site) becomes a real web watcher by embedding a WebTransport-capable MoQ player component (`<hang-watch>`).
3. The existing WebRTC/WS bootstrap directory/relay remains temporarily for compatibility, but is treated as deprecated once MoQ/WebTransport is stable.
@ -41,10 +41,10 @@ Out of scope (explicitly deferred):
### Relay default
Default relay endpoint is:
- `https://interop-relay.cloudflare.mediaoverquic.com/`
- `https://cdn.moq.dev/anon`
Nodes may override via CLI flags for self-hosted relays or future Cloudflare relay endpoints.
As of February 20, 2026, the production relay endpoint (`https://relay.cloudflare.mediaoverquic.com/`) is observed to close sessions immediately after MoQ `SETUP` for current clients, while the interop relay completes `SETUP` and `ANNOUNCE` tests.
As of February 21, 2026, browser sessions against `https://interop-relay.cloudflare.mediaoverquic.com/` are observed to stall/fail during MoQ session establishment with current web clients, while `https://cdn.moq.dev/anon` establishes browser sessions in Chrome.
### Web player