On Thursday 18 September 2003 10:59 am, Some Guy wrote: > Well they sure seem to think Freenet is trash (M�ll). > http://f27.parsimony.net/forum66166/messages/2353.htm > > Thier routing is really simple. It won't scale too > well but they can cross some of those bridges when > they come to them. > > As far as thier annoymity is concerned: it suffers in > simular ways freenet may suffer. > 1) If a node requests/inserts something "evil" outside > it's specialization (1/16th slot) to a hostile node, > it's incriminated. In freenet you may still be able > to do the same attack, but you'll have to do more > statistics. > 2) Which nodes have what content seems to be pretty > public too. > > They mention grapevine. > http://www.grapevineproject.org/ > http://grapevine.sourceforge.net/doc/grapevine/grapevine.html > Does anyone know anything about it yet?
I have tried Freenet, Grapevine, Entropy, GunNet, and even Chord. Although I don't know the details of all their implementations, they are all good. So in effect, all three projects suffer form not doing one thing that the others do, and not having a large network. I think all three projects could benefit if a single suffocation could be produced that all three could work towards, that would allow the networks to interoperate. There are a lot of things that are easy to reach a general consensis on. (Encryption / routing etc.) Then for splitfiles FEC is the logical choice, because it is much more sophisticated then anything the other projects use. However it might be nice to have files that did not need to be part of the data store, like in GnuNet. However the hard part would be comming up with a standard for communications and metadata. Ideally the protocol would not care about firewalls / nats and utilize the underlying network as best as possible. I understand Jrand0m has some ideas in this aria. One would probably want to include some sort of simplistic search and flooding resistance, borrowed form GnuNet, and TUKs included in the metadata ala Grapevine. If someone could even produce a preliminary outline of what this should look like and submit it to the other projects, I'm sure they would cooperate and try to come up with improvements. The important thing to remember is this is not just 'Here's how we do it', but rather an ideal network, even if it contains elements that you don't know how to implement yet. _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
