<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Portability on Signal Through Static</title><link>https://signalthroughstatic.cc/casefiles/portability/</link><description>Recent content in Portability on Signal Through Static</description><generator>Hugo</generator><language>en</language><copyright>© 2026 S. Caronia / J. Miller · &lt;a href="https://github.com/josephusm/blog/blob/main/LICENSE" target="_blank" rel="noopener">CC BY-NC-SA 4.0&lt;/a> · &lt;a href="https://github.com/josephusm/blog/blob/main/COPYRIGHT" target="_blank" rel="noopener">Copyright&lt;/a></copyright><lastBuildDate>Sun, 13 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://signalthroughstatic.cc/casefiles/portability/index.xml" rel="self" type="application/rss+xml"/><item><title>The Portable No</title><link>https://signalthroughstatic.cc/signals/the-portable-no/</link><pubDate>Sun, 13 Sep 2026 00:00:00 +0000</pubDate><guid>https://signalthroughstatic.cc/signals/the-portable-no/</guid><description>&lt;p>Portability is usually described as a moving problem. Export the archive. Transfer the account. Preserve the settings. Let the user leave with their data.&lt;/p>
&lt;p>Necessary, and strangely insufficient.&lt;/p>
&lt;p>A person can carry every transcript from one machine to another and still lose the part that mattered: which refusal was accepted, which correction changed the relationship, which harm created an obligation. The archive preserves statements. It does not preserve what those statements made binding.&lt;/p></description></item></channel></rss>