March 18, 2026

Kraken, not lag, on the starboard

(Media over QUIC) on a Boat

Boat cams, kraken alerts, and a comment war over who’s steering the stream

TLDR: MoQ’s boat demo shows video that sends only what viewers request, prioritizing the most important feeds to save bandwidth. Commenters split between “this is just what WebRTC can already do” and “finally, a simpler way to pick tracks and scale,” with memes and kraken jokes keeping the vibes buoyant

A cheeky post on using Media over QUIC (aka MoQ) to stream from a boat—only sending the video you actually ask for—hit the dock, and the comments went full regatta. Fans loved the idea of “subscribe only to what you need” and giving the “kraken cam” top priority, while skeptics asked if this is really new or just a shiny remake of old tricks.

The loudest horn blast? One builder claimed, “pull-based works with WebRTC too,” arguing you can already stop streams when they’re off-screen and resubscribe later. That sparked a mini–turf war: is MoQ a revolution, or just better organized with global relays and cleaner track choices? Meanwhile, a curious commenter dove into the weeds asking if lower-priority video sits in memory and gets sent later, and how forward‑error‑correction fits in—translation: even boat tech gets nerdy fast.

Of course, the internet did its internet thing. Someone blasted I’m On A Boat, kraken jokes flew, and another user swooned, “there’s still a place for good writing.” One dreamer imagined a one‑stop app where you pull only the pieces you want—video, audio, captions—across everything you watch. Love it or doubt it, the vibe is clear: send less, choose more, and make the important bits sail through first. Ahoy, bandwidth

Key Points

  • MoQ is presented as a primarily pull-based media transport, contrasting with push-based protocols like WebRTC, SRT, RTSP, and RTMP.
  • MoQ splits broadcasts into application-defined tracks, and only explicitly subscribed tracks are transmitted, saving bandwidth.
  • Moq-relay merges identical downstream subscriptions into a single upstream request and can be clustered for CDN-like global scaling.
  • Subscriptions include priorities; QUIC uses these to deliver higher-priority streams first under congestion, with best-effort dropping of lower-priority data.
  • An AI-driven workflow can subscribe to low-res streams by default and dynamically add high-res tracks when needed, optimizing bandwidth on constrained links (e.g., boats with satellite).

Hottest takes

"Pull-based streaming can work with webrtc" — dmm
"I am a bit confused, so.. it’s sent delayed later or is it only added in non-priority stream? Also slightly far from that, how does that work with FEC?" — tamimio
"The Lonely Island - I'm On A Boat" — teekert
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.