> No, this one's trivial to solve. We've talked about doing selective caching
> in 0.4 or soon after. Nodes should incorporate a simple key closeness
> judgment as well as a load balancing judgment in the selective cache test.
> Then if you request all parts of a splitfile, your node will only cache
> some of them.
The threat is not in that you will have *all* parts of a file, but in that
you will have a suspiciously large number of parts so that it is clear
that you personally requests the file. I doubt that selective caching will
change the caching significantly enough that your cache contents seem
random. Perhaps if you totally rewrote the caching algorithm so that it
*only* cared about key closeness. Then your cache contents would have very
little relation to which files you've requested.
_______________________________________________
Devl mailing list
[EMAIL PROTECTED]
http://lists.freenetproject.org/mailman/listinfo/devl
