On Wed, Sep 08, 2021 at 07:12:18PM -0400, Michael Stone wrote: > Why not simply automate setting it at install time using preseed? I'm > honestly not sure who the target audience for auto-apt-proxy is--apparently > someone who has an infrastructure including a proxy, possibly the ability to > set dns records, etc., but can't change defaults at install time or via some > sort of runtime configuration management?
I believe that the target audience is non-tech end-users. Most orgnizations already optimized their way of downloading .debs via some way (e.g. auto-apt-proxy) or another. As you point out, organizations are easily able to deviate from defaults. They're not our primary target with defaults. Laptops of end-user systems are the target, but also developers. When people gather at a place (conference, hackspace, private meetup, etc.) downloading of .debs should just work quickly by default. Many such sites could easily provide a local cache and a number even do. BSPs tend to have a blackboard with information including the local mirror to use. Seriously, how many people change their mirror when they go to a BSP? If we installed auto-apt-proxy by default, much of the local caching would just work. The thing we seem to be disagreeing on is what is more important? https by default or quick and efficient downloads? Some may think that our CDN can handle the load just fine and the effects of caching are peanuts. I can attest that those peanuts are 4TB/year (equivalent to 8 days waiting for downloads) for me. I see that we've given up on a global network of independently-managed mirrors and that CDNs are way easier at this time. While initially CDNs had bad reliability issues, those have completely vanished in my experience. On the other hand, local caching still outperforms CDNs by a factor of 10 or so. I'd love to make it the default. Helmut