[tahoe-dev] Choice of tree-hash
tony.arcieri at gmail.com
Tue Oct 2 01:00:42 UTC 2012
On Mon, Oct 1, 2012 at 5:13 PM, James A. Donald <jamesd at echeque.com> wrote:
> This presupposes an improbable degree of competence and industry on the
> part of law enforcement.
It also shows a willingness by the system author(s) (me!) to provide
solutions to their problems. I'm open to better suggestions! Sacrificing
deduplication in the case people don't wish to provide a convergence secret
is unacceptable to me.
> Indeed, we already had this debate. Google and others proposed blocklists
> of files specifically identified by hash, law enforcement and copyright
> holders rejected blocklists of specific content as completely and totally
> unacceptable, indeed outrageous. They want to block by category, rather
> than block exact specific files identified by hash.
*shrug* IMO that's their problem, not mine. There is absolutely no
technological solution to blocking "by category" in a system like the
Cryptosphere. A content ID-based blocklist is the best solution I can
personally think of. I'm open to better suggestions that don't involve
abandoning global deduplication
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the tahoe-dev