From: zimoun <zimon.toutoune@gmail.com>
To: Maxime Devos <maxime.devos@student.kuleuven.be>, 44199@debbugs.gnu.org
Subject: [bug#44199] [PATCH 0/1] An origin method for GNUnet FS URI's
Date: Wed, 18 Nov 2020 23:40:13 +0100 [thread overview]
Message-ID: <86o8ju2ss2.fsf@gmail.com> (raw)
In-Reply-To: <e6e8c509fff0b5ae2c32678865fba0bece3193d6.camel@student.kuleuven.be>
Dear,
On Wed, 18 Nov 2020 at 21:28, Maxime Devos <maxime.devos@student.kuleuven.be> wrote:
> (btw it's Maxim*e*, not Maxim. The ‘e’ isn't pronounced but it's still
> written.)
Sorry.
>> From my understanding, this is a show stopper. It has to be solved
> first going further, IMHO. It is not possible to write manually the
> URI for all the packages. And as perhaps you read with the project
> ’disassemble’, it is not straightforward.
>
> I agree! I see three straightforward answers to this.
Thanks for sharing your views.
> a) Fancy
>
> Write a GNUnet service using the DHT to map the hashes used in origin
> specifications (*) to URI's for the FS system. To let the local
> contribution to the DHT survive peer restarts, maintain a database
> (e.g. SQlite) of (Guix hash -> GNUnet hash) (^), that is expanded with
> each successful source (or binary) substitution or build.
>
> (Alternatively, as the DHT isn't anonymous,
> place hash -> GNUnet hash references into some well-known name space.
> Then hash lookup + FS should automatically be anonymous when desired.)
Yeah, for sure but both are a piece of tough work though.
> b) Simple, slow introduction (no additional GNUnet services required)
>
> Extend (origin ...) with an optional gnunet-hash field.
> Adjust ‘guix download’, ‘guix refresh’ and ‘guix import’
> to emit the gnunet-hash (%) field. Plumb this field to the guix daemon
> somehow. Same approach is possible for IPFS.
Guix is not doing that for Software Heritage id for example (that’s why
dissamble exists :-)). So I am really doubtful that Guix will do it for
the more-experimental GNUnet.
However, if you want to implement proof-of-concept, you can use the
field ’properties’ which is more or less free. I mean, you can add
whatever you want in.
> c) Not scalable, but may reduce network traffic to ci.guix.gnu.org & co
>
> Like in a) keep a database of known (Guix hash -> GNUnet FS URI).
> Perhaps make this available through a web interface or git repository
> ... wait, this sounds familiar ... this seems to fit well into the
> ‘disarchive’ project!
The most traffic issue is about substitutes, not really about sources.
And about substitutes, this patch #33899 [1] implements the support of
IPFS. Once it is ready, the pieces will be there somehow, so adding
GNUnet to distribute susbtitutes maybe would be an option.
Please join the conference [2] on this Sunday, a session to discuss all
this will be dedicated.
1: <http://issues.guix.gnu.org/issue/33899>
2: <https://guix.gnu.org/en/blog/2020/online-guix-day-announce-2/>
All the best,
simon
next prev parent reply other threads:[~2020-11-18 22:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-24 19:47 [bug#44199] [PATCH 0/1] An origin method for GNUnet FS URI's Maxime Devos
2020-10-24 19:54 ` [bug#44199] [PATCH 1/1] guix: Add (guix gnunet-download) Maxime Devos
2020-10-27 13:39 ` [bug#44199] [PATCH 0/1] An origin method for GNUnet FS URI's zimoun
2020-10-27 18:50 ` Maxime Devos
2020-11-16 0:35 ` zimoun
2020-11-18 20:28 ` Maxime Devos
2020-11-18 22:40 ` zimoun [this message]
2020-11-01 0:05 ` Maxime Devos
2020-11-15 21:13 ` Ludovic Courtès
2020-11-18 19:14 ` Maxime Devos
2020-11-18 22:42 ` zimoun
2021-01-27 13:07 ` [bug#44199] Info: Rehash Project Maxime Devos
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=86o8ju2ss2.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=44199@debbugs.gnu.org \
--cc=maxime.devos@student.kuleuven.be \
/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).