From roots-in@roots-l.rootsweb.com Thu Jul 20 12:36:36 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 k6KIaajb010344;
	Thu, 20 Jul 2006 12:36:36 -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 k6KIaYVT007225
	for <roots-approved@rootsweb.com>; Thu, 20 Jul 2006 12:36:34 -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 k6KFwRFI016690
	for <roots-approved@rootsweb.com>; Thu, 20 Jul 2006 11:58:27 -0400
Received: (from roots-in@localhost)
	by roots-l.rootsweb.com (8.12.10/8.12.8/Submit) id k6KFwRwV016689
	for roots-approved@rootsweb.com; Thu, 20 Jul 2006 11:58:27 -0400
Resent-From: roots-in@roots-l.rootsweb.com
Resent-Message-Id: <200607201558.k6KFwRwV016689@roots-l.rootsweb.com>
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 k6KE80FI016414
	for <roots-in@roots-l.rootsweb.com>; Thu, 20 Jul 2006 10:08:00 -0400
Received: (from slist@localhost)
	by lists5.rootsweb.com (8.12.8/8.12.8) id k6KGjuBk011522
	for roots-in@roots-l.rootsweb.com; Thu, 20 Jul 2006 10:45:56 -0600
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 k6KGjujb011513
	for <ROOTS-L@lists5.rootsweb.com>; Thu, 20 Jul 2006 10:45:56 -0600
Received: from bw-10.mtpinos.com (bw-10.mtpinos.com [63.173.235.138])
	by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k6KGjq5x007742
	for <roots-l@rootsweb.com>; Thu, 20 Jul 2006 10:45:52 -0600
Received: from bw-10.mtpinos.com (localhost [127.0.0.1])
	by bw-10.mtpinos.com (Postfix) with ESMTP id 439CF37CAFE
	for <roots-l@rootsweb.com>; Thu, 20 Jul 2006 09:45:52 -0700 (PDT)
Delivery-Date: Thu Jul 20 09:35:29 2006
Received: by askin-67.linkpendium.com (Postfix, from userid 503)
	id B9F5424B18F; Thu, 20 Jul 2006 09:35:24 -0700 (PDT)
Received: (from slist@localhost)
	by lists5.rootsweb.com (8.12.8/8.12.8) id k6KGZMu3008190
	for ROOTS-admin@lists5.rootsweb.com; Thu, 20 Jul 2006 10:35:22 -0600
Date: Thu, 20 Jul 2006 10:35:22 -0600
X-From_: bmarrs@bcmvco.net Thu Jul 20 10:35:22 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 k6KGZMjb008171
	for <ROOTS-L-request@lists5.rootsweb.com>; Thu, 20 Jul 2006 10:35:22 -0600
Received: from mout.perfora.net (mout.perfora.net [217.160.230.41])
	by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k6KGZGEY030729
	for <ROOTS-L-request@rootsweb.com>; Thu, 20 Jul 2006 10:35:17 -0600
Received: from [66.233.8.131] (helo=nlmcoswks0101)
	by mrelay.perfora.net (node=mrelayus1) with ESMTP (Nemesis),
	id 0MKp2t-1G3bUY1uzK-000442; Thu, 20 Jul 2006 12:35:17 -0400
Reply-To: bmarrs@bcmvco.net
From: "Barbara Marrs" <bmarrs@bcmvco.net>
To: ROOTS-L-request@rootsweb.com
Old-Date: Thu, 20 Jul 2006 10:40:17 -0600
Organization: BCMV_NET
Message-ID: <000001c6ac1b$33264b80$8308e942@nlmcoswks0101>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
X-Provags-ID: perfora.net abuse@perfora.net login:cfb179a6b68ec47ad60de261be5bda09
X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34
X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34
X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by admin.rootsweb.com id k6KGZMjb008171
X-Diagnostic: Already on the subscriber list
X-Diagnostic: 5486 bmarrs@bcmvco.net                  32752 bmarrs@bcmvco.net
X-Envelope-To: ROOTS-L-request
Resent-To: roots-l@rootsweb.com
Resent-Date: Thu, 20 Jul 2006 09:45:52 -0700
Sender: roots-in@roots-l.rootsweb.com
Subject: [ROOTS-L] Unauthorized posting

Some years ago I came in contact with a distant many time
generations removed, a cousin of my husbands.  At first we shared
common family genealogy.

Then they posted my deceased son's information.  Repeatedly they
refused to remove his information.  I then contacted the webmaster
and the information was removed, for which I am thankful.  What
scares me is that out there is someone who has no regard for my
right to say when and how my immediate family information will be
posted.  It is unconscious able for any one to take the parents,
children and post their information of someone directly related and
ignore their request to remove them from public viewing.

I believe it is my right to determine when and how my immediate
family members will be posted.  To post individual information just
to rack up the number (one up man ship) is disgusting.  This is not
a numbers game.  It is not how many names we accumulate.  It is an
avenue to find our ancestors and understand the hardships they
endured to survive.  It is a way to personalize history so our
children will understand and appreciate their history.  The way of
life 500 years ago was so different.  To appreciate our ancestors we
need to know the circumstances, dangers, religion, courage,
sickness, determined where they lived and traveled.  How many of our
ancestors would have met and married because they lived hundred of
miles apart until they arrived in the western hemisphere?

With identity theft rampant posting a current decease opens access
to parents, siblings personal information.

I know that the information is accessible because some years later
the information showed up from the postings of a third person.  I
explained to that person and she very understandingly removed my
son's information.

I know where she got this information because it matched the
information from the unclaimed distant descendant.

The information was so very wrong.  My husband and I were born 10
years before his father was born.  They had my son being born years
after he had died.  I also would have been over 100 years old; oh,
yes medical marvel.

The lack of common sense used in so many posting astounds me!

Fortunately, I had not given them my personal data so my side of the
family is, so far, safe.  They did ask for it but my family and my
husband do not have any common ancestors, so I did not see the need
to expand their information.  Hind sight I know now why they were so
wanting my family.

If the other family members thought to disguise the source it did
not work.  All they accomplished was to confusion future researchers
with bad information.  It is hard enough to determine what is
accurate information without a deliberate smoke screen of wrong
information.

My two bits worth
Barbara


 



