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, [email protected] 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.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ GNUnet-developers mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnunet-developers
