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's centralised. But IPFS doesn't offer distributed durability; it offers a CDN. It doesn't seem to address this issue the authors seem to claim it solves. (To me)<p>I still think it'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' seem like a robust answer for the "what if we lose access to the source code problem" given it's not a durable storage system<p>In this case; projects like <a href="https://www.softwareheritage.org/" rel="nofollow">https://www.softwareheritage.org/</a> and <a href="https://sfconservancy.org/" rel="nofollow">https://sfconservancy.org/</a> seem better bets to solve the source code access issue