1. MOQ brought something to show.
DEMOQED / 8 OCT / SF · Ingest · Relays · Robotics
The programme connects live ingest, relay scaling and new applications.
DEMOQED’s October 8 programme at San Francisco’s Alamo Drafthouse included Meta on Instagram and Facebook Live ingest, OpenMOQ relay scaling, Evolve Robotics, and Daily benchmarking MOQ against HLS. The programme identifies concrete applications and teams to follow; talk titles do not establish deployment scale or benchmark results.
Source section: https://blog.rvnd.me/moqmusings/2026-10-05-moq-showed-its-work#demoqed
Primary sources: https://moqalliance.org/demoqed-2026/

2. One deadline. No fresh excuse.
Timestamp + timeout · First object · Later objects
Individual -00 proposals; relative lateness, not capture-to-screen delivery.
Two individual -00 Internet-Drafts propose timestamp properties and end-to-end delivery-timeout accounting across a relay chain. The first forwarded object establishes a reference timeline; later objects can expire when they fall too far behind. This does not bound startup delay or guarantee capture-to-screen delivery, and it is not adopted core MOQT behaviour.
Source section: https://blog.rvnd.me/moqmusings/2026-10-05-moq-showed-its-work#deadlines-and-allowances
Primary sources: https://datatracker.ietf.org/doc/draft-frindell-moq-timestamp/00/ https://datatracker.ietf.org/doc/draft-sharma-moq-end-to-end-delivery-timeout/00/

3. The relay gets a service.
OpenMOQ moqx v0.3.6 · Newest group retained · Retry / CPU fixes
Released October 10; draft-14 support removed. Check configuration.
OpenMOQ moqx v0.3.6, released October 10, retains the newest group of a live track under cache byte pressure, fixes reconnection after an upstream failure during handshake, and addresses a cache thread consuming 100% CPU and concurrency crashes. These are implementation reliability fixes, not universal MOQ production readiness. Draft-14 support is removed: configurations that still list version 14 fail startup. This is not a draft-22 compatibility announcement.
Source section: https://blog.rvnd.me/moqmusings/2026-10-05-moq-showed-its-work#relay-maintenance
Primary sources: https://github.com/openmoq/moqx/releases/tag/v0.3.6 https://github.com/openmoq/moqx/pull/739 https://github.com/openmoq/moqx/pull/737

4. Give your mic a room.
VoiceBlender · Mic · Mixer · Room audio · SIP / WebRTC
Existing draft-11 experiment; use its matching local setup. Not ready for production.
VoiceBlender’s existing browser example sends microphone audio as Opus over MOQ to a mixer and receives the room mix back. Its broader system also supports SIP and WebRTC audio legs. This is an experimental draft-11 proof of concept: follow the matching local server/client guide and add another participant or the documented WAV source. It is not a production-ready MOQ path or a claim of draft-22 interoperability. The telephone illustration is a metaphor for voice-system integration, not a tested call.
Source section: https://blog.rvnd.me/moqmusings/2026-10-05-moq-showed-its-work#built-with-moq
Primary sources: https://github.com/VoiceBlender/voiceblender/tree/master/examples/moq-web https://github.com/VoiceBlender/voiceblender/blob/master/CONFIGURATION.md