1. MOQ brought something to show.
A nervously proud Packet presents a camera filming a small flower on a low stage. Separate labels connect DEMOQED with ingest, relays and robotics; the image illustrates the programme’s application focus without depicting an actual conference demonstration.
The programme connects live ingest, relay scaling and new applications.
Source: https://blog.rvnd.me/moqmusings/2026-10-05-moq-showed-its-work#demoqed

2. One deadline. No fresh excuse.
A determined Packet carries one running hourglass past checkpoint posts without turning it over. A separately drawn first-object-to-later-objects timeline represents the shared reference for relative lateness; the visible qualification identifies individual proposals rather than a delivery guarantee.
Individual -00 proposals; relative lateness, not capture-to-screen delivery.
Source: https://blog.rvnd.me/moqmusings/2026-10-05-moq-showed-its-work#deadlines-and-allowances

3. The relay gets a service.
A relieved Packet oils a relay machine and replaces a misplaced data block inside its open compartment. Separate labels identify retaining the newest cached group and retry/CPU fixes. The card explicitly flags removal of draft-14 support.
Released October 10; draft-14 support removed. Check configuration.
Source: https://blog.rvnd.me/moqmusings/2026-10-05-moq-showed-its-work#relay-maintenance

4. Give your mic a room.
A curious Packet plugs a cable into an audio switchboard while holding a telephone receiver, with a microphone on the desk. A separate mic-to-mixer-to-room-audio diagram explains the browser audio path. SIP/WebRTC labels describe the broader mixer, while the visible text preserves the experiment’s draft-11 and non-production status.
Existing draft-11 experiment; use its matching local setup. Not ready for production.
Source: https://blog.rvnd.me/moqmusings/2026-10-05-moq-showed-its-work#built-with-moq
