gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gzz-commits] gzz/Documentation/misc storm-urn-application.txt


From: Benja Fallenstein
Subject: Re: [Gzz-commits] gzz/Documentation/misc storm-urn-application.txt
Date: Wed, 22 Jan 2003 17:21:31 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021226 Debian/1.2.1-9

Alatalo Toni wrote:
On Wed, 22 Jan 2003, Benja Fallenstein wrote:
how are those implemented, then?

Ownership and permissions? Write permissions aren't implemented at all,
since you can't change a block (they're identified by cryptographic

oh of course, sorry for not thinking it through.

hashes, after all). Read permissions are implemented by the pool a block
is placed in: If you have access to the pool, you can read the block.

and i guess copy(right) can't be separated from that, i.e. if you can read
you can copy (although it's not the intention) .. right? or if you think
is stupid just ignore :)

I guess you could implement a voluntary micropayment by including payment data in the header, and requiring clients to respect it. Conceivably you could take legal action against clients that don't. Maybe you could even encrypt the blocks somehow and apply Digital Restrictions Management. I'm not interested in any of this. :-)

- Benja





reply via email to

[Prev in Thread] Current Thread [Next in Thread]