From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0@n0.is Subject: Re: Using a CDN or some other mirror? Date: Tue, 4 Dec 2018 21:15:41 +0000 Message-ID: <20181204211541.6kdb5zae6ltilyxv@abyayala> References: <20181203154335.10366-1-ludo@gnu.org> <87tvju6145.fsf@gnu.org> <34d346ac-fc0a-aac2-f092-8a57e345c4e6@goebel-consult.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35119) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gUI2o-0003ur-Oy for guix-devel@gnu.org; Tue, 04 Dec 2018 16:15:51 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gUI2j-0004vN-VJ for guix-devel@gnu.org; Tue, 04 Dec 2018 16:15:50 -0500 Received: from static.195.114.201.195.clients.your-server.de ([195.201.114.195]:33298 helo=conspiracy.of.n0.is) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gUI2j-0003GL-La for guix-devel@gnu.org; Tue, 04 Dec 2018 16:15:45 -0500 Content-Disposition: inline In-Reply-To: <34d346ac-fc0a-aac2-f092-8a57e345c4e6@goebel-consult.de> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Hartmut Goebel Cc: guix-devel@gnu.org Hartmut Goebel transcribed 771 bytes: > Am 03.12.2018 um 17:12 schrieb Ludovic Courtès: > > Thus, I’m thinking about using a similar setup, but hosting the mirror > > on some Big Corp CDN or similar. > > Isn't this a contradiction: Building a free infrastructure relaying on > servers from some Big Corporation? Let allow the privacy concerns > raising when delivering data via some Big Corporation. > > If delivering "packages" works via static data without requiring any > additional service, we could ask universities to host Guix, too. IMHO > this is a much preferred solution since this is a decentralized publish > infrastructure already in place for many GNU/Linux distributions. Regardless of me agreeing with Hartmut here, I suggest https://wasabi.com/ as an S3 compatible storage (, which is not run by Amazon.).