> internal root server. The fact that root server may be added freely by > anyone really means that it isn't centralized. (Kinda like having your > own internal dns server, except everyone can see your entries)
> Node 1 asks Node 2 what nodes it recommends. > Node 2 passes Node 1 a list of fast nodes that it knows and trusts > (optional). > Node 1 adds these nodes to it's list. Now if perhaps you're suggesting that every node acts as a "root server", giving up a list of nodes it knows about, this is perhaps a good idea to kick start new nodes onto the network. However, shipping with a list of nodes is bad. They will be able to find all Freenet users by simply monitoring traffic to a few sites, those which are in the list that is shipped. If all of the initial nodes in the list where SSL-masked nodes running on high traffic sites like sourceforge that had a lot of SSL connections then it might be okay because the first connection would not look like Freenet. The second connection (from the list given by the SSL-masked nodes) would be unrelated to the first connection. So it might be a good way to start nodes on Freenet. The problem is getting a whole bunch of SSL-masked nodes running on high traffic, SSL-using sites. _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
