<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Http on XKV.org</title>
    <link>https://xkv.org/tags/http/</link>
    <description>Recent content in Http on XKV.org</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 03 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://xkv.org/tags/http/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>XKV Opens Its HTTP Mode to Other Services and Exports Its Reasons as W3C PROV</title>
      <link>https://xkv.org/xkv-opens-its-http-mode-to-other-services-and-exports-its-reasons-as-w3c-prov/</link>
      <pubDate>Tue, 03 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://xkv.org/xkv-opens-its-http-mode-to-other-services-and-exports-its-reasons-as-w3c-prov/</guid>
      <description>&lt;p&gt;Until now, XKV&amp;rsquo;s HTTP mode had no authentication, so the advice was to keep it on localhost. That ruled out the setup it suits best: a few services, or a few AI agents, writing settings into one store and each saying why. XKV 0.4.0 adds bearer tokens and TLS to &lt;code&gt;xkv serve&lt;/code&gt;, small clients for Python and TypeScript, and an export of the reasons behind a value in W3C PROV, the provenance format audit and lineage tools read.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
