<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>frostvex</title>
<link>https://frostvex.icu/</link>
<atom:link href="https://frostvex.icu/feed.xml" rel="self" type="application/rss+xml" />
<description>Releases, internals, and benchmarks from the frostvex project.</description>
<language>en-us</language>
<lastBuildDate>Tue, 14 Apr 2026 12:00:00 +0000</lastBuildDate>
<image>
  <url>https://frostvex.icu/assets/og-preview.png</url>
  <title>frostvex</title>
  <link>https://frostvex.icu/</link>
</image>

<item>
<title>Frostvex 0.3 — sub-millisecond diffs and a saner manifest</title>
<link>https://frostvex.icu/blog/v0-3-released.html</link>
<guid>https://frostvex.icu/blog/v0-3-released.html</guid>
<pubDate>Tue, 14 Apr 2026 12:00:00 +0000</pubDate>
<description>Manifest engine rewrite, 60% faster steady-state diffs, breaking changes, migration notes.</description>
</item>

<item>
<title>Benchmarks 2026 — frostvex on a real home network</title>
<link>https://frostvex.icu/blog/benchmarks-2026.html</link>
<guid>https://frostvex.icu/blog/benchmarks-2026.html</guid>
<pubDate>Sat, 04 Apr 2026 09:00:00 +0000</pubDate>
<description>Four nodes, three different ISPs, one of them on flaky LTE backup. Throughput, retransmits, manifest churn, and where we still lose to plain rsync.</description>
</item>

<item>
<title>Why I rewrote the merge engine in Rust</title>
<link>https://frostvex.icu/blog/lockfree-merging.html</link>
<guid>https://frostvex.icu/blog/lockfree-merging.html</guid>
<pubDate>Sun, 29 Mar 2026 10:00:00 +0000</pubDate>
<description>The old merge engine used a coarse mutex. Three readers and two writers were enough to bottleneck it. Here's what I replaced it with.</description>
</item>

<item>
<title>Quarantine, not deletion: how 0.2.x learned to forgive flaky disks</title>
<link>https://frostvex.icu/blog/quarantine-not-deletion.html</link>
<guid>https://frostvex.icu/blog/quarantine-not-deletion.html</guid>
<pubDate>Thu, 12 Feb 2026 14:00:00 +0000</pubDate>
<description>Why frostvex 0.2.x stopped deleting files even when asked. The case for soft removal in sync tools.</description>
</item>

<item>
<title>Picking BLAKE3 over xxh3, and why it took me a week to commit</title>
<link>https://frostvex.icu/blog/blake3-over-xxh3.html</link>
<guid>https://frostvex.icu/blog/blake3-over-xxh3.html</guid>
<pubDate>Thu, 08 Jan 2026 11:00:00 +0000</pubDate>
<description>Why I switched chunk hashing to BLAKE3 in 0.2.5, and why it took me a week to commit.</description>
</item>

<item>
<title>2025 year-end retrospective: 11 releases, 3 bugs that ate sleep</title>
<link>https://frostvex.icu/blog/year-end-2025.html</link>
<guid>https://frostvex.icu/blog/year-end-2025.html</guid>
<pubDate>Sun, 21 Dec 2025 16:00:00 +0000</pubDate>
<description>11 releases, 3 bugs that ate sleep, and what I learned shipping a small CLI in 2025.</description>
</item>

<item>
<title>QUIC for sync: choosing quinn, then patching it</title>
<link>https://frostvex.icu/blog/quic-quinn-patches.html</link>
<guid>https://frostvex.icu/blog/quic-quinn-patches.html</guid>
<pubDate>Tue, 04 Nov 2025 09:00:00 +0000</pubDate>
<description>Why frostvex transports over QUIC, why I picked the quinn library, and the three small patches that made it work.</description>
</item>

<item>
<title>Reed-Solomon parity for backup pools — a small benchmark</title>
<link>https://frostvex.icu/blog/reed-solomon-parity.html</link>
<guid>https://frostvex.icu/blog/reed-solomon-parity.html</guid>
<pubDate>Tue, 30 Sep 2025 12:00:00 +0000</pubDate>
<description>A small benchmark of Reed-Solomon parity overhead across 4+2, 6+3, and 8+4 schemes — and why we ended up at 8+4 for the default.</description>
</item>

<item>
<title>Why Rust, after years of Go</title>
<link>https://frostvex.icu/blog/why-rust.html</link>
<guid>https://frostvex.icu/blog/why-rust.html</guid>
<pubDate>Tue, 19 Nov 2024 14:00:00 +0000</pubDate>
<description>Picking Rust for frostvex was not obvious. Here's the case I made to myself.</description>
</item>

</channel>
</rss>
