<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Wycast Blog</title>
    <link>https://staging.wycast.com/blog</link>
    <description>Notes on building live video infrastructure for device fleets.</description>
    <language>en</language>
    <lastBuildDate>Wed, 19 Aug 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://staging.wycast.com/blog/rss.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>Hybrid Is Not a Checkbox</title>
      <link>https://staging.wycast.com/blog/hybrid-is-not-a-checkbox</link>
      <guid isPermaLink="false">wycast-blog-hybrid-is-not-a-checkbox</guid>
      <pubDate>Tue, 11 Aug 2026 00:00:00 GMT</pubDate>
      <description>The ability to run the same operational model in the cloud, on-premises, at the edge, or fully air-gapped is not a deployment option. It is an architectural property that is either present or absent from the beginning.</description>
    </item>
    <item>
      <title>Media, Metadata, and Control on the Same Device</title>
      <link>https://staging.wycast.com/blog/media-metadata-and-control-on-one-device</link>
      <guid isPermaLink="false">wycast-blog-media-metadata-and-control-on-one-device</guid>
      <pubDate>Tue, 04 Aug 2026 00:00:00 GMT</pubDate>
      <description>Keeping video, telemetry, and device commands coherent on constrained hardware is an architectural problem, not a protocol preference. Most systems discover the cost of separation after the fleet is already painful.</description>
    </item>
    <item>
      <title>Why the Edge Runtime Has to Be Small</title>
      <link>https://staging.wycast.com/blog/why-the-edge-runtime-has-to-be-small</link>
      <guid isPermaLink="false">wycast-blog-why-the-edge-runtime-has-to-be-small</guid>
      <pubDate>Tue, 28 Jul 2026 00:00:00 GMT</pubDate>
      <description>On constrained devices, the media runtime is not just another service. Its size, modularity, and assumptions determine what else can still fit on the board.</description>
    </item>
    <item>
      <title>Where the System Is Allowed to Live</title>
      <link>https://staging.wycast.com/blog/where-the-system-is-allowed-to-live</link>
      <guid isPermaLink="false">wycast-blog-where-the-system-is-allowed-to-live</guid>
      <pubDate>Tue, 21 Jul 2026 00:00:00 GMT</pubDate>
      <description>The quiet decision about cloud, edge, hybrid, and air-gap is not a deployment detail. It determines who holds the media, the state, and the failure modes.</description>
    </item>
    <item>
      <title>A Console Is Not a Control Plane</title>
      <link>https://staging.wycast.com/blog/a-console-is-not-a-control-plane</link>
      <guid isPermaLink="false">wycast-blog-a-console-is-not-a-control-plane</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <description>Being able to watch streams is not the same as being able to operate a fleet. The difference shows up the first time you need to change state across many devices without chasing sessions.</description>
    </item>
    <item>
      <title>Your Control Channel Is Becoming a Second Product</title>
      <link>https://staging.wycast.com/blog/your-control-channel-is-a-second-product</link>
      <guid isPermaLink="false">wycast-blog-your-control-channel-is-a-second-product</guid>
      <pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate>
      <description>When media and control travel on separate paths, you inherit separate failure modes, separate authentication, and separate operational tools. Most teams only notice after the fleet is already painful.</description>
    </item>
    <item>
      <title>Stop Paying for the Relay on Sessions That Never Needed It</title>
      <link>https://staging.wycast.com/blog/stop-paying-for-the-relay</link>
      <guid isPermaLink="false">wycast-blog-stop-paying-for-the-relay</guid>
      <pubDate>Tue, 30 Jun 2026 00:00:00 GMT</pubDate>
      <description>Direct-first, relay-only-when-required is an operational rule, not a protocol preference. Defaulting to relay creates a permanent tax on latency and cost.</description>
    </item>
    <item>
      <title>The Network Is Not Going to Cooperate</title>
      <link>https://staging.wycast.com/blog/the-network-is-not-going-to-cooperate</link>
      <guid isPermaLink="false">wycast-blog-the-network-is-not-going-to-cooperate</guid>
      <pubDate>Tue, 23 Jun 2026 00:00:00 GMT</pubDate>
      <description>Designing control so that losing video does not also mean losing the device. Difficult networks are normal operating conditions for anything that leaves a controlled environment.</description>
    </item>
    <item>
      <title>The Camera That Couldn’t Be Moved</title>
      <link>https://staging.wycast.com/blog/the-camera-that-couldnt-be-moved</link>
      <guid isPermaLink="false">wycast-blog-the-camera-that-couldnt-be-moved</guid>
      <pubDate>Tue, 16 Jun 2026 00:00:00 GMT</pubDate>
      <description>Why treating a camera as only a media pipe creates late-stage operational pain. Reassignment without a truck roll or a reflash is a design choice, not a feature request.</description>
    </item>
  </channel>
</rss>
