From: eric@remailer.net (Eric Hughes)
To: cypherpunks@toad.com
Message Hash: f9d4041a0b80a598678389d4c670d36109e9d43e57363b78db231cdc559a776f
Message ID: <199501121637.IAA00893@largo.remailer.net>
Reply To: <Pine.3.89.9501120925.C24527-0100000@nesta.pr.mcs.net>
UTC Datetime: 1995-01-12 16:38:56 UTC
Raw Date: Thu, 12 Jan 95 08:38:56 PST
From: eric@remailer.net (Eric Hughes)
Date: Thu, 12 Jan 95 08:38:56 PST
To: cypherpunks@toad.com
Subject: Re: Data Havens..A consumer perspective
In-Reply-To: <Pine.3.89.9501120925.C24527-0100000@nesta.pr.mcs.net>
Message-ID: <199501121637.IAA00893@largo.remailer.net>
MIME-Version: 1.0
Content-Type: text/plain
From: Nesta Stubbs <root@nesta.pr.mcs.net>
> 3. I will let you do anything to the data you wish, so long as I
> get it back intact.
why would you give the haven owner free run? I mean naturally he does
have free run with your data once he gets it,
That's exactly the reason, namely, to make the agreement between
individuals match the underlying nature of information. This is
different in the trust in silence about the user. This is also not to
say that the operator can't undertake to make assurances about where
bits go and don't go.
I am sure you
woudln't want your data stored ona public access Unix system, or in
plaintext.
So don't store it in plaintext. The operator of the data storage
facility has no responsibility for this.
if the datahaven is turned into a data broker
I don't know about you, but I don't like paying money for random bits.
well what would be thepurpose of this data haven you propose except as a
extra storage pace for data, like if you dont have space on your own
drive?
Even when you've got enough of your own disk space, it's still subject
to failure. Putting data in multiple places reduces the possibility
of unrecoverable catastrophe.
Eric
Return to January 1995
Return to “root <root@einstein.ssz.com>”