Sorry I’ve been kind of out of the Haiku loop for a few weeks though I was aware of our infrastructure issues.
A blog post would be nice @kallisti5, maybe you could explain a bit more about why Haiku needs 1 TB of data and 3 TB of bandwidth for the packages, and maybe a bit of the architecture, or you could link to existing docs. That might help people understand the issues better and provide suggestions.
I do suspect that there is massive redundancy and duplication among multiple releases of the same package, and something I’ve thought about for a long time is some way to better archive older releases of packages so they could still be downloaded, if needed, but maybe use less space day to day.
Sort of the same ideas as IPFS but maybe simplified a bit for our use and hopefully made more reliable. Anyhow I’ve had the thought about a “package diff” system for a while, especially for the haiku.hpkg, since I doubt a lot changes between releases. I just need to sit down one day and actually try to implement it
The other benefit of such a system would be tiny, almost instantaneous updates. At least, I think so.