<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>BlogGeek.me</title>
  <atom:link href="https://bloggeek.me/feed.xml" rel="self" type="application/rss+xml" />
  <link>https://bloggeek.me/</link>
  <description>The leading authority on WebRTC</description>
  <language>en-US</language>
  <lastBuildDate>Thu, 06 Aug 2026 13:30:00 GMT</lastBuildDate>
  <item>
    <title>Twilio SIGNAL 2026: the pivot from CPaaS to conversation infrastructure</title>
    <link>https://bloggeek.me/twilio-signal-2026/</link>
    <guid isPermaLink="true">https://bloggeek.me/twilio-signal-2026/</guid>
    <pubDate>Thu, 06 Aug 2026 13:30:00 GMT</pubDate>
    <dc:creator><![CDATA[Tsahi Levent-Levi]]></dc:creator>
    <description><![CDATA[Twilio SIGNAL 2026 was not a new channel. It was a repositioning: the Conversation Layer, what it means for WebRTC, and the lock-in nobody named on stage.]]></description>
  </item>
  <item>
    <title>WebRTC won't fix your call quality. Observability will</title>
    <link>https://bloggeek.me/webrtc-fix-quality-observability/</link>
    <guid isPermaLink="true">https://bloggeek.me/webrtc-fix-quality-observability/</guid>
    <pubDate>Mon, 03 Aug 2026 13:30:00 GMT</pubDate>
    <dc:creator><![CDATA[Tsahi Levent-Levi]]></dc:creator>
    <description><![CDATA[Switching WebRTC stacks won't fix call quality you can't see. Why observability, not your transport, decides how your calls actually perform.]]></description>
  </item>
  <item>
    <title>The vendor you're about to bet on can't see the market. Neither can you</title>
    <link>https://bloggeek.me/video-api-vendor-blind-spot/</link>
    <guid isPermaLink="true">https://bloggeek.me/video-api-vendor-blind-spot/</guid>
    <pubDate>Tue, 21 Jul 2026 18:35:02 GMT</pubDate>
    <dc:creator><![CDATA[Tsahi Levent-Levi]]></dc:creator>
    <description><![CDATA[Every vendor sees only the deals that reach them. The 2026 Video API Report maps the market no insider can see and no buyer has time to build.]]></description>
  </item>
  <item>
    <title>What getting rtcStats seen taught me about the whole WebRTC ecosystem</title>
    <link>https://bloggeek.me/rtcstats-seen-taught-webrtc-ecosystem/</link>
    <guid isPermaLink="true">https://bloggeek.me/rtcstats-seen-taught-webrtc-ecosystem/</guid>
    <pubDate>Mon, 06 Jul 2026 13:30:00 GMT</pubDate>
    <dc:creator><![CDATA[Tsahi Levent-Levi]]></dc:creator>
    <description><![CDATA[I set out to get one tool seen and ended up mapping the whole WebRTC tools ecosystem, scored by how AI actually sees it.]]></description>
  </item>
  <item>
    <title>The Real Cost of Real-Time: What Your WebRTC Bill Actually Looks Like</title>
    <link>https://bloggeek.me/video-api-pricing-models/</link>
    <guid isPermaLink="true">https://bloggeek.me/video-api-pricing-models/</guid>
    <pubDate>Mon, 08 Jun 2026 12:30:00 GMT</pubDate>
    <dc:creator><![CDATA[Tsahi Levent-Levi]]></dc:creator>
    <description><![CDATA[Most buyers pick a Video API vendor on features. The pricing model is what they get stuck with.]]></description>
  </item>
  <item>
    <title>Chrome moves to a 2 week release cycle. Where are you with your WebRTC app</title>
    <link>https://bloggeek.me/chrome-2-week-release-cycle-webrtc/</link>
    <guid isPermaLink="true">https://bloggeek.me/chrome-2-week-release-cycle-webrtc/</guid>
    <pubDate>Mon, 25 May 2026 00:30:00 GMT</pubDate>
    <dc:creator><![CDATA[Tsahi Levent-Levi]]></dc:creator>
    <description><![CDATA[]]></description>
  </item>
  <item>
    <title>MOQ is lacking a compelling adoption reason</title>
    <link>https://bloggeek.me/moq-adoption-problem/</link>
    <guid isPermaLink="true">https://bloggeek.me/moq-adoption-problem/</guid>
    <pubDate>Mon, 11 May 2026 12:30:00 GMT</pubDate>
    <dc:creator><![CDATA[Tsahi Levent-Levi]]></dc:creator>
    <description><![CDATA[]]></description>
  </item>
  <item>
    <title>WebRTC Monitoring: Are You Monitoring Your Servers or Your Service?</title>
    <link>https://bloggeek.me/webrtc-monitoring-server-or-service/</link>
    <guid isPermaLink="true">https://bloggeek.me/webrtc-monitoring-server-or-service/</guid>
    <pubDate>Mon, 27 Apr 2026 12:30:00 GMT</pubDate>
    <dc:creator><![CDATA[Tsahi Levent-Levi]]></dc:creator>
    <description><![CDATA[Most WebRTC teams monitor servers, not service quality. Learn why client-side WebRTC monitoring catches problems server dashboards miss - and how to start.]]></description>
  </item>
  <item>
    <title>Memory prices, WebRTC and the future of Voice AI</title>
    <link>https://bloggeek.me/memory-prices-webrtc-voice-ai/</link>
    <guid isPermaLink="true">https://bloggeek.me/memory-prices-webrtc-voice-ai/</guid>
    <pubDate>Mon, 13 Apr 2026 12:30:00 GMT</pubDate>
    <dc:creator><![CDATA[Tsahi Levent-Levi]]></dc:creator>
    <description><![CDATA[A quiet crisis is underway: AI is gobbling up all the world's memory, pushing prices up 6X and forcing WebRTC and Voice AI to rethink how they operate.]]></description>
  </item>
  <item>
    <title>Voice AI best practices, based on rtcStats data</title>
    <link>https://bloggeek.me/voice-ai-best-practices/</link>
    <guid isPermaLink="true">https://bloggeek.me/voice-ai-best-practices/</guid>
    <pubDate>Mon, 30 Mar 2026 12:30:00 GMT</pubDate>
    <dc:creator><![CDATA[Tsahi Levent-Levi]]></dc:creator>
    <description><![CDATA[WebRTC is the backbone of Voice AI, yet our analysis reveals that not all voice bot implementations are created equal; read on to learn the essential best practices for echo cancellation, Opus bitrates, and network configuration to ensure your bot works for everyone.]]></description>
  </item>
</channel>
</rss>
