<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Versioning on Momo Engineering Journal</title><link>/tags/versioning/</link><description>Recent content in Versioning on Momo Engineering Journal</description><image><title>Momo Engineering Journal</title><url>/images/og-image.png</url><link>/images/og-image.png</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 28 Oct 2026 17:47:15 -0600</lastBuildDate><atom:link href="/tags/versioning/index.xml" rel="self" type="application/rss+xml"/><item><title>S3 Versioning on a Content-Addressed Store: Two Kinds of Identity</title><link>/posts/056-s3-versioning-on-cas/</link><pubDate>Sun, 11 Oct 2026 08:56:13 +0000</pubDate><guid>/posts/056-s3-versioning-on-cas/</guid><description>Why S3 versioning and content-addressed storage seem to conflict — mutation identity vs content identity — and how momo keeps both: UUIDv4 version records pointing at deduplicated blobs, delete markers that shadow without deleting, and pagination that can only be computed after sorting. Teaches: the real semantics backup tools depend on, and where the version chain deliberately stops being distributed.</description></item></channel></rss>