From roots-in@roots-l.rootsweb.com Tue Aug 22 11:31:38 2006
Received: from mail.rootsweb.com (mail.rootsweb.com [192.168.65.34])
	by admin.rootsweb.com (8.12.8/8.12.8) with ESMTP id k7MHVcjb012241;
	Tue, 22 Aug 2006 11:31:38 -0600
Received: from roots-l.rootsweb.com (roots-l.rootsweb.com [66.43.16.22])
	by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k7MHVamX009817
	for <roots-approved@rootsweb.com>; Tue, 22 Aug 2006 11:31:36 -0600
Received: from roots-l.rootsweb.com (roots-l [127.0.0.1])
	by roots-l.rootsweb.com (8.12.10/8.12.10) with ESMTP id k7MEpXFI012746
	for <roots-approved@rootsweb.com>; Tue, 22 Aug 2006 10:51:33 -0400
Received: (from roots-in@localhost)
	by roots-l.rootsweb.com (8.12.10/8.12.8/Submit) id k7MEpXcI012745
	for roots-approved@rootsweb.com; Tue, 22 Aug 2006 10:51:33 -0400
Received: from lists5.rootsweb.com (lists5.rootsweb.com [66.43.27.41])
	by roots-l.rootsweb.com (8.12.10/8.12.10) with SMTP id k7MEiJFI012666
	for <roots-in@roots-l.rootsweb.com>; Tue, 22 Aug 2006 10:44:19 -0400
Received: (from slist@localhost)
	by lists5.rootsweb.com (8.12.8/8.12.8) id k7MHOCVf008217
	for roots-in@roots-l.rootsweb.com; Tue, 22 Aug 2006 11:24:12 -0600
X-Envelope-From: ctm007@gmail.com Tue Aug 22 11:24:12 2006
Received: from mail.rootsweb.com (mail.rootsweb.com [192.168.65.34])
	by admin.rootsweb.com (8.12.8/8.12.8) with ESMTP id k7MHOCjb008208
	for <ROOTS-M@lists5.rootsweb.com>; Tue, 22 Aug 2006 11:24:12 -0600
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169])
	by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k7MHO8o9005659
	for <ROOTS-M@rootsweb.com>; Tue, 22 Aug 2006 11:24:11 -0600
Received: by ug-out-1314.google.com with SMTP id m2so2126555uge
        for <ROOTS-M@rootsweb.com>; Tue, 22 Aug 2006 10:24:09 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=jZWmYvbrUhPs8QXW3DOnqlgduuiCC4rxWrwoveURr69JnBzwqscQXyCvWzaQMvU2PfvVU2iO/FretYVNN83h0isN1wkxklDE4gu1alfMWJpZBkI5sp1PQHqECKqlAXmQ13UT9YOIU4/jJn6SpJm0Q5XG3NG197d4Lt7/CbX9/TE=
Received: by 10.67.89.5 with SMTP id r5mr4517504ugl;
        Tue, 22 Aug 2006 10:24:09 -0700 (PDT)
Received: by 10.67.22.4 with HTTP; Tue, 22 Aug 2006 10:24:09 -0700 (PDT)
Message-ID: <fe7d1acc0608221024n5c9707d7m91196a4fc433e2e9@mail.gmail.com>
Date: Tue, 22 Aug 2006 12:24:09 -0500
From: ctm007 <ctm007@gmail.com>
To: bobert <bobert@i-1.net>
Subject: Re: [ROOTS-L] QUESTION: WHY SUBMIT DATA
Cc: ROOTS-M@rootsweb.com
In-Reply-To: <000101c6c5fe$fb4fbdb0$404eeb04@Desktop>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <200608212346.k7LNkoGt026649@lists5.rootsweb.com>
	 <000101c6c5fe$fb4fbdb0$404eeb04@Desktop>
X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34
X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34
Sender: roots-in@roots-l.rootsweb.com

Hi Shirley,

Please do not take offense with my reply.   I intend no disrespect.  I
just happen to have a different opinion about email messages than most
folks.

I believe we have to Warn the recipient of an email message that it is
not to be disclosed if we expect to keep it secret.   If we fail to
endorse an email message that it is not to be disclosed, then it
becomes public knowledge between we and thee and thee can do with it
as he please.   I know most members of this List disagrees with me,
but that's how I feel.

On the other side of the coin, if one is working a confidential
informant as a law enforcement officer (I use to) and promised him/her
anonymity, and if the one who promised anonymity disclose the
confidential information to unauthorized people, then that person (the
promisor) can be prosecuted.   However, if the informant discloses the
information, then there is no violation.

Also, even if you do endorse your email messages as not to be
disclosed, all email messages are subjected to capture by various
United States law enforcement agencies who will scan the messages for
key words to see if there is any harm in the message.    If that
happens, there is always the possibility that trusted people at ISP's
will sell the email messages to persons interested in screening them
for data to put in search engines.

Bottom line:  one should not expect privacy with an email message.

Carl

On 8/21/06, bobert <bobert@i-1.net> wrote:
> Hi, Rooters.  I have an elementary question:  Why submit family
> data/trees to
> Ancestry or any other website, if you don't want to share it, or have it
> accesible to anyone searching for surnames.
>
> I sent some data to a shirttail cousin and he combined it with some of
> his and, unknown to me at first, submitted to one of these gathering
> websites.   He had no
> permission  to do so - did not understand about submitting data
> on living persons - and it was not until I raised Holy H. with him that
> he
> had it removed.  He told me he 'did it' because all his relatives
> appreciated
> him doing it with their data.
>
> But - the damage was done...and still may be active if he managed
> to slip it...co-mingle it  in,  with another of his own relative's name.
>
> It still rankles when I think of what he did!
> Shirley:  bobert@i-1.net
>
>

