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. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20030109/1f8b02b5/attachment.pgp>
