Nix × IPFS – Milestone 1
Does IPFS actually solve the problem they set out here though?<p>IPFS is a distributed CDN; but not very good for storing things persistently or reliably from my experience.<p>At the moment; the nixos cache is stored in very durable and reliable S3 storage; with very high durability guarantees. Why is that not good enough?<p>sure it&#x27;s centralised. But IPFS doesn&#x27;t offer distributed durability; it offers a CDN. It doesn&#x27;t seem to address this issue the authors seem to claim it solves. (To me)<p>I still think it&#x27;s _super cool_. And once builds are also content-addressed and not just fixed-output derivations; having trustless content delivery is a valuable addition.  But IPFS doesnt&#x27; seem like a robust answer for the &quot;what if we lose access to the source code problem&quot; given it&#x27;s not a durable storage system<p>In this case; projects like <a href="https:&#x2F;&#x2F;www.softwareheritage.org&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.softwareheritage.org&#x2F;</a> and <a href="https:&#x2F;&#x2F;sfconservancy.org&#x2F;" rel="nofollow">https:&#x2F;&#x2F;sfconservancy.org&#x2F;</a> seem better bets to solve the source code access issue