From: abostick@netcom.com (Alan Bostick)
Date: Mon, 9 Jan 95 15:21:38 PST
To: dfloyd@io.com
Subject: Re: Data Haven problems
In-Reply-To: <9501090448.AA14477@anchor.ho.att.com>
Message-ID: <ZwQ4lyczBSQA075yn@netcom.com>
MIME-Version: 1.0
Content-Type: text/plain


-----BEGIN PGP SIGNED MESSAGE-----

In article <9501090448.AA14477@anchor.ho.att.com>, you wrote:

> Filtering by filename and type can also be useful - if you don't allow
> files named *.gif and *.jpg, users may be less likely to
> spam you with pornography.  Namespace control in general is an issue -
> do users get to choose filenames, or list directories, or do they
> have to know the names of files to retrieve. 
> Another issue is whether files can only be retrieved by the sender -
> probably a local policy issue.  

Pornographic images aren't spam _per_se._ What makes them troublesome is
the huge number of people who wish to download them when their
availability is widely known.  (My ISP's ftp site is being bogged down
by lots of accesses; it is speculated that these are people trying to
access pornography kept there.)

The obvious fix here is the same as the proposed fix for remailer
spamming:  charge for access.

As a (presumably) fixed-location data haven, one would want to be able
to use some kind of anonymous e-money for payment, but one could also
use good, old-fashioned credit card numbers, too.

The feelthy peexture business might well be the cash cow that keeps a
data-haven/fortress remailer afloat (if that's not too mixed a metaphor).

                          | PROOF-READER, n: A malefactor who atones for
   Alan Bostick           | making your writing nonsense by permitting
   abostick@netcom.com    | the compositor to make it unintelligible.
finger for PGP public key |      Ambrose Bierce, THE DEVIL'S DICTIONARY
Key fingerprint:          | 
50 22 FB 46 41 A3 17 9D F7 33 FF E1 4E 1C 89 79  +legal_kludge=off

-----BEGIN PGP SIGNATURE-----
Version: 2.6.1

iQB1AgUBLxGxHOVevBgtmhnpAQEEnAL/blauOWwrahdpEK+NbH4WC5V5fekmUYdg
tT5VU+d2C5PGF9Bm5cXtNlZczbI84f+jsBmxRDlXQAsec56D7M7ZwjBMcp2X8t9Z
+FlsU90fRN3NGbYOK/vlSOmzjPBQxf8A
=gvPB
-----END PGP SIGNATURE-----