On Wed, May 31, 2006 at 10:31:09AM -0700, Ian Clarke wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > On 31 May 2006, at 04:51, Matthew Toseland wrote: > > >On Mon, May 29, 2006 at 11:06:18PM -0700, Ian Clarke wrote: > > > >Oskar isn't sure how to do it; > > He may not be, I am pretty sure since I have already done something > very similar once in Dijjer.
We are not talking about classic freenet routing here, we are talking about Metropolis-Hastings based networks. > > >he said for example that with fixed > >locations it will work. > > A reasonably stable darknet will have essentially fixed locations, > but even if it doesn't, most location swaps will be between locations > close to each-other. Greedy routing is pretty robust. Ummm, he said using fixed locations on opennet nodes and LRU and greedy routing should work. The problem with this is that the main network swaps locations. > > >I am not willing to deploy opennet until we > >have solid simulations of it, and we have dealt with any serious > >issues, > >and we are reasonably confident with darknet. > > Of course we should simulate it, but at this time I am not aware of > any showstopping problems, I think the path towards implementation of > opennet is pretty clear barring unexpected discoveries in simulations. I think that opennet is likely to bring with it a host of new problems, but the most obvious one is that it will probably have far greater churn of locations, due to having far greater connection churn. It seems that we ought to get darknet working reasonably well first - and there is no reason why a darknet cannot expand rapidly once it reaches a certain size. > > Ian. -- Matthew J Toseland - toad at amphibian.dyndns.org Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: <https://emu.freenetproject.org/pipermail/tech/attachments/20060531/35c21c34/attachment.pgp>