On Fri, Aug 7, 2009 at 2:02 PM, Masayuki Hatta<mhatta at mhatta.org> wrote: >> Inclusion into the official Debain archive would be nice, but is >> problematic. ?The main reason is the update frequency. ?Mandatory >> builds are not uncommon (1-2 per month, perhaps) on Freenet for a >> variety of reasons; if you're not running the latest mandatory >> build, you can't talk to the network. ?That poses problems for >> Debian's update frequency, though it might be possible to have >> something that was perpetually in unstable with no intention of >> migrating to stable. ?I don't know enough about the policies >> surrounding testing to comment on that. > > Hmm, I didn't know the freenet protocol is still in a state of flux. > I can upload packages to sid/experimental and make it never enter into > testing, but I think it would be better to distribute them from the > official Freenet site or such for a while. ?Could someone upload or > put a link to my package repositry?
AIUI, it's not just that the protocol is in flux, but that how the protocol is used is. For example, there were some changes to how caching and htl of requests were handled (builds 1224-1226). Older nodes could talk to newer ones, but a) the caching changes are in preparation for some later changes (bloom filter sharing), and it's important to have the caching changes active everywhere for a while before those go live, and b) there are probably security risks to being one of a very few nodes left using the old caching / htl rules (ie you're safe as long as you do what the herd does, whichever route it's going). Also, the network protocol is still changing, though less frequently. (Every few months, perhaps? You'd have to ask toad.) I think the last change was the turtled transfers a while ago, and the next one will probably be bloom filter sharing. Evan Daniel
