<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hardware on Foogar</title>
    <link>https://www.foogar.com/tags/hardware/</link>
    <description>Recent content in Hardware on Foogar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 05 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.foogar.com/tags/hardware/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>It Doesn&#39;t Read the Value, It Counts Your Writes</title>
      <link>https://www.foogar.com/posts/2026-11-05-it-counts-your-writes/</link>
      <pubDate>Thu, 05 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.foogar.com/posts/2026-11-05-it-counts-your-writes/</guid>
      <description>&lt;p&gt;The camera had one job: accept a value and keep it. It accepted the request, returned a success, and handed back something else entirely. Then it did that again, with the same body, and gave me a third answer.&lt;/p&gt;&#xA;&lt;p&gt;The problem started as a frozen picture where a video should be. A live camera view that renders one frame and never moves is a specific kind of insult — the camera is online, the credentials are correct, the path is valid, and the thing still doesn&amp;rsquo;t animate. Two causes were plausible: the transport, and the codec. It turned out to be both. The integration handed out a stream URL in a scheme nothing on the receiving end could open, and behind it the camera was encoding in a codec a browser won&amp;rsquo;t decode without help.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
