Skip to content

[codex] move staging site to new domain #108

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

Open
kixelated wants to merge 2 commits into
base: main
Choose a base branch
from
+46 −46
Open

[codex] move staging site to new domain #108

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
acf11fa
move staging site to new domain
kixelated Jun 28, 2026
468afc0
update patch notes
kixelated Jun 28, 2026
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
4 changes: 2 additions & 2 deletions src/layouts/global.astro
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,8 +30,8 @@ const fullDescription = description
: "Media over QUIC is a new live media protocol designed for simplicity and scale. It uses new browser technologies like WebTransport and WebCodecs to deliver media with latency that rivals WebRTC.";
const ogImage = new URL(frontmatter?.cover ?? "/layout/icon.png", siteUrl).toString();

// pro.moq.wtf for staging builds, pro.moq.dev for live (and local dev).
const proUrl = import.meta.env.MODE === "staging" ? "https://pro.moq.wtf" : "https://pro.moq.dev";
// moq.wtf for staging builds, moq.pro for live (and local dev).
const proUrl = import.meta.env.MODE === "staging" ? "https://moq.wtf" : "https://moq.pro";
---

<!doctype html>
Expand Down
86 changes: 43 additions & 43 deletions src/pages/blog/update-00.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
layout: "@/layouts/global.astro"
title: Update 00
author: kixelated
description: Update 00 notes
description: Multiple months of patch notes extrordinaire for your eyeballs.

@sourcery-ai sourcery-ai Bot Jun 28, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nitpick (typo): Typo in description text: "extrordinaire" should be "extraordinaire".

This misspelling will show up in the blog metadata and previews; please correct it to "extraordinaire."

Suggested change
description: Multiple months of patch notes extrordinaire for your eyeballs.
description: Multiple months of patch notes extraordinaire for your eyeballs.

@coderabbitai coderabbitai Bot Jun 28, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Fix typo in frontmatter description.

"extrordinaire" should be "extraordinaire".

📝 Suggested fix 
-description: Multiple months of patch notes extrordinaire for your eyeballs.
+description: Multiple months of patch notes extraordinaire for your eyeballs.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
description: Multiple months of patch notes extrordinaire for your eyeballs.
description: Multiple months of patch notes extraordinaire for your eyeballs.
🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/pages/blog/update-00.mdx` at line 5, The frontmatter description contains
a typo in the blog page metadata. Update the description text in the markdown
frontmatter so that the word “extrordinaire” is corrected to “extraordinaire” in
the update-00 content.

cover: "/blog/update-00/bbb.png"
date: 2026-06-25
---
Expand All @@ -17,12 +17,12 @@ IDK my brain is so fried from talking to Claude all day.


## Hop-based Routing
Now you can [connect relays to each other](https://doc.moq.dev/bin/relay/) however you desire.
Now you can now arbitrarily connect [moq-relay](https://doc.moq.dev/bin/relay/) instances to each other to form a cluster.

@coderabbitai coderabbitai Bot Jun 28, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Remove redundant "now".

"Now you can now" should be "Now you can" or "You can now".

📝 Suggested fix 
-Now you can now arbitrarily connect [moq-relay](https://doc.moq.dev/bin/relay/) instances to each other to form a cluster.
+Now you can arbitrarily connect [moq-relay](https://doc.moq.dev/bin/relay/) instances to each other to form a cluster.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Now you can now arbitrarily connect [moq-relay](https://doc.moq.dev/bin/relay/) instances to each other to form a cluster.
Now you can arbitrarily connect [moq-relay](https://doc.moq.dev/bin/relay/) instances to each other to form a cluster.
🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/pages/blog/update-00.mdx` at line 20, The sentence in the blog post has a
duplicated “now” in the opening phrase. Update the wording in the MDX content so
the lead-in reads either “Now you can” or “You can now” while keeping the rest
of the moq-relay sentence unchanged.

They'll gossip available broadcasts to each other and proxy any subscriptions automatically via the shortest path.
Comment on lines 19 to 21

@sourcery-ai sourcery-ai Bot Jun 28, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nitpick (typo): Redundant wording with "Now you can now" in the routing section.

