[2843] in WWW Security List Archive

home help back first fref pref prev next nref lref last post

Re: disabling "save as source"?

daemon@ATHENA.MIT.EDU (Chris Garrigues)
Thu Aug 29 12:59:22 1996

To: Daniel Paz Cornes <dpaz@hsoft.es>
Cc: "O.C. Winton WN1Z" <orrin@redshift.com>, www-security@ns2.rutgers.edu,
        cwg@deepeddy.DeepEddy.Com
In-Reply-To: Your message of "Wed, 28 Aug 1996 21:10:11 +0200."
             <32249993.5B57@hsoft.es> 
Date: Thu, 29 Aug 1996 10:08:53 -0500
From: Chris Garrigues <cwg@DeepEddy.Com>
Errors-To: owner-www-security@ns2.rutgers.edu

--===_-1_Thu_Aug_29_10:08:52_CDT_1996
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable


Somehow I missed Orrin's original message...

> O.C. Winton WN1Z wrote:
> > =

> > Sorry if this has been covered before:
> > =

> > I am thinking of offering web space for sale for people
> > wanting to put their genealogy info & family trees etc.
> > on the Web.  It would be convenient for me if i could offer
> > a deal of "30 days for free, and if you look at it and like
> > it, send me the payment, otherwise it gets removed."
> > =

> > For this to be effective, i'd have to be able to disable their
> > ability to just save it as source and post it somewhere else.
> > Is there a way to do this with Netscape 2.0 + ?

> I think there is no way to do what you want. Server sends the source (u=
sually
> an HTML document) to the client across a TCP connection. Someone who ca=
n get
> the document can save it as source.
> =

> Even if client don=B4t allow you to save the source, you can get it dir=
ectly with
> telnet connection to server, for example.

Daniel is correct.  As such, you need to make sure that you're providing =
some =

"value-added" beyond conversion of geneology data into HTML.

Since I'm interested in this area, I've put some thought into it.  What y=
ou =

need to do is to add the value in the other data which is interlinked wit=
h =

their data.  =

Consider why a genealogist wants to put data on the web?  They probably w=
ant =

to do it so that other genealogists can find their data.  There's your ho=
ok.  =

You need to have a useful master index from which their information can b=
e =

found by other researchers.  What they're paying for is not to have their=
 =

GEDCOM converted into HTML; they're paying to have their GEDCOM data in y=
our =

index.

Designing such a search engine is an interesting problem.  You'd like peo=
ple =

to be able to do queries like "Find the best matches for John Smith, born=
 in =

1763 in New Jersey and moved to Philadelphia where he married a woman nam=
ed =

Jane.  His son was named Thomas".

If you can do this, you'll have one of the prime sites on the net.  If al=
l you =

do is sell pages, you don't really have anythiong very interesting.  I su=
ggest =

you do a search for some of the other existing genealogy stuff on the net=
 =

before you invest any time in this effort.

Chris

-- =

Chris Garrigues                    O-              cwg@DeepEddy.Com
  Deep Eddy Internet Consulting                     +1 512 432 4046
  609 Deep Eddy Avenue
  Austin, TX  78703-4513              http://www.DeepEddy.Com/~cwg/



--===_-1_Thu_Aug_29_10:08:52_CDT_1996
Content-Type: application/pgp-signature

-----BEGIN PGP MESSAGE-----
Version: 2.6.2

iQB1AwUBMiWyf5aQnaaFII2dAQEtDwL9H6Kx5M3pz/Xvt4CWHL54rhHnFUwNYgdY
BungagwsYZ51rzJFO0d9uB9ASozxe6cBzD4JKvzMnI+Jg+a7GXQSF5hdBt6vnQCX
8IjJyWlXfXoLXhN0hv9g6fmNtbEKB/sk
=F+PX
-----END PGP MESSAGE-----

--===_-1_Thu_Aug_29_10:08:52_CDT_1996--

home help back first fref pref prev next nref lref last post