<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Hugo Lavernhe</title>
    <link>https://hugolavernhe.com/</link>
    <description>Recent content on Hugo Lavernhe</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 28 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://hugolavernhe.com/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Debugging a Go Call-Transcriber on Jitsi&#39;s Video Bridge</title>
      <link>https://hugolavernhe.com/blog/call-transcriber/</link>
      <pubDate>Mon, 28 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://hugolavernhe.com/blog/call-transcriber/</guid>
      <description>Five protocol-level bugs in a Go call-transcriber for Jitsi group calls: Deepgram timeouts, JVB reconnects, and what they teach about integration work.</description>
    </item>
    <item>
      <title>Keeping a WebRTC call alive when a signaling instance goes down</title>
      <link>https://hugolavernhe.com/blog/webrtc-signaling-liveness/</link>
      <pubDate>Wed, 16 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://hugolavernhe.com/blog/webrtc-signaling-liveness/</guid>
      <description>Closing a gap left open by horizontal scale-out: detecting a failed signaling instance, comparing two designs (a sweep vs. a heartbeat lease) on detection latency, false positives under a paused node, and steady-state cost.</description>
    </item>
    <item>
      <title>Scaling a WebRTC signaling layer horizontally</title>
      <link>https://hugolavernhe.com/blog/webrtc-signaling-scale/</link>
      <pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://hugolavernhe.com/blog/webrtc-signaling-scale/</guid>
      <description>Load-testing a single-instance WebRTC signaling path to its actual ceiling, rewriting it around an explicit state machine, then scaling it horizontally with Redis across multiple backend instances.</description>
    </item>
    <item>
      <title>Rewriting Jibri to Use the Jitsi Meet External API</title>
      <link>https://hugolavernhe.com/blog/gsoc-rewrite-jibri/</link>
      <pubDate>Thu, 20 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://hugolavernhe.com/blog/gsoc-rewrite-jibri/</guid>
      <description>A Google Summer of Code 2026 project that moved Jibri from reaching into Jitsi Meet&amp;#39;s internal application state to driving its public External API instead.</description>
    </item>
  </channel>
</rss>
