From: ng0 <ng0@infotropique.org>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Using IPFS to host mirrors of source packages
Date: Tue, 22 Aug 2017 19:31:06 +0000 [thread overview]
Message-ID: <20170822193106.n7l3ifkeyqetnsgl@abyayala> (raw)
In-Reply-To: <20170822091407.GA26942@thebird.nl>
[-- Attachment #1: Type: text/plain, Size: 1877 bytes --]
Pjotr Prins transcribed 1.1K bytes:
> On Tue, Aug 22, 2017 at 08:38:32AM +0000, ng0 wrote:
> > Ludovic Courtès transcribed 0.6K bytes:
> > > Hello,
> > >
> > > Pjotr Prins <pjotr.public12@thebird.nl> skribis:
> > >
> > > > By hosting source packages on IPFS they become content addressable and
> > > > should scale for downloads. It would also become a safe way of
> > > > distributing data.
> > > >
> > > > https://github.com/ipfs/ipfs
> >
> > I hope that you are aware that this isn't that safe.
> > As an intermediate solution it is okay. It is similar to providing
> > torrents. It works, but everyone wants the easy way, the
> > easy solution which works $now.
>
> What do you mean? Gnunet has a focus on privacy (at a cost of speed).
> IPFS is not really meant to be private (though you can host a private
> network). For public data it is safe. You have to trust the original
> party that provides the file, but that is similar to what we are doing
> today fetching data from github, ftp etc. (a Guix SHA check is good
> enough).
>
> Today I was bitten again by R/bioconductor removing source files. It
> would make good sense to me to mirror those files on IPFS. I think
> that is a long term solution.
>
> Pj.
While I don't want to comment on everything, let me just comment this:
I think IPFS is the best for now. I'll continue working on GNUnet and
gnunet-fs on my side and will hope that Guix accepts it once gnunet-fs is
ready for this usage.
Offtopic question: What's with my request for inclusion on savannah?
At least a short comment in 4 weeks would be re-assuring. I'm not sure
if there are technical issues or if everyone is on vacation and otherwise
busy.
--
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-08-22 19:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 15:10 Using IPFS to host mirrors of source packages Pjotr Prins
2017-08-11 15:33 ` Alex Sassmannshausen
2017-08-11 19:17 ` Christopher Allan Webber
2017-08-12 13:58 ` Pjotr Prins
2017-08-13 7:36 ` Arun Isaac
2017-08-22 8:18 ` Ludovic Courtès
2017-08-22 8:38 ` ng0
2017-08-22 9:14 ` Pjotr Prins
2017-08-22 10:17 ` Ludovic Courtès
2017-08-22 16:49 ` Pjotr Prins
2017-08-22 22:27 ` Ludovic Courtès
2017-08-22 19:31 ` ng0 [this message]
2017-08-22 9:17 ` ng0
[not found] <mailman.1213.1502464262.21956.guix-devel@gnu.org>
2017-08-11 15:44 ` Joshua Sierles
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=20170822193106.n7l3ifkeyqetnsgl@abyayala \
--to=ng0@infotropique.org \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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).