unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Guix-devel <guix-devel@gnu.org>
Subject: Re: Lightning talk at IPFS camp
Date: Mon, 3 Jun 2019 20:53:47 +0200	[thread overview]
Message-ID: <8cdf8d67-2b98-c6f9-e795-d507207b4e1b@fastmail.net> (raw)
In-Reply-To: <Wxmumrlq9b1OnR-XzLeMbkICIfuGY49g5mzznbHIcZA6qqsafY_LDpIejOyRy4W5af5h8qg95fpAfNFpUgmIofQcRuic_dScXYdaSLmJtWk=@protonmail.com>

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 solved, these would be ripe for abuse by malicious actors.

I didn't say that provenance information should be made public, even if 
the data itself is. It could well be encrypted. More generally, 
encryption is an essential ingredient for dealing with non-public data 
in IPFS. Which is indeed a weak point considering that you never know 
for how long encryption will be safe.

> Not having any local file system is also just plain wasteful.

Note that I said file system, not storage. There should be local storage 
for efficiency, but it would act like a cache, not as a separately 
managed storage space.

BTW, data management is not really part of IPFS at all, it needs to be 
handled by another layer and so far there is little more than 
experiments. Textile looks promising, for example.

Konrad.

  reply	other threads:[~2019-06-03 18:53 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
2019-06-03 16:19   ` Pronaip
2019-06-03 18:53     ` Konrad Hinsen [this message]
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=8cdf8d67-2b98-c6f9-e795-d507207b4e1b@fastmail.net \
    --to=konrad.hinsen@fastmail.net \
    --cc=guix-devel@gnu.org \
    /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).