[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GNUnet-developers] Network size issues

From: Christian Grothoff
Subject: Re: [GNUnet-developers] Network size issues
Date: Tue, 30 Apr 2019 19:39:23 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1

On 4/30/19 7:33 AM, IC Rainbow wrote:
> Maybe it would be useful for quickstarting F2F networks then?

Well, I'd expect F2F networks to generally prefer other mechanisms:
a hostlist server, or LAN discovery might do just as well. Also, for
simple exchange of the information without the extra 'eternal'
persistence, we have the gnunet-peerinfo -g/-p command (which uses URLs
for basically the same information, instead of binary files).

The gnunet-hello (and gnunet-peerinfo -g/-p) bootstrap mechanism also
assumes that someone has a stable IP, which is not so common, so F2F
networks in a LAN would do better with broadcast/multicast, and on the
Internet possibly with a hostlist.

But of course, in principle, any mechanism could be used.

On 4/30/19 6:35 PM, address@hidden wrote:
> Is it worth documenting, for example as gnunet-hello.1?
> We do document other, not-intended for average users, applications
> already.

Well, peerinfo will disappear with TNG, and HELLOs will look completely
different with TNG. I haven't even planned how we would store these
types of HELLOs in the TNG design, where usually everything is in
PEERSTORE (which often uses a database instead of flat files). So there
is a good chance that gnunet-hello will disappear or significantly
change for 0.12.

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]