[tahoe-dev] several newbie questions

[Zooko O'Whielacronx]

On Thu, Apr 21, 2011 at 6:58 AM, Miles Fidelman
<mfidelman at meetinghouse.net> wrote:
>
> 2. Looking at the capability mechanisms, it's not clear to what extent
> capabilities are bound to individuals.  The standard problem with key-based
> capabilities mechanisms is that they can be copied.

I think this is an inevitable consequence of a system where people use
computers which are controlled by them and which communicate with one
another over a network. In such a situation, it is impossible to give
someone the ability to read or write some data while completely
preventing them from extending that ability to someone else. I believe
this limitation applies just as well to any other system as it does to
Tahoe-LAFS.

On the other hand, various techniques which go under the rubric of
"DRM" can incompletely prevent people from doing that, and as far as
I've thought about it, Tahoe-LAFS does not prevent you from using
those techniques to deter people from sharing access to data.

This is one of those topics where generalized statements about what is
good and bad generate more heat than light, but concrete technical
details can help everyone understand better.

So, if you want to pursue this topic, please share with us what you
goals are and we can discuss details about how such goals could be
met.

Regards,

Zooko