Stephan Eggermont <step...@stack.nl> writes: >> All of http://files.pharo.org/ ? So how many GB is that? > > It is only a few thousand changes per release. There is no reason why that > shouldn’t compress well
Did anybody try? In IPFS, files are cut into blocks of roughly 256 KB. Blocks shared between multiple files are stored only once. So if changes in Pharo images from one version to the next happen mainly in one or two specific places (such as beginning and end), they would be stored efficiently on IPFS without any effort. But again, the best way to know is to try it out. Konrad.
