--- Some Guy <[EMAIL PROTECTED]> wrote: > --- pineapple <[EMAIL PROTECTED]> wrote: > > --- Nick Tarleton <[EMAIL PROTECTED]> wrote: > > > > > Maybe just XOR with a randomly chosen > node-private > > > value. But won't this fubar > > > routing and specialization, if each node has a > > > different ordering in its > > > routing? Or do I misunderstand what is meant by > > > "estimator keyspace"? > > > -- > > > > Since the ordering of keys in the estimator > keyspace > > is completely arbitrary anyway the answer is no, > but > > with some caveats: > > No, sorry pineapple this won't work. Freenet's old > routing required a closer(a,b,c)->boolean, > which has to be globaly defined. It can be defined > serveral ways, you could break each key into > two dimensions and take the "new york distance" or > count the number of bits different. For NGR > you have to keep it in one dimension. Reording the > keyspace differently at every node would break > the routing, since nobody could agree if a node is > specailized in an area.
I fail to see how reording the estimator keyspace would cause a routing problem. Isn't the estimator graph a "black box" that is not shared with the outside world? Why should it matter to a node how another node implements it's estimators? __________________________________ Do you Yahoo!? Exclusive Video Premiere - Britney Spears http://launch.yahoo.com/promos/britneyspears/ _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
