all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: mikadoZero <mikadozero@yandex.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Software Heritage & Guix
Date: Tue, 02 Apr 2019 20:58:24 -0400	[thread overview]
Message-ID: <cucr2aj52hb.fsf@yandex.com> (raw)
In-Reply-To: <871s2n0zxn.fsf@gnu.org>


Ludovic Courtès writes:

> ... 
> Long-term archival is something that cannot be left to peer-to-peer
> networks: it’s something where you want availability guarantee, whereas
> peer-to-peer storage networks usually replicate content that’s popular,
> while unpopular content disappears.
> ...

As IPFS is already being discussed on the Guix mailing list I looked into
it as an example of how it deals with this "availability guarantee".

There is a relevant section in their documentation on pinning services
which seems to address this directly:

https://docs.ipfs.io/guides/concepts/pinning

So maybe peer to peer data storage networks can do long-term archival.

I am just using IPFS as an example there are alternatives to it.

  reply	other threads:[~2019-04-03  0:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29 16:05 Software Heritage & Guix Ludovic Courtès
2019-03-29 16:42 ` John Soo
2019-03-29 18:19 ` sirgazil
2019-03-30 13:46 ` Pjotr Prins
2019-03-30 15:51 ` znavko
2019-03-30 17:30   ` Pjotr Prins
2019-03-30 18:03 ` znavko
2019-03-30 19:13   ` swedebugia
2019-03-31 16:24     ` Ludovic Courtès
2019-03-31 16:22   ` Ludovic Courtès
2019-03-31  1:57 ` mikadoZero
2019-03-31 16:30   ` Ludovic Courtès
2019-04-03  0:58     ` mikadoZero [this message]
2019-04-03  8:17       ` Giovanni Biscuolo
2019-04-03 21:27         ` Ludovic Courtès
2019-03-31  6:27 ` znavko
2019-04-01  8:33 ` znavko
2019-04-03  7:57 ` Chris Marusich
2019-04-18 16:39 ` 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

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

  git send-email \
    --in-reply-to=cucr2aj52hb.fsf@yandex.com \
    --to=mikadozero@yandex.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.