Please adjust this sentence to remove the duplicated "now" (e.g., "Now you can arbitrarily connect..." or "You can now arbitrarily connect...") for smoother readability.

Suggested change
## Hop-based Routing
Now you can [connect relays to each other](https://doc.moq.dev/bin/relay/) however you desire.
Now you can now arbitrarily connect [moq-relay](https://doc.moq.dev/bin/relay/) instances to each other to form a cluster.
They'll gossip available broadcasts to each other and proxy any subscriptions automatically via the shortest path.
## Hop-based Routing
Now you can arbitrarily connect [moq-relay](https://doc.moq.dev/bin/relay/) instances to each other to form a cluster.
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:
For example, I can host a relay at `https://denver.moq.dev` and configure it with:
```bash
moq-relay --cluster-connect chicago.moq.dev --cluster-connect seattle.moq.dev ...
moq-relay --cluster-connect "https://chicago.moq.dev" --cluster-connect "https://seattle.moq.dev" ...
```

Imagine relays are also configured to connect to their nearest neighbors.
Expand All @@ -44,27 +44,25 @@ Every relay would connect to every other relay, which would have resulted in:\
Oh yeah and
Your local relay (snug behind a firewall) can proxy all broadcasts to/from a public CDN:
```bash
moq-relay --cluster-connect https://cdn.moq.dev ...
moq-relay --cluster-connect "https://cdn.moq.dev" ...
```

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*).
It'll work with any other MoQ CDN... once they implement enough of the [`moq-transport`](https://datatracker.ietf.org/doc/draft-ietf-moq-transport/) spec (Cloudflare pls).
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:**
Speaking of standards, the IETF keeps marching forward, so I have to "support" every new draft version:
- [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
- [qmux](https://datatracker.ietf.org/doc/draft-ietf-quic-qmux/) 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.
We don't support every single feature because some of them are dumb and it takes forever to litigate every single addition/change in the IETF.
I'm starting [to publish extensions](https://www.ietf.org/archive/id/draft-lcurley-moq-probe-00.html) for stuff we add on top, but it's such a drain on my time.

So instead the moq.dev libraries **prefer to negotiate:**
- moq-lite drafts 01-04
- hang drafts 00-01
Instead the moq.dev libraries **prefer to negotiate**:
- [moq-lite](https://datatracker.ietf.org/doc/draft-ietf-moq-lite/) drafts 01-04
- [hang](https://datatracker.ietf.org/doc/draft-ietf-moq-hang/) drafts 00-01

moq-lite-05 is coming SOON with more stuff.

Expand All @@ -89,14 +87,15 @@ We can import/export other formats without re-encoding, preserving the intent bu
- Matroska/WebM
- HLS
- LOC
- TS
- MPEG-TS

Going back to Transport Streams (gross) as an example.
When you import a TS stream with `moq-mux`, we'll split A/V into MoQ tracks, but we'll also preserve "unknown" tracks with a special "ts" section.
If you export the same stream to TS with `moq-mux`, we'll re-assemble the TS stream and reinsert the unknown tracks.

This is a **REALLY BIG DEAL** for broadcast TV.
Your precious SCTE35 markers are preserved.
Your precious SCTE35 markers are preserved AND you're not wasting 5% of your bandwidth on 188-byte packets.

ur welcome

## CLI
Expand All @@ -114,11 +113,12 @@ moq-cli subscribe --url https://cdn.moq.dev/anon --broadcast my-stream --format

You can download all of the moq binaries (`moq-relay`, `moq-token`, etc) from your favorite package manager:
- Homebrew
- .deb/.rpm
- Docker
- Nix
- ???
- winget
- .deb/.rpm

For specific commands, [see the CLI docs](https://doc.moq.dev/bin/cli).
Cool I guess?


Expand All @@ -136,38 +136,38 @@ Each subsequent frame *within the same group* can reuse the previous frames as a
Claude ran a benchmark over a synthetic stream of JSON sensor snapshots.
The type of output you'd expect from a drone.

| Configuration | Bitrate saved |
| ---------------------------------------- | ------------- |
| DEFLATE per frame | 39% |
| JSON Merge Patch | 58% |
| JSON Merge Patch + DEFLATE per frame | 72% |
| DEFLATE per group | 89% |
| **JSON Merge Patch + DEFLATE per group** | **91%** |
Bitrate savings for different configurations:
| | No DEFLATE | DEFLATE per frame | DEFLATE per group |
| ---------------- | ---------- | ----------------- | ----------------- |
| No deltas | 0% | 39% | 89% |
| JSON Merge Patch | 58% | 72% | 91% |


I was surprised to see how important `Z_SYNC_FLUSH` is given it's not supported by the [browser implementation](https://developer.mozilla.org/en-US/docs/Web/API/Compression_Streams_API) and [is bugged](https://github.com/101arrowz/fflate/pull/286) in the most popular Javascript implementation.
Really the main benefit of JSON Merge Patch is to save some CPU cycles.
At this point, the main benefit of JSON Merge Patch is to save some CPU cycles.

## Backends
We've used Quinn for the longest time, but now you can use other QUIC backends!
Why? IDK different features and performance.

QUIC Backends (WebTransport + raw QUIC):
- quinn
- noq
- quiche (Cloudflare)
- iroh (p2p)
QUIC Backends (both WebTransport + raw QUIC):
- [quinn](https://github.com/quinn-rs/quinn)
- [noq](https://github.com/n0-computer/noq)
- [quiche](https://github.com/cloudflare/quiche) (Cloudflare)
- [iroh](https://github.com/n0-computer/iroh) (peer-to-peer)
- [WASM](https://github.com/moq-dev/web-transport/tree/main/rs/web-transport-wasm)

You can also use non-QUIC backends with Qmux!
You can also use non-QUIC backends with [Qmux](https://datatracker.ietf.org/doc/draft-ietf-quic-qmux/)!
It emulates a QUIC connection, but over a reliable transport.
We do suffer more from head-of-line blocking but sometimes it be like that.
We do suffer more from head-of-line blocking so it's worse than QUIC, but sometimes it be like that.

Non-QUIC Backends (Qmux):
- WebSocket
- WebSockets
- TLS
- TCP
- Unix domain sockets

For example, I'm using unix domain sockets (or TCP) to run localhost workers without paying the TLS/UDP overhead tax.
I'm using WebSockets as a TCP fallback (when QUIC is not available) and unix domain sockets to avoid paying the TLS/UDP overhead tax on localhost.
It's still Media over QUIC even if QUIC is not used...


Expand Down Expand Up @@ -203,8 +203,8 @@ We full [monorepo](https://github.com/moq-dev/moq) now.

`moq-ffi` uses Uniffi to generate async bindings for various languages.
It's all the same Rust code under the hood, but IDK now you can use it on iOS/Android/whatever.

[MoQKit](https://fishjam.swmansion.com/blog/moq-boy-escaped-the-browser) uses it.

neat

Supported:
Expand All @@ -223,13 +223,13 @@ Oh and don't worry, we still have [C support](https://doc.moq.dev/lib/c/) via [`
I'm almost done spinning up a PAID MoQ CDN.
It's like a week or two away, **GET HYPED**.

As part of that, I actually have to make sure everything is production-ready, which means focusing on the boring stuff like:
- `mTLS`: relays can authorize via client certificates
- `TLS`: cert reloading and custom root CAs
As part of that, I actually have to make sure everything is production-ready, which means focusing on the boring stuff.
Stuff like making static configurations... dynamic.

And more of the static configuration is now possible via a REST API.
- `--auth-api`: authorize a user
- `--cluster-connect-api`: discover neighboring relay nodes
- `mTLS`: relays can authorize via client certificates
- `TLS`: cert reloading
- `--auth-api`: authorize a user via an API
- `--cluster-connect-api`: discover neighboring relay nodes via an API

And finally my favorite one, but it deserves its own blog post later:
- `.stats`: deliver MoQ metrics over MoQ
Expand Down
2 changes: 1 addition & 1 deletion wrangler.jsonc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@
"staging": {
"name": "moq-dev-staging",
"route": {
"pattern": "moq.wtf",
"pattern": "new.moq.dev",
"custom_domain": true
}
},
Expand Down
Loading