Re: Lightning talk at IPFS camp

2019-07-01 Thread Ludovic Courtès
Hi, Pierre Neidhardt skribis: > All good, I had a look at the discussion and I'll study the patch a bit > more. > > Today I learnt that Nix also had tried the same thing some 2 years > back. And they ran into scalability issues. Maybe we should ask the > Nix folks. Does anyone know more detai

Re: Lightning talk at IPFS camp

2019-06-27 Thread Ludovic Courtès
Hello! Pierre Neidhardt skribis: > Update: I've been asked if I wanted to conduct a "Deep dive" > (https://github.com/ipfs/camp/blob/master/DEEP_DIVES/README.md) about > IPFS and Guix. In other words: what problem we've encountered, how to > solve them, what we'd like to do. Neat. > I think i

Re: Lightning talk at IPFS camp

2019-06-24 Thread Pierre Neidhardt
Update: I've been asked if I wanted to conduct a "Deep dive" (https://github.com/ipfs/camp/blob/master/DEEP_DIVES/README.md) about IPFS and Guix. In other words: what problem we've encountered, how to solve them, what we'd like to do. I think it would be a good time to discuss a work out bug 3389

Re: Lightning talk at IPFS camp

2019-06-13 Thread ng0
Pierre Neidhardt transcribed 1.7K bytes: > Thank you all for your comments! > > > That sounds like a great opportunity. Guix and IPFS are in my humble > > opinion two of the most interesting ongoing projects in the computing > > world.. Bringing the two together can only make this better. > > My

Re: Lightning talk at IPFS camp

2019-06-07 Thread Ludovic Courtès
Konrad Hinsen skribis: > Ludovic Courtès writes: > >> (They could have chosen Guile instead of a custom Lisp, but that’s an >> “implementation detail”. :-)) > > From my reading of the whitepaper, no. They have pretty strict > constraints on their language because they send live code updates > t

Re: Lightning talk at IPFS camp

2019-06-07 Thread Konrad Hinsen
Ludovic Courtès writes: > (They could have chosen Guile instead of a custom Lisp, but that’s an > “implementation detail”. :-)) >From my reading of the whitepaper, no. They have pretty strict constraints on their language because they send live code updates to running instances and want to be a

Re: Lightning talk at IPFS camp

2019-06-07 Thread Konrad Hinsen
Ludovic Courtès writes: > Hey! > > I stumbled upon this: > > https://github.com/ipfs/package-managers#readme And I just stumbled on this one: https://github.com/ipfs/roadmap Quote: 2019 Priority We will be focusing our efforts into a single (lazer focus) priority. 📦 Package Man

Re: Lightning talk at IPFS camp

2019-06-07 Thread Ludovic Courtès
Hi! Pierre Neidhardt skribis: > Konrad Hinsen writes: [...] >> For human input, Git would be OK, with repositories stored in IPFS >> (there's already some support for that, see >> https://github.com/ipfs/go-ipld-git). A more radical redesign is >> Radicle (http://www.radicle.xyz/), which uses

Re: Lightning talk at IPFS camp

2019-06-07 Thread Ludovic Courtès
Hey! I stumbled upon this: https://github.com/ipfs/package-managers#readme Hopefully that’s something you’ll discuss at IPFS Camp! Ludo’.

Re: Lightning talk at IPFS camp

2019-06-06 Thread Konrad Hinsen
Pierre Neidhardt writes: >> I was thinking of the Guix package definitions. In the long run, >> assuming IPFS turns out to be reliable enough, we could put all source >> into IPFS with a CID reference, rather then today's many ways to >> download source files. > > There would be nothing special a

Re: Lightning talk at IPFS camp

2019-06-06 Thread Pierre Neidhardt
Konrad Hinsen writes: > I was thinking of the Guix package definitions. In the long run, > assuming IPFS turns out to be reliable enough, we could put all source > into IPFS with a CID reference, rather then today's many ways to > download source files. There would be nothing special about it be

Re: Lightning talk at IPFS camp

2019-06-06 Thread Konrad Hinsen
Pierre Neidhardt writes: >> - A unified way to refer to stuff (I am thinking of IPLD here) >> No more tarballs, git commits, etc. CIDs everywhere. > > Do you have a concrete use case? I was thinking of the Guix package definitions. In the long run, assuming IPFS turns out to

Re: Lightning talk at IPFS camp

2019-06-03 Thread Konrad Hinsen
Am 03.06.19 um 18:19 schrieb Pronaip: - All data comes with provenance tracking: - computations are tracked via Guix - human input is logged (interactivity) or version controlled unless you vision of the distant future somehow also includes most social problems having been sol

Re: Lightning talk at IPFS camp

2019-06-03 Thread Pronaip
Hi, not to rain on the parade, but > - All data lives in IPFS: no local filesystem, no Guix store. > A personal computing device only stores references to information > that its owner cares about. > > - All computations are equal: no distinction between "software builds" > and ever

Re: Lightning talk at IPFS camp

2019-06-03 Thread Konrad Hinsen
Hi Pierre, > I'm going to the IPFS camp (https://camp.ipfs.io/) on June 27th and I've > been asked to give a (5 minute) lightning talk about IPFS & Guix. Yaik! :) That sounds like a great opportunity. Guix and IPFS are in my humble opinion two of the most interesting ongoing projects in the comp

Re: Lightning talk at IPFS camp

2019-05-31 Thread Ludovic Courtès
Hi Pierre, Pierre Neidhardt skribis: > I'm going to the IPFS camp (https://camp.ipfs.io/) on June 27th and I've > been asked to give a (5 minute) lightning talk about IPFS & Guix. Yaik! :) Excellent, I’m sure you’re going to have a great time! > I'll have to prepare some slides (probably in O