<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Binary-Encoding on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/binary-encoding/</link>
    <description>Recent content in Binary-Encoding on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 21 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/binary-encoding/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted CBOR Binary Serialization Libraries: libcbor vs tinycbor vs QCBOR vs libbinn</title>
      <link>https://www.pistack.xyz/posts/2026-06-21-cbor-binary-serialization-libraries-libcbor-tinycbor-qcbor-libbinn/</link>
      <pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-21-cbor-binary-serialization-libraries-libcbor-tinycbor-qcbor-libbinn/</guid>
      <description>&lt;p&gt;&lt;strong&gt;CBOR&lt;/strong&gt; (Concise Binary Object Representation, RFC 8949) is rapidly becoming the go-to binary serialization format for resource-constrained environments. Unlike JSON, which wastes bandwidth on repeated field names and whitespace, CBOR encodes data in a compact binary form while preserving JSON&amp;rsquo;s flexible data model — objects, arrays, strings, numbers, booleans, and null. It is the backbone of the &lt;strong&gt;IETF&amp;rsquo;s COSE&lt;/strong&gt; (CBOR Object Signing and Encryption) standard and is used in &lt;strong&gt;FIDO2 WebAuthn&lt;/strong&gt;, &lt;strong&gt;W3C Web of Things&lt;/strong&gt;, and &lt;strong&gt;Constrained Application Protocol (CoAP)&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
