Hrmm.. For one, keep in mind that these names are for the User's beneifit, not the node's... In reality, "Charles"'s nodelist is a unique USK, at USK at XCVNDFJGGSSDGSDG...
So that means that the User might get confused, but the node knows the difference between them. Because the node knows the difference between them (the node knows teh difference between the charles that Alice added, and the charles Bob added, since the File includes the original USK), you can prioritize- You can tell the name resolver to draw from the lists in in order of their place in the file.. So if you have Alice USK at SDASD Charles USK at BBBBBB Charles USK at SDGSDGSDGSDG Bob USK at SDFBJISDG Your name resolver will trust the top one more than the second, and so on. Doing it that way automatically passes the order on to the people subscribed to your list.. They inherit your trust relationship, and your priority by default. I think in practice, link pages would end up being uniquely named. Do you have a better suggestion, without giving each node a user-facing generated number? -Colin > > What if I have 2 lists, one from someone I call Alice and one from > someone I call Bob. Then Alice adds a friend she calls Bob (who's not > the same as the one I call Bob). What now? > > Or alternately both Alice and Bob add different Charlies... > > Evan > _______________________________________________ > Devl mailing list > Devl at freenetproject.org > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
