The date of the 2026 edition of your favorite multimedia conference is here!

Mark your calendars, gather a friend group and start planning your trip to Kraków – RTC.ON is coming back Sept 16-18, 2026 🎉

Coming next: RTC.ON 2026 Early Bird ticket sale! As per usual, the newsletter subscribers will be the first one to know once it's .ON. Stay tuned!

AGILE SOFTWARE DEVELOPMENT | Link

Google Meet Reactions

While Google Meet reactions are a standard feature, the underlying implementation is a complex orchestration of WebRTC DataChannels and Protocol Buffers. Frustrated by the platform's emoji search functionality, the author embarked on a technical deep dive to intercept and reverse engineer the binary signaling messages used to sync state across participants. They detail a method that spoofs incoming data packets, tricking the local UI handlers into triggering reactions. It is a great read for those interested in Google Meet's internals.

MARTIN GARCIA | Link

Webrtc Serverless signaling via QR codes

Ever wondered if you could establish a WebRTC connection without any signaling server whatsoever? Martin shares his unconventional approach at essentially hacking SDP and QR codes to allow squeezing the WebRTC negotiation into QR-compatible data size. By stripping SDP payloads down from kilobytes to just 55 bytes, he’s created a "serverless air-drop" that is just the thing you want for low-latency data transfer without the infra overhead.

MOQ DEV | Link

MoQ community growing strong

In his latest post, Luke (kixelated) reflects on the momentum that is building up for Media over QUIC. While he has been the lone voice for MoQ for some time, that time is definitely gone. He’s telling about an increasing group of engineers and companies taking part and contributing to this municipal effort.

PION BLOG | Link

Pion SCTP advancement

Pion just modernized how their SCTP implementation handles packet loss by adopting RACK-TLP loss detection algorithm, that’s been originally designed for TCP in the RFC 8985. It’s a technical win that improves the throughput and grants lower latency for WebRTC Data Channels.

BLOGGEEKME | Link

When the Network is Fine, but the CPU Says No

Tsahi at bloggeek.me gives us a friendly reminder that while we might all be obsessed with fixing or overcoming network deficiencies, CPU may be the "silent killer" of call quality. Since browsers won’t give you a direct CPU percentage for privacy reasons, this post is a primer on how to use metrics like encode time and the qualityLimitationReason stat to indirectly figure out if a user's laptop is actually the bottleneck. There’s also a TL;DR video explainer link in the article.

Picture a lively dinner party: glasses clinking, half-finished sentences, and three people laughing at the same time. To a human, navigating this is instinctual. To an AI, it is a nightmare. We have effectively mastered the predictable flow of a one-on-one chat. But handling a group conversation, where people interrupt and talk over each other, is much more difficult.

Together with the Fishjam team, we set out to showcase our Selective Forwarding Unit solution by building a unique demo app that solves this problem. That’s how the Deep Sea Stories game came to life.

We hope you enjoy the RTC.ON newsletter as much as we do. It's great to see all of you joining us each month for a little multimedia walk through – thanks!

Here are some more ways to connect with us:

Want to share RTC.ON newsletter with a friend? Here is a link to our sign up page, including the archive of all past issues.