On Mon, Feb 18, 2002 at 01:31:02AM -0500, Kevin Atkinson wrote: > *) Focus more on speed and scalability than anonymity. The goal of > DistribNet is to be as fast or faster than the Web for any sort of > pages with reasonable popularity.
Certainly, by removing a lot of the crypto in Freenet, you could probably come up with a system that is faster, but Freenet's underlying protocol has log(n) scalability which is probably as good as you could hope for in any such system. My advice is to stick with the underlying protocol to get its scalability, and adaptiveness, just strip out the crypto. > *) Data will not have to be routed though other nodes. Instead most > data will be send directly from one node to another. Freenet's underlying algorithm relies on this, if you get rid of that, you will be throwing the baby (underlying routing/caching algorithm) out with the "bathwater" (crypto stuff which is only needed for anonymity). > *) Will allow anyone to anonymously post content to the network You can't have it both ways. If you get rid of the crypto, you lose the anonymity. > *) The ability for one to share content that is on one's hard drive > or be able to fetch content from the Web or other networks when it > is more effect to do so. Again, the reason that you can't just share stuff on your hard disk is that nobody else will be able to find it without using some kind of inefficient gnutella-style search. > *) Searching and support for "updateable" keys will be build into the > protocol from the beginning. The searching faculty will be > designed in such a way to make message boards trivial to implement. Easy to say, not so easy to do. > There will not be anything like freenet's KSK keys as those proved to > be completely insure. If you mean "insecure" then you shouldn't worry about that, your entire architecture will be "insecure" in the same way. That isn't nescessarily a bad thing, your goals aren't as paranoid as freenet's. > Query for keys will be handled similar to freenet but instead of > returning the actual data a pointer to the node which can easily > provide the data is returned. What if that node goes down? What if its connection is slow? What if its data is so popular that the node goes down? What if the data is available from multiple nodes? You should stick to Freenet's caching algorithms, they are essential to Freenet's scalability and robustness. If you don't care about those, then you shouldn't try to claim that your architecture is based on Freenet, since you will be throwing out most of what is valuable about the Freenet architecture. Ian. -- Ian Clarke [EMAIL PROTECTED] Founder & Coordinator, The Freenet Project http://freenetproject.org/ Chief Technology Officer, Uprizer Inc. http://www.uprizer.com/
msg00594/pgp00000.pgp
Description: PGP signature
