From 6a1103e6bf698dd6ed50b1eadbcc6096a2b0c8cb Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 25 Jun 2026 23:08:10 +0000 Subject: [PATCH 1/7] blog(update-00): add reference links to docs, repo, and IETF drafts --- src/pages/blog/update-00.mdx | 32 ++++++++++++++++---------------- 1 file changed, 16 insertions(+), 16 deletions(-) diff --git a/src/pages/blog/update-00.mdx b/src/pages/blog/update-00.mdx index bfbbfe8..4c30018 100644 --- a/src/pages/blog/update-00.mdx +++ b/src/pages/blog/update-00.mdx @@ -17,7 +17,7 @@ IDK my brain is so fried from talking to Claude all day. ## Hop-based Routing -Now you can connect relays to each other however you desire. +Now you can [connect relays to each other](https://doc.moq.dev/bin/relay/) however you desire. They'll gossip available broadcasts to each other and proxy any subscriptions automatically via the shortest path. For example, I can host a relay in Denver and configure it with: @@ -47,17 +47,17 @@ Your local relay (snug behind a firewall) can proxy all broadcasts to/from a pub moq-relay --cluster-connect https://cdn.moq.dev ... ``` -It'll work with any MoQ CDN that implements enough of the `moq-transport` spec (*cough* not Cloudflare yet *cough*). +It'll work with any MoQ CDN that implements enough of the [`moq-transport`](https://datatracker.ietf.org/doc/draft-ietf-moq-transport/) spec (*cough* not Cloudflare yet *cough*). But you'll need `moq-lite-03+` to establish multiple connections, otherwise a cycle will ruin your day. ## Standards Speaking of standards, the IETF keeps marching forward, so I have to "support" every new draft version lul. **Supported:** -- moq-transport drafts 14-18. -- qmux drafts 00-01 -- msf drafts 00-01 -- loc draft 01 +- [moq-transport](https://datatracker.ietf.org/doc/draft-ietf-moq-transport/) drafts 14-18. +- [qmux](https://datatracker.ietf.org/doc/draft-nandakumar-moq-qmux-moqt/) drafts 00-01 +- [msf](https://datatracker.ietf.org/doc/draft-ietf-moq-msf/) drafts 00-01 +- [loc](https://datatracker.ietf.org/doc/draft-ietf-moq-loc/) draft 01 It takes forever to litigate every single addition/change in the IETF. I'm trying my best [to publish extensions](https://www.ietf.org/archive/id/draft-lcurley-moq-probe-00.html), but it's such a drain on my time. @@ -73,7 +73,7 @@ moq-lite-05 is coming SOON with more stuff. My philosophy is that we should **not** transmit arbitrary media formats over MoQ. It's possible to [transmit TS over MoQ](https://www.ietf.org/archive/id/draft-gregoire-moq-msfts-00.html) verbatim, but then every player/subscriber needs to decode Transport Streams (gross). -Instead, `moq-mux` is our transmuxing layer. +Instead, [`moq-mux`](https://doc.moq.dev/lib/rs/crate/moq-mux.html) is our transmuxing layer. We can import/export other formats without re-encoding, preserving the intent but not the original structure. [Here's the codecs we support](https://github.com/moq-dev/moq/tree/main/rs/moq-mux/src/codec): @@ -100,7 +100,7 @@ Your precious SCTE35 markers are preserved. ur welcome ## CLI -Note that `moq-mux` is available as both a library and a CLI via `moq-cli`. +Note that `moq-mux` is available as both a library and a CLI via [`moq-cli`](https://doc.moq.dev/bin/cli.html). ```bash # Publish: pipe in a MPEG-TS file @@ -150,14 +150,14 @@ It's still Media over QUIC even if QUIC is not used... Claude made the web UI look better. tfw an AI has better taste than me. -Clone the repo and run `just dev` to see: +[Clone the repo](https://doc.moq.dev/setup/) and run `just dev` to see:
![bbb](/blog/update-00/bbb.png)
he a sniffer
-You can use the UI on your own site via the web components: +You can use the UI on your own site via the [web components](https://doc.moq.dev/bin/web.html): ```html