>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. >-- >Matthew Toseland >toad at amphibian.dyndns.org/amphibian at users.sourceforge.net >Freenet/Coldstore open source hacker. >Contracted full time by Freenet Project Inc. >http://freenetproject.org/ >ICTHUS. Do a mandatory upgrade -- just tell everyone two weeks before it goes into effect. Announce it on the website, all the mailing lists, tell Cofe and Cruft so it gets put out on the freesites. People will not mind. The only complaints we got last time, were because NO INFORMATION WAS COMMUNICATED! We need to up the last known good build anyways to get everyone upgraded to the new builds to clear up the old nodes that are running old buggy code. Once that is done, gauging a new bugfix's efffect on the network will be almost realistic. _______________________________________________ devl mailing list devl at freenetproject.org http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
