~/lambiengcode blog/
>~ls blog/
rt

real-time media, curated

A scheduled pipeline pulls new posts from WebRTC and Media-over-QUIC sources, summarizes each with an LLM, and publishes it here — every entry links back to the original.

The annual ClueCon conference founded by the creators of FreeSWITCH has always been where the real-time communications community gathers to share what’s working, what’s breaking, and what’s next. This year’s edition, August 10-14 at The Midland Hotel in Chicago, made one thing un

Robots, policies, operators, and recorders as independent participants in one realtime session: five multi-participant architectures we have helped customers build on LiveKit.

The moq.dev project has moved from a side effort to a funded, full-time push on Media over QUIC — kixelated is now building it as a business, not just a spec implementation.

#moq#quic

We built a self-hosted video calling system for a healthcare platform client, replacing the usual “meeting link” pattern with a real phone-call flow: clinician dials, patient’s phone rings, patient answers. Highlights: Read the full WebRTC.ventures Story of Success: Self-Hosted J

STUNner is a Kubernetes-native TURN server, TURN being the relay protocol that gives WebRTC clients a public endpoint to send media through. It builds on the Gateway API to terminate TURN at a single load balancer endpoint and relay media to the pod behind it, so media-server […]

Swapping WebRTC stacks doesn't fix call quality you can't measure — the argument for treating observability, not the transport layer, as the real lever on perceived quality.

#webrtc#observability

Voice AI tooling broadly falls into two categories: managed platforms that get you a production agent fast, and custom-built frameworks that give you full ownership of your voice pipeline. Within each category, the specific tools differ in ways that are worth understanding before

tl;dr: Opus encoding just got 20% faster on desktop Chromium by turning on AVX2 vectorization in libopus. Vectorization means one instruction doing the same arithmetic on a whole vector of values at once instead of one at a time. Codecs spend their hot loops running identical mat

Vibe-coding WebRTC

webrtcHacks

Well, that title is clickbait for Hacker News. The honest title would have been “using AI to tackle long-standing WebRTC issues.” Posts on webrtcHacks are rare these days, and in German we would say there are Unkenrufe that WebRTC is dead. It is not. It is the infrastructure for

MoqBoy

moq.dev

Using MoQ for REAL-TIME BIDIRECTIONAL STREAMING. Gameboy games!

First class support for MoQ in OBS... via a fork. Go forth and integrate libmoq into all of your favorite tools still using C for some reason.

Do you need to use MoQ? What are we even doing with our lives?

It turns out there's actually a bunch of people behind MoQ not named `kixelated`

A level-headed breakdown of when WebRTC's sub-second interactivity still wins and when MoQ's CDN-friendly, QUIC-native fan-out is the better fit — not a 'MoQ replaces WebRTC' piece.

#moq#webrtc#architecture

It is time for another edition of “Is everyone switching to…“. Cloudflare recently published a blog post about Media over Quic (MoQ) which made a number of statements about WebRTC that require some “clarification”. Let us start with that and look at MoQ and WebTransport after tha

Earlier this month, OpenAI released the GA version of its realtime API. This includes many capabilities that the Beta didn’t have, including video support. I started out doing an update to the The Unofficial Guide to OpenAI’s Realtime WebRTC API I made for the Beta release last N

Audio jitter buffers are required 101 introductory material for understanding VoIP. libWebRTC’s audio jitter buffer implementation – the one in Chromium – is known as NetEQ. NetEQ is anything but basic. This is good from a user perspective since real-life networks conditions are

OpenAI is utilizing WebRTC for its Realtime API! Even better, webrtcHacks friend and Pion founder Sean DuBois helped to develop it and agreed to a Q&A about the implementation. It is not often a massive WebRTC use case like this emerges so rapidly. In addition, Sean was extremely