<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Exchange on XKV.org</title>
    <link>https://xkv.org/tags/exchange/</link>
    <description>Recent content in Exchange on XKV.org</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 19 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://xkv.org/tags/exchange/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>XKV Can Now Swap Changes Between Stores and Keep the Reasons Behind Them</title>
      <link>https://xkv.org/xkv-can-now-swap-changes-between-stores-and-keep-the-reasons-behind-them/</link>
      <pubDate>Mon, 19 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://xkv.org/xkv-can-now-swap-changes-between-stores-and-keep-the-reasons-behind-them/</guid>
      <description>&lt;p&gt;XKV 0.2.0 is out, and it adds exchange. One store writes its recent changes to a file, another store reads them in, and every change arrives with its actor, its reason, its ref and its causes. Ask the second store why a value is what it is, and you get the same chain the first store would give you.&lt;/p&gt;&#xA;&lt;p&gt;That matters wherever the same settings live in more than one place. A service and its staging copy. Two sites that each take local writes. A laptop that was offline for a day. Copying values between them is easy. Copying the story behind them is what usually gets lost, and with it any chance of answering &amp;ldquo;who changed this, and why&amp;rdquo; on the receiving side.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
