-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 08 January 2003 09:17 pm, Matthew Toseland wrote: > With the upcoming release of 0.5.1, and with the combination of ARKs and > routing changes meaning that we will probably have a much greater > proportion of new nodes permanent, it seems reasonable that we may need > to increase the default maximum HTL. From a technical point of view, the > only way to be sure that it was adopted would be to increase the last > known good build to the version where we increased it... this would have > much of the effect of a network reset, which could be a problem... we > could increase it without trying to enforce it, but that would be messy > in that some requests would get arbitrarily shortened just because they > went through some old nodes... > > How should we handle this? Should we handle this? The longer we defer it > the greater the impact on the network.
How exactly is the minimum build incremented? If you simply made new builds only connect to newer builds you'd either get both networks anyway, with a bridge layer of above-minimum but not blocking nodes, or you'd start splitting it early. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+Hetox533NjVSos4RAmKcAKC6vjrhCIBR/JDXHtbLJeeTiAM3xACgrWIj yRxmIet90ablo0xudw6QCN8= =HlOs -----END PGP SIGNATURE----- _______________________________________________ devl mailing list devl at freenetproject.org http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
