From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Lepiller Subject: Re: plz is there a roadmap for a more resilient substitutes infrastructure? Date: Fri, 02 Nov 2018 23:51:20 +0100 Message-ID: References: <87wopv7jzw.fsf@roquette.mug.biscuolo.net> <20181102210451.htzxk6ox7uldr2fr@thebird.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39272) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gIiIA-0006gF-A1 for guix-devel@gnu.org; Fri, 02 Nov 2018 18:51:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gIiI6-0007iF-To for guix-devel@gnu.org; Fri, 02 Nov 2018 18:51:50 -0400 Received: from lepiller.eu ([2a00:5884:8208::1]:36210) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gIiI6-0007ZP-Dt for guix-devel@gnu.org; Fri, 02 Nov 2018 18:51:46 -0400 In-Reply-To: <20181102210451.htzxk6ox7uldr2fr@thebird.nl> 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: guix-devel@gnu.org, Pjotr Prins , Giovanni Biscuolo We could easily distribute nar files over distributed networks (IPFS, bitto= rrent, =E2=80=A6) but we still need a "canonical source" that builds these = packages, otherwise how do you know what you are looking for? Don't we alwa= ys need some sort of central authority? Le 2 novembre 2018 22:04:51 GMT+01:00, Pjotr Prins a =C3=A9crit : >On Fri, Nov 02, 2018 at 01:16:03PM +0100, Giovanni Biscuolo wrote: >> please is there a roadmap in GNU and/or Guix devel team to address >this >> problems? > >I think it would be a good idea to create a more distributed approach >for creating and finding substitutes=2E A simple name service would >help=2E We could even use IPFS or something to fetch nar files - IPFS >comes with a name service=2E That way anyone building a substitute could >push it to IPFS and expose it to the rest of the world=2E Since IPFS is >content-addressable we can prevent injections=2E Any change to the file >would change its location=2E So the address + NAR hash is safe=2E And no >key setting required=2E > >Does away with the dependency on just a few machines=2E Maintaining >machines is a pain=2E Why not distribute the effort? I am happy to build >some stuff and put it out there - in fact I already run my own >substitute server, but it has only the substitutes I need=2E If we all >do that we can bundle resources together=2E Guix can easily support >that=2E > >If someone wants to think this through and can write a prototype it >would make a great talk at FOSDEM=2E We can also discuss it at Guix >days=2E > >Pj=2E