Developer liability
Adam Back
adam@cypherspace.org
Wed, 14 Feb 2001 21:25:34 -0400
A solution would be to publish the software anonymously, and
communicates only using pseudonymous or anonymous mail, and
anonymous publishing. Pr0duct Cipher, author of Magic Money would
be an example of this type of thing.
The anonymous publishing system could have it's own software
updates published in it's own distributed document space.
I think I saw the gnutella binary on gnutella. The compiler
boot strapping exercise for pseudonymous publishing systems.
Adam
On Wed, Feb 14, 2001 at 03:06:00PM -0800, hal@finney.org wrote:
> The concern is that even if the P2P system is decentralized and doesn't
> have a core target like Napster.com, the authors of the software could
> be exposed to liability. The motivation on the part of content owners
> would be to discourage the development of new P2P software by scaring
> people away from working on those programs. Obviously the owners aren't
> going to recover much money from these impoverished programmers, who
> are often students working in their spare time (at least that's the case
> with Freenet).