unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>, Guix-devel <guix-devel@gnu.org>
Subject: Re: Lightning talk at IPFS camp
Date: Mon, 03 Jun 2019 17:15:44 +0200	[thread overview]
Message-ID: <m1zhmyn1i7.fsf@fastmail.net> (raw)
In-Reply-To: <87ef4g2zfq.fsf@ambrevar.xyz>

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 computing
world.. Bringing the two together can only make this better.

> I'll have to prepare some slides (probably in Org reveal?) soon, so now
> is the time to pitch in some ideas ;)

A common issue: augmenting trust in digital information
  - IPFS: unalterable references to arbitrary data
  - Guix: provenance tracking for software builds

What IPFS can do for Guix:
  - A better way to archive and distribute Guix and the software
    it builds.
  - A unified way to refer to stuff (I am thinking of IPLD here)
    No more tarballs, git commits, etc. CIDs everywhere.
  - A unified storage scheme for all data, both "system" and "user".

What Guix can do for IPFS:
  - Provenance tracking for data that has been processed by software

A vision for a (remote) future:
  - 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 everything else.
  - All data comes with provenance tracking:
     - computations are tracked via Guix
     - human input is logged (interactivity) or version controlled

Konrad.

  parent reply	other threads:[~2019-06-03 15:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30  7:07 Lightning talk at IPFS camp Pierre Neidhardt
2019-05-31 22:10 ` Ludovic Courtès
2019-06-03 15:15 ` Konrad Hinsen [this message]
2019-06-03 16:19   ` Pronaip
2019-06-03 18:53     ` Konrad Hinsen
2019-06-06  8:13       ` Pierre Neidhardt
2019-06-06 12:15         ` Konrad Hinsen
2019-06-06 12:36           ` Pierre Neidhardt
2019-06-06 16:53             ` Konrad Hinsen
2019-06-07 12:39             ` Ludovic Courtès
2019-06-07 13:48               ` Konrad Hinsen
2019-06-07 20:10                 ` Ludovic Courtès
2019-06-07 12:41             ` Ludovic Courtès
2019-06-07 13:45               ` Konrad Hinsen
2019-06-13 21:38         ` ng0
2019-06-24 20:37 ` Pierre Neidhardt
2019-06-26 12:19   ` Pierre Neidhardt
2019-06-27 14:53   ` Ludovic Courtès
2019-06-27 22:04     ` Pierre Neidhardt
2019-07-01 10:16       ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m1zhmyn1i7.fsf@fastmail.net \
    --to=konrad.hinsen@fastmail.net \
    --cc=guix-devel@gnu.org \
    --cc=mail@ambrevar.xyz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).