The New Family Finder NGS Test Results, Comparison, and Preparation

This article is focused on two things.

  1. Comparison of my new NGS and the earlier Family Finder tests
  2. How to prepare for yours if you’ve ordered the upgrade

I compared my results from my older Family Finder test with my new NGS Family Finder test results. As an early beta tester, I have two separate tests, a strategy that is not recommended because it causes duplicate matches for people within the database. Additionally, multiple kits for one person doubles the results and could skew future ethnicity research for myOrigins.

Therefore, FamilyTreeDNA has announced very attractively priced upgrades at $29 for both:

  • People who have taken Family Finder test directly at FamilyTreeDNA
  • People who have uploaded their DNA files into Family Finder from other companies

After seeing my comparison, you may want to compare your own results when they arrive, so I’ve documented that process. Warning: this took between 4 and five days because I was working with a spreadsheet with more than 15,000 rows, and I had to write scripts to perform multiple functions. It was NOT fun and I do not recommend it.

Personally, had I known then what I know now about how reliable the new NGS test is, I wouldn’t have bothered with the comparison. However, I would have downloaded my original match list for posterity, just in case.

If you purchase an upgrade to the new NGS Family Finder, your new test results will replace your older Family Finder test results, but will preserve important account features such as linked matches, any notes you have taken, and more. That’s another reason to upgrade rather than order a separate new test. They’ve done the heavy lifting, not to mention that you’ll save about $50 when compared to the price of a new test.

Why is the New NGS Family Finder Test Better?

The new NGS test holds immense promise for the future. This includes better matching, beginning now. Essentially, FamilyTreeDNA is skating to where the puck is going to be (hockey analogy) and preparing for future tools. That future is not far away!

An amazing new set of tools is goaled for release around the end of the year. And I do mean amazing. They are being beta-tested internally now.

Dave Vance spoke about the new Family Finder NGS test at the ECGGC conference in late August, which you can view through the end of 2026 if you register for the virtual  conference, here, and watch the recorded sessions. You’re looking for the DNA Academy on Saturday evening. I can’t share specific preview slides with you as they are noted in his presentation as “not for distribution,” so my pen is capped for now.

All I can say is that after seeing what’s in store, people were literally throwing their billfold at the folks at the FamilyTreeDNA booth – and I do mean literally. “Here – take my money, please!” as the billfold went sailing. We all had a good laugh, but he was serious.

One presenter (not me, just in case you are wondering) left her credit card and a list of tests to upgrade while she was presenting.

They ran out of swab kits at the conference shortly after Dave’s presentation about what the future holds.

Additionally, you will also be treated to THE absolute best presentation I’ve ever seen about what NGS testing is, how it works, and how it compares to traditional tests, low-pass whole-genome tests, and medical-grade whole-genome tests.

You’ll be a passenger on the Genome Valley train, so climb aboard!

So, without spilling any beans, what’s so great about the NGS test?

To begin with, the older Family Finder tests won’t be able to provide everything the new NGS test will be able to offer – and those completely new tools are in active development today.

Why?

The NGS test targets over 280 million base pairs, up from the currently available 700,000.

That’s more than 400 TIMES the coverage.

This increases coverage in the human genome from about .02% to about 9%.

To quote FamilyTreeDNA, “This change allows us to deliver more precise autosomal results today while creating a strong foundation for future reports and tools.”

You can read the FamilyTreeDNA FAQ here.

Before we move on to the comparison, let’s talk for a minute about test types and uploads from other vendors.

Tests and Uploads

All new Family Finder tests purchased at FamilyTreeDNA since March 2, 2026 have been tested using Next Generation Sequencing (NGS), so the following matrix does not apply to those tests. Those tests don’t need to be upgraded.

If you sign on to your account, on the Family Ancestry dashboard, and see that your NGS button is grey, then you have not upgraded. Click on that grey button to read more and to upgrade. Right now the upgrade is $29, but I don’t know if that is a promotional price or permanent.

If you tested at FamilyTreeDNA prior to March 2, 2026, or uploaded a DNA file from another vendor, your test will fall into one of the following upgrade path categories.

Tested at FamilyTreeDNA before March 2, 2026 Uploaded and purchased the Unlock Uploaded but did not purchase the Unlock
Upgrade Path Can use sample stored in lab if enough DNA remains* If you purchased any other type of test at FamilyTreeDNA, they will use DNA stored in the lab if enough remains. Otherwise, you will be sent swabs. If you purchased any other type of test at FamilyTreeDNA, they will use DNA stored in the lab if enough remains. Otherwise, you will be sent swabs.
New Swabs* If needed, they will notify you Yes, if needed, will notify or send swabs if you have not taken a direct test at FamilyTreeDNA Yes, if needed, will notify or send swabs if you have not taken a direct test at FamilyTreeDNA
NGS Results Will replace existing results Will replace existing results Will replace existing results

*You will be notified if enough DNA does not remain, and you will be sent new swabs. Be sure your address is current.

One of the reasons the NGS test performs better, even with existing matches from earlier tests, is because less imputation is involved. Let’s talk for a minute about imputation and how it works.

The Concept of Imputation

Most vendors change chips internally from time to time, and FamilyTreeDNA is no different. The difference this time is that the new NGS test covers exponentially more DNA than any earlier test, and all earlier tests combined. This means more than 400 times greater coverage, which in turn means less imputation is needed to compensate for the inevitable no-reads and to be compatible with files that tested different DNA locations.

Imputation is also used when comparing DNA files between vendors who don’t test the same locations.

Click to enlarge any image

Here’s an illustration of the concept of how imputation works.

All of the FamilyTreeDNA chip versions over the years have included about 700,000 locations, as have most other vendors. But the locations tested are not universally the same.

In our simplified concept example, FamilyTreeDNA’s tested “locations” are shown with blue cells.

The total of 20 squares shows the maximum amount of DNA tested by any of the three vendors shown, combined.

Green Vendor 1 in our illustration tests the same amount of DNA that FamilyTreeDNA tests, 12 squares, but some locations are the same and some are different. Of the 12 colored squares for both vendors, seven are the same locations, and five are not. The locations that are the same can be compared directly, but the locations that are different have to undergo special handling called imputation.

Looking at any location in our DNA, one of four nucleotides, or letters, can be present: T, A, C or G on each strand of our chromosomes, although we are only looking at one strand in our example.

Using a very simplified model of imputation, think of imputation as “filling in the blanks” using clues from surrounding letters – kind of like a crossword puzzle.

When two vendors’ data doesn’t overlap, imputation is used to fill in the blanks, as accurately as possible, for the missing data.

Using a word analogy, for vendors one and two only, we see that blue location three has no Family Finder data, where green Vendor 1 does, and the same with location five. If blue locations two and four are C and T, and three has to make a word, then there are few options. In this case, let’s say it’s cat, and location five is imputed to an A too.

Now moving to green Vendor 1, their locations two and five need to be imputed. Moving away from the word analogy, let’s look to the human genome, and let’s say that most of the time, location two is a C if location one and three are Gs. So green location two is imputed to C.

If there’s not enough quality surrounding data, imputation can’t be performed reliably. Hence, location six is still in limbo here.

You can see that in our scenario, location three is the only mismatch, out of three imputed locations. Does location three mismatch because imputation was wrong? We don’t know. Do locations two and five match because imputation was wrong? We don’t know.

All things considered, imputation is based on the science of probability, and is usually relatively reliable, but it’s still not the same as comparing actual data. The more locations that have to be imputed, and the longer the stretch, the greater the possibility of error. Every vendor implements imputation differently too. Even vendors who don’t and have never accepted uploads still use imputation internally to equalize their own legacy files from earlier test versions.

Stepping back once again to compare the four vendors, you’ll notice that pink Vendor 3 only tested half as much DNA as the blue Family Finder test and green Vendor 1, and again, not all of the same locations. That’s exactly what happened with one of the vendors last December – they dropped the number of DNA locations tested to about 400,000 from about 700,000. In our example, you can see how much would have to be imputed. Locations 11, 15, 19 and 20 can’t be imputed for the pink vendor’s file because there’s no surrounding DNA. Location 17 can’t be imputed for the green vendor for the same reason.

When vendors impute to match multiple versions of other vendors’ uploaded files, it can quickly become messy.

The answer, of course, is a “supertest,” which tests all of the locations that overlap everyone, including that vendor’s own earlier tests.

Welcome to Family Finder NGS, shown in orange at the bottom of our example comparison.

As you can see, the orange NGS test covers all of the locations tested by all of the other tests.

NGS is targeted testing for a specific set of locations that are known to undergo mutations in the human genome and provides extremely high-quality results. Imputation for the NGS file is rarely necessary, although imputation for the other vendors’ and earlier file versions is still required for them to match to each other.

This is exactly why the upgrade is recommended, and why there’s no benefit to retaining your old test. The NGS test tests far more data and provides much more reliable matching.

NGS is the great equalizer.

NGS Test Comparison Process

I took my NGS test during the initial R&D development and testing phase, so my original Family Finder test was not upgraded. This afforded me the opportunity to compare the two results.

I downloaded the match files for both of my tests, the original Family Finder and the new NGS Family Finder test, color-coded the background of the cells, not the text inside the cells, and dropped them into a single combined spreadsheet.

It doesn’t matter what colors you choose, but be sure you can easily see the difference. I used apricot for the original Family Finder test matches and light purple for the new NGS test.

As we walk through these results together, you’ll notice that I continue to refer to them by color. In part, that’s so I can maintain my own sanity as I compare results. When I write these types of articles, I have to check and recheck results.

When the same person showed as a match to both tests (meaning they had both an apricot and purple row), I calculated the difference in matching amounts of DNA (cMs) between the match’s results on both tests. I added several calculation columns, which are not shown above.

I’ll tell you, this was not a trivial exercise. It was painful and I really don’t recommend it.

Let’s take a look at the results.

Total Matches

I have some matches with the new NGS test that I do not have with the legacy Family Finder, and I have some matches on the older test that are no longer present on the NGS test.

  Old Family Finder (apricot) NGS Family Finder (purple) Difference
Total Matches 9014 7719 1,295
Maternal 1665 Not linked
Paternal 3783 Not linked
X-Matches 2198 1849 349

I have not yet linked the same matches in my NGS test, so I can’t compare the number of maternal and paternal matches. Fortunately, when you upgrade an existing test, FamilyTreeDNA preserves your linked matches, so you won’t need to relink.

Relationship Estimates

  Old Family Finder (apricot) NGS Family Finder (purple)
1st-2nd cousins, Great/Half Uncle/Aunt/Niece/Nephew, Great-Grandparent/Grandchild 6 6
1st-3rd cousin 1 1
2nd-3rd cousin 5 4
2nd-4th cousin 127 132
3rd-5th cousin 1937 1900
4th to remote 6938 5676
Total 9014 7719

The closest relationships remained the same. One 2nd-3rd cousin moved to the 2nd-4th cousin range by losing 10 cM, 194 cM to 184 cM, but they were apparently on the threshold anyway. That match is actually my second cousin, so both ranges are accurate. It was also a transfer kit, so they did not test at FamilyTreeDNA. This revised match is probably the difference between actual reads and imputed reads in some regions, meaning the match is now more accurate.

275 matches had a predicted relationship change, but not uniformly in one direction, and no one moved more than one category in either direction. This all makes sense.

Match Differences

  Number
Matches found in both the apricot and purple spreadsheets 7,352
Unique (comparable) matches in both spreadsheets 7,174
Matches in original Family Finder apricot only 1,681
Matches in NGS purple only 400

A total of 7,352 matches appear in both spreadsheets, meaning the apricot and purple names matched exactly.

Unfortunately, some people had multiple tests, so I couldn’t always compare apples to apples because they appear three times or more on the combined spreadsheet, and I don’t know which of their kits are which.

If someone with the same exact name had more than one match for either or both tests, I did not compare them because their matching amounts were different, and I didn’t know which one(s) my old test matched, versus which one(s) my new test matched. Usually, one was an upload and one was a test at FamilyTreeDNA, but not always. I excluded those 178 match rows from the analysis.

Therefore, 7,174 matches could be directly compared.

There were 1,681 people who match ONLY on the old Family Finder test, and 400 that match only on the new NGS test. And yes, I downloaded the match files at the same time on the same day, so this comparison was controlled for any time difference.

cM Differences

  Number
Largest apricot match not in purple (NGS) list 26.3 cM
Largest purple (NGS) match not in apricot list 27.63 cM
Largest difference 69.86 cM NGS kit more
NGS detected greater over 10 cMs 19
NGS detected less over 10 cM 7
Total NGS greater 2,924
Total NGS less 3,040
No change 1,090

The largest value difference where a match appeared in the original apricot Family Finder test, and not in the purple NGS test, was 26.3 cMs.

The largest value difference where a match appeared in the NGS purple Family Finder test, and not in the apricot original Family Finder test was 27.63 cMs.

The largest difference between the two tests was 69.86 cMs larger detected by the NGS test. This match was a known second cousin whose matching cMs went from 373.06 to 442.92, but the longest block only increased a negligible amount from 87.47 to 87.69.

The next largest difference was with a 1C1R with a 41.56 cMs difference, also with the NGS-detected value being larger.

In all cases where the number of differing cMs was 16 or greater, the NGS had detected more.

There were very few tests that differed more than 10 cMs. In 19 cases, the NGS test detected a greater difference of 10 cMs or higher, meaning if the original test value was 100 cMs, in the NGS test, it was 110 cMs or greater.

In 7 cases the NGS test detected a smaller difference of 10 cMs or more, meaning that if the original test value was 100 cMs, in the NGS test, it was 90 cMs or smaller.

Out of the 7,174 tests being compared, 19 tests with greater than a 10 cM variation isn’t very many, around 0.26%.

In total, 1,090 matches had no change at all, while 2,924 NGS matches had more matching DNA detected, and 3,160 matches had less.

All but 287 of those differences were less than 5 cMs, and 6778 were less than 1 cM. In other words, literally not worth counting.

myOrigins Ethnicity

We all know to expect changes in our ethnicity from time to time at all vendors. The NGS test is exciting because it covers a much larger portion of our genome. As more people test, the reference library also becomes larger, which means that the ethnicity predictions can and will become more refined too

myOrigins Old Family Finder (apricot) NGS Family Finder (purple)
Central Europe 57% 52%
England, Wales, Scotland 28% 33%
Ireland 15% 14%
Magyar <1% <2%
AmerIndian Andes and Caribbean <1 (see below) N/A
AmerIndian North America <1% (chr 1 & 13) <1 (chr 1 & 2)
Anatolia, Armenia, Mesopotamia, North Africa <1 (chr 13) <1% (chr 10)

None of my major categories changed, but the amounts attributed to each category changed somewhat.

Trace regions, which are less than 1%, shifted some as well, as did their chromosome locations.

For me, this is particularly interesting, because I paint my ethnicity segments at DNAPainter in order to overlay my Native American segments over the matches with whom I’ve identified common ancestors.

Those segments, matches, and ancestors, taken together, help identify the source of the Native American segments.

My Native segment on chromosome one stayed essentially the same, but the Native segment on chromosome 13 is not present on the new NGS test. However, a new Native American segment is now shown on chromosome 2 in the same location that 23andMe also shows a Native American segment.

Chromosome one has already been proven to a Native American ancestor on my mother’s side, but I have hit a brick wall on the chromosome 13 segment. Now, I’ve painted the Native Segment on chromosome 2 and it aligns with the same ancestral line as my Native American segment on chromosome 1.

My Middle Eastern/North African segment still exists, but the location has changed. This segment was adjacent to my Native American segment on chromosome 13 before, on my father’s side, which suggested a history of enslavement. I thought I knew which ancestral line they both descend from, but now I need to review my matches and reconsider.

Unfortunately, my parents are both deceased and there’s no DNA available, so I cannot upgrade their tests or purchase new ones for them. No aunts or uncles are available either. In this case, cousin matches and their associated genealogy on those segments become critically important.

Native American and African American segments are often the best, and sometimes the only hints we have to find and identify those ancestors.

Preparing for Your NGS Results

To be very clear, you don’t necessarily need to compare or prepare, BUT, if you order an upgrade to an existing test, your old match list will be replaced with the new one. Your old match list will not be preserved unless you do it.

What may change?

  • Your ethnicity results will probably change somewhat
  • You will have matches you did not have before
  • Some existing matches, especially at low matching levels, will no longer be there
  • The amount of DNA you share with some people will change

Important: Any notes you have recorded on your matches and any matches that you have linked will be preserved and carried over to your new results when your new test is complete.

If you want to preserve your matches from your earlier test, or your myOrigins results, you’ll need to download your match list, and either download or take screenshots of your ethnicity information.

Ability to Download Tested at FamilyTreeDNA before March 2, 2026 Uploaded and purchased the Unlock Uploaded but did not purchase the Unlock
myOrigins Can download Can download Cannot download
Chromosome Painter (ethnicity) Can download Can download Cannot download
Match list with segment and other information Can download Can download Cannot download
Raw data file Can download Cannot download* Cannot download*

*On tests you uploaded, you don’t need to download the raw data file because you already have it from the originating vendor.

What information is included in your Match List download file?

  • Match name
  • Relationship Range
  • Shared Data cMs
  • Longest Block cMs
  • Linked Relationship (if you linked them in your tree) – this feature is what allows FamilyTreeDNA to assign your matches maternally, paternally or to both sides using triangulation
  • Ancestral Surnames that they’ve entered
  • Y-DNA Haplogroup if applicable
  • mtDNA Haplogroup if applicable
  • Notes
  • Paternal/Maternal or Both side(s) match (if you’ve linked people and this match can be assigned using triangulation. (This is why it’s important to link as many people as possible to their place in your tree.)
  • X-Match cMs
  • Autosomal Transfer yes/no

If you match the same person on the NGS test, this information is preserved for that match.

Where to Download

You must have 2FA (Two-Factor Authentication) enabled for all downloads.

The files you may want to download are found on your dashboard in two locations.

  • Family Finder Matches
  • Chromosome Painter (ethnicity)

Family Finder Matches Download

To download your list of matches with their complete information, click on Family Finder Matches on the dashboard, then on “Export CSV.”

This download provides all the fields mentioned above, whereas the Chromosome Browser segment download provides only your matching segment data, without the additional information.

Download MyOrigins Ethnicity Segment Data

To download your myOrigins ethnicity segments, click on Chromosome Painter on your dashboard, then on “Download Segments.” You can also view or copy those segments by viewing the Detailed Segments tab.

I paint these segments at DNAPainter so that I can correlate my ethnicity regions with my ancestors’ segments.

To assign segments accurately, it helps immensely to have at least one parent’s DNA results too, and preferably both.

You may also want to take a screenshot of your myOrigins map. Note the left-side scroll bar when you’re taking screenshots.

What’s Next?

What else can you do at FamilyTreeDNA to benefit your genealogy?

  • If you haven’t already, upload a GEDCOM file or create a tree at MyHeritage, and link your Family Finder test to your results.
  • Link your individual matches to their place in your tree. This allows FamilyTreeDNA to use segments triangulated with linked matches to assign other matches to either the maternal or paternal side of your tree, or both.
  • Add your line to WikiTree. It’s easy. Begin with yourself and add ancestors until you connect with someone who is already in WikiTree. For me, it was the grandparent level.
  • Add your WikiTree link to your FamilyTreeDNA account under the gear in the upper right-hand corner, then Genealogy, then Family Tree. This gives your matches an easy way to identify common ancestors by using WikiTree’s Find Relationships feature, and provides two types of tree resources for you and your matches – MyHeritage and WikiTree.
  • Make sure your Earliest Known Ancestor information is correct and up-to-date with your most recent research, including a specific map location. You’ll find that under the gear too, then Genealogy, then Earliest Known Ancestors.
  • Add your surname list to your profile under the gear, Genealogy, Surnames tab.
  • Use the Matrix tool at FamilyTreeDNA to see how much DNA your shared matches share with each other.
  • Y-DNA – If you’re a male, test your Y-DNA, which is your father’s direct paternal line. The Big Y-700 test provides you with matches and the most detailed information possible.
  • mtDNA – Everyone can take a mitochondrial DNA test, which shows matches and provides information about your mother’s direct matrilineal line.
  • Use Advanced Matching, found under Additional Tests and Tools on your dashboard page, near the bottom, which allows you to select from multiple tests to see who matches you on both types of tests. For example, those who match you on both your full sequence mtDNA test and your Family Finder test.
  • Join projects relevant to your family surname, geography or broader interests. You’ll find Group Projects in the top banner of your dashboard page after signing in.
  • Utilize the Discover tools for both Y-DNA and mitochondrial DNA results.

Check your matches often to see who is new and what might have changed as people upgrade to the new NGS test and more people test.

_____________________________________________________________

Share the Love!

You’re always welcome to forward articles or links to friends and share on social media.

Subscribe!

If you haven’t already subscribed, it’s free. You’ll receive an e-mail whenever I publish by clicking the “follow” button at the top of the main blog page, here.

Help Keep This Blog Free

I receive a small commission when you click a vendor link in my articles and purchase that item. This does NOT increase your price but helps me keep the lights on and this informational blog free for everyone. Please click on the affiliate links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

What is a Quick-and-Dirty Tree, and When Might I Need One?

You may have heard genealogists talk about creating a quick-and-dirty tree.

What is that, exactly? When and why would you want one?

Good questions.

Matches and Trees

DNA matches don’t always have useful trees.

They might have:

  • No tree
  • A partial tree with only a few people in the closest generation or two
  • A tree with some lines built out, but others not so much

What’s a genealogist to do? After all, it’s your match’s tree, not your tree, and you have no way to expand their tree.

Except, you do.

It’s called a quick-and-dirty tree.

Quick-and-Dirty Trees

A quick-and-dirty tree is essentially a “throw-away” tree that you construct at Ancestry with the express purpose of obtaining hints, including potential parents, in order to quickly build your matches tree backwards in time until you (hopefully) reach a common ancestor.

And yes, of course trees, hints and suggestions of any kind can be wrong – but that doesn’t mean they’re always wrong, and you’re not adding anything from your quick-and-dirty tree to your tree – or even displaying it publicly.

You’re simply trying to find a common ancestor by using what your match has provided in their tree. Think of a quick-and-dirty tree as a scratch pad of sorts.

Let’s work through an example.

Initial Analysis

In this example, Ancestry has already told me that this match is most probably my half-second-cousin (half 2C) or second-cousin-once-removed (2C1R) based on the amount of DNA that we share, although the full relationship range includes several more options.

Ancestry also tells me that this match is on my maternal side. There’s no information provided about whether this match is on their maternal or paternal side, or even both.

A second-cousin (2C) relationship means that we share great-grandparents, and once removed means that one of us is one step further down the tree than the other person.

In other words, I’m 2C with my match’s parents, or my match is 2C with my mother. I wrote about this in the article, Concepts: What Does a Cousin “Once Removed” Mean?

I see that my match has a public linked tree with 7 people, which probably isn’t going to be terribly helpful.

Of course, the first thing to do is to review my match’s tree and see if I recognize either their surname or the names in their tree.

This tree only reaches back two generations, and our common ancestor, based on the relationships predicted by shared DNA, would be another generation, or two, further removed.

I don’t recognize any of these names, although I’ll review each person for a location to see if I can narrow the scope to the couple most likely to lead to our common ancestor.

On my mother’s side, one of her parents is from northern Indiana, and one is from southern Indiana, but not everyone enters locations in their trees, and they aren’t necessarily accurate.

The list of “all people” in my match’s tree, under “Find in tree”, at far right, provides additional information. Unfortunately, this tree shows Earl Townsend’s wife’s name as Mildred Ideal Thorstenson Townsend Smith here and in her profile, but the name order differs. To begin, I’ll enter Thorstenson Smith, not her married name of Townsend, in the quick-and-dirty tree I’m building. You can refine this shortly.

In this case, it looks like the Townsend line is most promising to find a common ancestor, given that Fulton County is in northern Indiana, but we’ll find out that this isn’t the case when we construct our quick-and-dirty tree.

Building the Quick-and-Dirty Tree

You need to build a new tree, NOT add to your “real” tree.

At Ancestry, go to Trees in the top banner, then click on “Create and Manage Trees.”

You’ll see the list of trees that you own. This is where all of the trees that you create live.

At the far bottom, you’ll see the prompt to create a new tree. Click there.

Next, you’ll see a blank tree.

For the home person, you can enter your match’s name, but be sure to list them as living so you’re not revealing private information.

After adding one parent, you’ll be prompted to save and name the tree. Both the tester, who is designated as male by the Ancestry icon, and his father are either both living, or private, so I’m simply entering the surname of Robinson based on the grandfather’s surname. That could be incorrect of course, but it’s all I have to go on – yet.

Ironically, their grandfather’s surname was spelled Robison, without the “n”, not Robinson, but I accidentally entered Robinson and still got where I needed to go.

Clearly, I’m not going to allow this tree to be viewed by others, aka public, so I’m not checking that box. If it’s checked by default, uncheck it.

I don’t make my quick-and-dirty trees public because they are entirely unproven and unverified. I’m literally quickly searching for hints with every intention of abandoning the tree when I’m finished. If you want to clean the tree up later, you have the option to change the tree’s privacy settings.

Information in Your Match’s Tree Might Be Wrong

Complete the tree to be the same as your match’s tree. After saving your tree, click on the individuals you’ve added to view their hints.

Let’s start with Earl Townsend who appears to be our best candidate based on location.

Earl Russell Townsend has 13 hints, including a marriage license that confirms his birth date and location and provides the names of his parents, plus his wife’s name as Mildred Thorstenson. Based on what we know already, this is probably the correct Earl Townsend.

Of course, the wife’s surname could be incorrect. It could be her first or second marriage, or she could have been a widow when they married, so this surname might not be her birth surname.

Look for additional records in Earl’s hints.

Russell’s death certificate confirms that information, as do the birth and death certificates of their children.

Accept those hints.

If you determine that the original information in your match’s tree is incorrect, you’ll want to correct it in your quick-and-dirty tree. Remember, this is a scratch pad – you can’t hurt this tree.

Let’s change Mildred’s name to reflect her birth surname.

I refined Earl’s wife’s name to Mildred Thorstenson, which then produced 12 hints for her, including her marriage and Social Security record, with her birth and death dates, and her parents’ names. Her name in my match’s tree of Mildred Ideal Thorstenson Townsend Smith had produced zero hints.

Additionally, census records showed Mildred with her parents.

These seem to align, so accept those hints.

Looking at the pedigree view of my quick-and-dirty tree, we now see that both Russell and Mildred’s parents identified in the records are suggested as their potential parents.

Review each suggestion. If they look accurate based on the records identified, accept those potential parents in order to view the next generation.

Based on these names and census information, I can eliminate the Thorstenson line. It’s Swedish, not German or Dutch, which comprise my mother’s northern Indiana lines, My mother has no known Swedish ancestors, and we have proven her Indiana lineage in this timeframe.

Accepting the hints for the parents of both Earl Townsend and Mildred Thorstenson, parent hints appear for John Townsend and Eva Martin.

Now we’re viewing the next group of hints, which would be the great-great-grandparent generation. If these are our common ancestor, that would mean that I’m third cousins with my match, which is beyond the predicted relationship range. Third cousins is not impossible, but it’s beyond the probable match level based on the amount of shared DNA. furthermore, I don’t recognize any surnames.

So, let’s move to the Robison (incorrectly spelled Robinson) line and step through the same process. We can always come back and work with more parental hints on the Townsend/Martin line if we need to.

Rolland Robison only has a death year in my match’s tree, and that combined with the misspelled surname meant he had no hints on Ancestry, so I clicked on “Search” in my quick-and-dirty tree.

I’m searching for a man by this name, with a wife whose first name is Chloe.

AHA!

There it is! Note that Ancestry found Rolland Robison, not Robinson, married to Chloe.

Chloe was a Ferverda. My mother’s father was John Ferverda, and the location is correct for this family.

I saved this record to Rolland Robinson and added Ferverda as Chloe’s surname in our quick-and-dirty tree. This provided Rolland with 12 hints.

Adding Ferverda as Chloe’s surname provides her with a dozen hints too, including potential parents, Hiram B. Ferverda and Evaline Louise Miller – my great-great-grandparents who are indeed the 2C generation.

These common ancestors fall within the expected amount of shared DNA for second cousins, so this aligns well.

My quick-and-dirty tree has revealed at least one pair of common ancestors. Could there be more common lineages? Yes. I would continue building out this quick-and-dirty tree for (at least) another couple of generations on the other lines just to be sure.

What Next?

That depends on what you want to accomplish and your genealogy goals.

I used a DNA match at Ancestry in this example, but your match might be at a different vendor. Regardless, you’ll still want to use Ancestry to build your quick-and-dirty tree based on how they present hints and potential ancestors.

Now that you know how your DNA match connects:

  • Minimally, make a note on the match that indicates the most recent common ancestor(s) identified. I include a link to the quick-and-dirty tree I’ve created.
  • You can add your match and their ancestral path to your common ancestor into your own tree at whichever vendor where the match occurs.
  • If you match at either FamilyTreeDNA or MyHeritage, both of whom provide segment information, I suggest painting your matching segments to DNAPainter.

Painting your segments identifies your matching segments as descending from those ancestors and makes it easier to identify the shared ancestral lineage of anyone else who shares that segment on the same side of your tree (maternal or paternal).

Word of caution here: You can potentially share multiple ancestral paths with any match, so different segments with one match can descend from different ancestors.

  • If your match is at FamilyTreeDNA, you’ll want to link your match to their place in your tree.

Using triangulation, FamilyTreeDNA utilizes linked matches to assign matches who share the same segments to the maternal or paternal side of your tree (or both) using triangulation.

  • You may be trying to break through a brick wall by identifying common ancestors BETWEEN your shared matches that aren’t in your own tree.

This approach is obviously easier the closer your brick wall is in time to the present. Great-grandparents, at the second-cousin level, and great-great-grandparents at the third-cousin level are much easier than 5th- or 6th-generation ancestors who lived before birth and death certificates and detailed census records existed.

Furthermore, the further back in time, the more likely that you may encounter:

  • Pedigree collapse, where the same ancestors appear more than once in your tree
  • Or you share multiple common ancestors with your matches

Of course, there’s always the possibility of endogamy too, where you descend from a historically heavily-intermarried population, such as Ashkenazi Jews or the Amish, for example, which means you may share segments passed down within the population from distant common ancestors you won’t be able to identify. While endogamy in your lineages may increase the amount of shared DNA, which in turn can skew relationship estimates, it won’t prevent you from using quick-and-dirty trees to locate common ancestors.

And finally, unexpected parentage or issues like record destruction may impede your progress, but you’ll never know if you don’t try, which brings us back to the purpose of quick-and-dirty trees.

Building a quick-and-dirty tree is the easiest way to grow your matches’ trees to reveal your common ancestors.

_____________________________________________________________

Share the Love!

You’re always welcome to forward articles or links to friends and share on social media.

Subscribe!

If you haven’t already subscribed, it’s free. You’ll receive an e-mail whenever I publish by clicking the “follow” button at the top of the main blog page, here.

Help Keep This Blog Free

I receive a small commission when you click a vendor link in my articles and purchase that item. This does NOT increase your price but helps me keep the lights on and this informational blog free for everyone. Please click on the affiliate links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

Lifting the Mius and Guidry Men Out of the Shadows: The Gallows Didn’t Win – 52 Ancestors #483

Say Their Names

  • Jacques Mius (c1688 in Nova Scotia – November 2, 1726 in Boston)
  • Philippe Mius (the third) (c1703 in Nova Scotia – November 2, 1726 in Boston)
  • Jean-Baptiste Guidry Sr. (c1684 in Nova Scotia – November 2, 1726 in Boston)
  • Jean-Baptiste Guidry Jr. (1712 in Nova Scotia – November 2, 1726 in Boston)
  • John Missel (unknown birth – November 2, 1726 in Boston)

Merligueche

The devastating events that snuffed out the lives of these four men and one boy began on July 28, 1723, here, in Merligueche Harbor, now Lunenburg, Nova Scotia, where Jean-Baptiste Guidry Sr. and Philippe Mius (the second) (c1660-after August 25, 1726) lived and were raising their families. Philippe had a trading post nearby.

Both Philippe and Jean-Baptiste were French Acadians. Philippe Mius married two Mi’kmaq women and had lived among the Native people for decades. Jean-Baptiste Guidry Sr. married Madeleine (Madelaine) Mius around 1720, the half-Mi’kmaq daughter of Philippe Mius and his second wife, Marie. They too lived in the Mi’kmaq village at Merligueche.

Jacques Mius and Philippe Mius (the third), sons of Philippe Mius (the second), were half Mi’kmaq, and were called “Indians” by the English, while Jean-Baptiste Guidry Sr. and his half-Mi’kmaq son by the same name were both referred to as “French.”

John Missel was an Indian man, according to the English records. His name is probably substantially misspelled, given that both Mius and Guidry are, and Jacques Mius is called James in the English records.

July 28, 1723

In 1723, New England was engaged in Dummer’s War with the Wabanaki Confederacy, which included the Mi’kmaq, particularly those living in New England as opposed to Nova Scotia. The Massachusetts government, along with the fishermen, were afraid of losing access to their lucrative Nova Scotia fishing waters, so naval galley ships were sent to patrol the Nova Scotia coastal waters.

On July 28, 1723, English Commander Joseph Marjory was patrolling the Nova Scotia coastline when he captured a group of seven people, according to the ship’s log, after anchoring in Merligueche Harbor. This family band, far removed from New England, had not been involved in warfare.

Commander Marjory labeled the three adult men and four children broadly as “Indians,” conveniently ignoring their European or mixed-European heritage. The children were aged 16, 10-12, and two younger children around 7 or 8. Yes, children were taken as hostages for leverage.

Among those kidnapped were François Mius, about 23, the son of Philippe Mius, the second, and Paul Guidry, about 22, the son of two French parents, Claude Guidry and Marguerite Petitpas. Paul Guidry was the brother of Jean-Baptiste Guidry who was married to Madeleine Mius, the daughter of Philippe Mius. The others were probably family members as well, but historical records have not confirmed their names.

François Mius, born about 1700, was one-half Mi’kmaq, and Paul Guidry, born about 1701, was entirely French, although he was born at Merligueche, as confirmed by his Catholic baptism record. He grew up among the Native people and the Mius family.

On October 3, 1723, the Boston News-Letter reported that a provincial sloop had sailed into Boston Harbor carrying “seven of the Cape Sable Indians on board, who were all sent to prison.”

But 1723 wasn’t the first time that both the Guidry and Mius family members had been kidnapped.

Dummer’s War Was Declared

There was another group of Guidry brothers, reportedly Augustin, Paul, Claude and Philippe, and their families who were kidnapped in 1722, shortly after Dummer’s War was declared on July 25th.

Paul Guidry and his wife Anne Marie Mius had their daughter Judith while being held in confinement in Boston, and Augustin Guidry and Jeanne Hebert had twins Hélène and Marie-Josèphe Guidry while confined in Boston in January of 1723.

The Guidry patriarch, Claude, then 75 years old, was also captured and performed an emergency or conditional baptism, called an ondoiement, done when no priest was available. His wife, Margaret Petitpas, about 62, and also French, probably delivered her granddaughters. At least some of these family members were returned to Nova Scotia, one way or another, in 1723, sometime before September 26th when the twins’ baptisms were recorded in the Grand Pre parish records.

If you’re heaving a collective sigh of relief – don’t.

Not everyone was released, and by the time that this powder keg exploded in August of 1726, the families had waited for more than three years.

The Interminable Wait

For three agonizing years, 1,124 days, their families sought their freedom, expecting them to be released anytime, like the Guidry family had been in 1723 after being held for a year. That’s what “normally” happened, but not this time.

Finally, on December 15, 1725, a peace treaty was signed in Maine, and hostilities related to the Dummer War ceased, but that treaty did not include all parties.

When word of the treaty arrived in Merligueche, they were hopeful. Surely their family members would be arriving home soon since hostages were no longer “needed.”

Yet no ship arrived on the horizon.

No hostages appeared.

The days dragged on.

An additional treaty was signed in Nova Scotia in June of 1726, but word spread slowly, and full peace was not reached until the summer of 1727.

The Acadians and Mi’kmaq had lost faith in the promises of the English – their long-time, sometimes clandestine, trading partners.

Still, no one returned, and no word came either.

Day by day, every single day, they waited and prayed to the Catholic God, and the Great Spirit.

Were the hostages even still alive?

Sane?

What had happened?

Were they ever coming home?

Letter to Philippe

My dearest ancestor, Philippe,

I did not understand why you sent the winds to summon me to Merligueche two summers ago.

I learned, as we sailed along the coastline, that this is where your village stood more than 300 summers before. Where you lived, and loved, and grieved endlessly.

Where I walked the very land you refused to leave during the hunting moons because the English ships might return your family – and you wanted to be there, waiting, to greet them and rejoice.

Where you called me to wait for their spirits with you.

Nothing was more important.

I did not know, when I laid my hand, wearing the ring that belonged to your granddaughter, my mother, on Paul’s stone in the cemetery, with 1754 neatly carved beneath the cross, who he was – and what he had endured and survived.

I did not know that Paul Guidry married your daughter Anne Marie Mius.

Paul was known as LaVerdure, which the English heard as “Labrador,” so later in his life they called him “Old Labrador,” before he was buried here on the sacred land at Merligueche.

I did not understand the aching in your soul, the desperation for François. How could you have known that he would one day become a Chief, a leader of his people, and that during his time in Boston he was iron being forged into steel by the fire? All you knew was that he was your son, being held hostage, in the worst of conditions, in a faraway world that he didn’t know and could not escape from.

Now I know why you called me.

I answered then.

I’ve answered now.

Life has come full circle.

Your blood is in my veins.

Two years later, your invisible hand pushed me across the waters to Boston.

To do what you could not.

Kidnappings and Hostages

In August 1726, Captain Joseph Decoy from Cape Breton had been trading in Boston when his son was taken and detained for some reason. Distraught, Capt. Decoy stopped at Merligueche, probably at the trading post. He told the people there what had happened and that he thought the only thing that would secure the release of his son was seizing a Boston vessel and trading it in exchange for his son’s freedom.

That’s the way life worked in the French and English colonies, both of which had been established on Indian lands.

Apparently, the people living in the village at Merligueche, after 1,124 days of fruitless waiting for their relatives to be released, were at their wits’ end too, and Capt. Decoy either planted or perhaps watered a seed.

On August 25, 1726, the English fishing vessel, Tryal, captained by Samuel Daly (recorded as Doty in the trial record), sailed into the harbor at Merligueche, where he invited several villagers, including the Mius and Guidry men, aboard to drink.

Philippe Mius (the elder) did not drink, nor did he stay on board after greeting Daly with a friendly handshake, unlike the others, who remained to imbibe with the crew. Jean-Baptiste Guidry Sr.’s mother also begged the Merligueche men not to stay on board and share the English sailors’ rum, but her warning, too, went unheeded.

One thing led to another, as described in my article, Philippe Mius (c1660 – after August 1726), Disaster, Piracy and the Dead Man’s Jig, and under the influence, it seemed like a good idea to do exactly what Capt. Decoy had suggested.

Who can blame them after more than three years of fruitless waiting for François Mius, Paul Guidry, and perhaps others to be released? By this time, any hope garnered by the 1725 peace treaty in Maine had quickly faded. Days turned into months, and months had dragged into years.

However, things didn’t go exactly as the Merligueche men had anticipated in their alcohol-fueled bravery. The English crew regained control of the ship before even leaving the harbor, tied Jacques Mius, Philippe Mius (the third), Jean-Baptiste Guidry Sr., Jean-Baptiste Guidry Jr., and John Missel below deck in ropes, and headed straight for Boston with their drunken trophy “pirates” that were, in fact, political prisoners. This type of back-and-forth capture, trade, and release of prisoners had been going on for decades. Except that, unlike others, François Mius and Paul Guidry had been held and languishing as prisoners at Castle William for an exceptionally long time and not released.

The English were not playing by the unspoken rules.

In addition to the men being transported to Boston, three other “Indian” men jumped overboard when the English regained control of their fishing sloop. Being about four miles from shore, they may have drowned, although one report states that they survived. Unable to escape, the wife of one of those men described as a “squaw” and two “papooses” remained on board and were taken to Boston with the male captives. If she ever saw her husband again, I’m guessing she had a few choice words.

We don’t know the identities of the woman and children, or what happened to them after the trial a few weeks later.

Philippe was now left staring at the endless horizon, which, in addition to having already swallowed François, Paul, and five others three years earlier, had now consumed two more sons, his son-in-law, grandson, another man, woman, and two additional children.

His heart must have sunk in his chest, heavy with grief and foreboding.

Family Members

Various Mius and Guidry family members were taken hostage in multiple kidnappings. I can’t help but hear the phrase, “If it weren’t for bad luck, I’d have no luck at all.”

Keeping track of the players is confusing, so I’ve assembled a color-coded chart.

The children of Philippe Mius and his Mi’kmaq wife, Marie, who were known to be kidnapping victims in these episodes or were married to hostages, are shown at left.

Claude Guidry and Marguerite Petitpas’s children are shown in a column at right. Both couples had children who were not known to have been involved in the hostage episodes, and those children are not shown.

Two Mius daughters married two Guidry sons. Madelaine (Madeleine) Mius married Jean-Baptiste Guidry Sr. dit Gravois and Anne Marie Mius married Paul Guidry.

The peach background color identifies known captives of the first kidnapping in 1722, where several Guidry family members and their families were taken. At least some were released in 1723, but perhaps not all.

The blue background color indicates known captives taken in July of 1723 who were still being held in 1726. There were more people kidnapped who were assuredly family members, but we don’t know their identities, nor do we know when François and Paul were eventually released. The records are silent until at least 1730 for Paul, and longer for François.

Paul Guidry was either kidnapped twice or never returned from the 1722 kidnapping. We know he was still held in the fall of 1726.

The names in bold red were captured in August of 1726 in Merligueche and hanged in Boston that November.

Boston

Prisoners who had allegedly committed crimes were held in jail while awaiting trial, but hostages, like the men taken in 1722 and 1723, were shipped to fortified Castle William on an island in Boston Harbor, where escape was not only improbable, but nearly impossible. That said, records from 1724 contain details about an incident in which a group of “Indian Hostages” successfully staged an escape from Castle William. Given the currents in the bay, I wonder if they survived, especially considering the physical conditions of the men held there and the island’s isolated location in the harbor. Could any of these brave escapees have been our Merligueche men?

François Mius, Paul Guidry and the other captives were held under deplorable conditions. Paul may have remained from the 1722 captures or could have been recaptured just a month or so after his 1723 return. In other words, by 1726, he had been confined there either three or four years.

Castle William was a stone military fortress, and the hostages were valuable pawns, diplomatic chess pieces, not men awaiting trial. There was no intention of releasing them, and only enough care was taken of them to keep them alive. Dead hostages aren’t useful.

Budgets reflected their fare of bread, salted meat and peas, along with colonial clothing such that they would not freeze to death.

They were fed, but experienced total isolation from everyone and everything they knew.

For three long years, and maybe more.

How did they not go mad?

In 1723, the men on board Marjory’s warship would have watched as they sailed directly into the harbor, dropping anchor at Castle William where their family members had been held after the 1722 kidnappings. Some may still have been languishing there.

Knowing what to expect, fear must have gripped the captives’ throats with its icy hands, but at least they had each other.

They, or their family members, had been here before and had tales to tell.

Their climb up this incline from the sea, with muskets or knives at their backs, was probably the last time they were outside these walls for more than three years – although we don’t know how much more than three years. For all we know, it could have been many more years of unjustified captivity.

Paul Guidry, if he had not been released earlier in 1723, would have been both thrilled and horrified to see his family members being ushered through those doors at knife- or bayonet-point, their hands bound.

How many of the people who entered this door walked out again? How many were carried in a wooden box or whose remains were simply tossed into the sea?

What horrors did they endure?

What about the women and children who were held here?

I shudder to think.

It’s worth mentioning that our last record of patriarch Claude Guidry is the twins’ official baptism entry in Grand-Pré that September where the parish record notes that he had given them ondoyée baptisms after their births here in January 1723.

Hostages were typically not held in dungeons at Castle William unless they were deemed uncooperative or unruly, but they were closely guarded within the barracks and parade grounds.

They probably looked up into the salt air, when they could, and wished themselves to be a seagull, lifting over the tops of the walls and following the waters of the Atlantic back to Merligueche.

Merligueche must have seemed like another time and place. Long ago. A land of their dreams.

Both François and Paul were in their early 20s, and while their more than three years spent here were undeserved and certainly unpleasant, to say the least, they were both honing survival skills that would serve them well for the rest of their lives – not the least of which was learning English.

François and Paul ultimately survived, but we have only silence about the rest.

Photo courtesy of Katherine Borges

How ironic that the flight path for planes arriving at Boston Logan Airport tracks right over the castle, named Fort Independence today. Escape – so close and so far into the future.

Is the reason we never learned the identity of the rest of the hostages because they died here?

I scattered flower petals that I had brought with me on the water, with a white feather that was gifted from above, for the souls who suffered and died at Castle William, perhaps attempting to escape – and for the soul of Philippe, the tortured father, who was suffering on the shores of Merligueche.

Boston

During the first week of September 1726, following the episode in Merligueche that resulted in the eight Acadian and Mi’kmaq captives, the ship Tryal sailed straight into Boston Harbor from the Atlantic, directly past Castle William.

The captives on board the Tryal would have watched as they passed Castle William, if they were allowed above deck. They would have known that their family members that they had been trying to free were suffering there.

Those men, beloved family members, whom they risked their lives to save, were within mere feet, yet they could not see them. In fact, they would never see them again.

The ship passed both Governors Island and Bird Island on their right, both within sight of Castle William and part of Boston’s Logan Airport today.

These two historical 1700s maps of Boston and the harbor are overlaid on a current map showing greyed-out ghostly images of future development, including the airport beneath most of Bird Island. Boston was significantly smaller then. Much of Boston and all of East Boston adjacent to the airport is built on fill.

Bird Island had mostly washed away before the airport development began in the 1930s and 1940s and had evolved into Bird Island Flats. The northwesternmost tip is marked today by an orange buoy in the harbor. The pointed Skyline Memorial is visible behind the buoy, at far left, with the airport runway and shipping terminals behind the tree and to the right.

These are the remnants, beneath the fill, of Bird Island.

Of course, the Boston skyline as seen from Bird Island today looks nothing like it did in 1726, but Long Wharf remains across the harbor, nearly indistinguishable in the picture, just slightly to the left of the buoy.

Click to enlarge any image.

The purpose of Skyline Monument is to orient visitors to what they are seeing across the water.

The ship Tryal with our unwilling passengers anchored along Long Wharf, which is found in the monument section below the white flowers on the railing at right if you zoom in.

The water near the Boston shoreline was too shallow for ocean-going vessels. It was mostly mud flats at low tide, hence the need for Long Wharf to be so, well, long, extending some 2,000 feet into the water, reaching well beyond the low tide mark.

Boston was the center of commerce in colonial New England. Merchants and traders maintained their businesses along the wharf, which transitioned directly into King Street, leading to the Old State House, and past that, the jail, then spelled gaol.

Most of the time, the ship’s captain would go directly to the customs house, unless he was smuggling, of course – but not on that day.

Nope, that day, Captain Daly had something much more valuable than fish to declare. He had pirates, five of them, plus an accidental “squaw” and two “papooses,” but they could be useful barter too.

Indeed, it was his lucky day. He was probably so excited that he “accidentally” forgot to declare his cargo!

The hostages would have been bound with ropes and marched through the street, like trophies, shepherded by proud-as-punch Capt. Daly, straight up King Street to either the State House or the gaol, as shown on this 1722 map.

Minus today’s modern innovations, the harbor as seen from the end of Long Wharf looks much the same. The tall building directly across the harbor to the left of center is the Hyatt, which stands on what was once Bird Island, beside the Skyline Memorial.

A walk down Long Wharf is a stroll through time, past the old Chart House, now a historic restaurant.

Jacques and Philippe Mius, both Jean-Baptiste Guidry Sr. and Jr., father and son, John Missel, and an unnamed Native woman with her two children walked this exact same path.

They were probably justifiably terrified.

Perhaps at night, past the bustling waterfront taverns, in a darkened street, enveloped by fear.

The children cried. The men wanted to.

Perhaps the State House in 1726 held a lantern in the cupola.

Just beyond the State House lay their final destination for the next few weeks anyway: the jail, drawn on the map as the prison.

Where were the woman and her two children taken? Did anyone have mercy, or were they “just Indians,” dispensable and disposable?

Did Jacques and Philippe Mius, Jean-Baptiste Sr. and Jr., and John Missel know that they were going to be tried as pirates? I’d wager that they did, and everyone knew what happened to pirates. Maybe they thought their trial would be different, because they weren’t actually pirates.

The Boston jail was a horrific place, described as a forbidding, dark stone building with “outer walls three feet thick, unglazed windows barred with iron, the cells partitioned off with planks, and the cell doors covered in heavy iron spikes. The passageways like the dark valley of the shadow of death.”

And that was not written by a prisoner. Imagine the experience of someone confined there and what they would have to say.

Daniel Fowle, a Boston printer, in his Total Eclipse of Liberty, said of the gaol, “If there is any such thing as a hell upon earth, I think this place is the nearest resemblance of any I can conceive of.”

I’m sure that Jacques, Philippe, both Jean-Baptistes, and John can attest to Hell on Earth. That, combined with the overwhelming dread of what they had to realize was coming.

The word of either a Frenchman or an Indian would never be believed against the triumphant deliverance of “pirates” to Boston by an English captain for a showy trial.

Today, Queen Street is Court Street, and the entire area from the street to the rear of the present-day 26 Court Street is occupied by the Old City Hall Annex, at far right. You can see the Old State House just a block away, now dwarfed by surrounding skyscrapers, where the Mius, Guidry and Missel men would be taken to be tried.

I use the word “tried” very loosely, because wouldn’t you know it, their case would be heard by William Dummer himself, of Dummer’s War, in the Vice Admiralty Court, which was structured in a way that essentially presumed one’s guilt unless you could prove yourself innocent. Oh, and by the way, jury trials were prohibited.

This is not going to go well.

I realize this is “only a sunbeam,” but I like to think that maybe their spirits were not snuffed out and that they remained to protect others from injustice.

The Eclipse

It was around noon on September 14th, 1726, and people were partaking of their midday dinner when the sun began to grow dim, casting an unnatural gray pallor over the Boston streets. Today, we know it was an eclipse, and nothing to be afraid of, but they didn’t know that then.

People looked up, reacting in fear as the sun was still present in the sky, yet was being swallowed by an evil darkness. The five men in the jail cells would probably not have been able to see the sky, but they would have heard their frightened jailors.

An ominous omen.

However, François Mius and Paul Guidry at Castle William would have seen the eclipse and probably understood its meaning all too well. To them, it foretold death.

In Puritan New England, an eclipse was widely interpreted as a direct warning from God. It was, indeed, just that, an omen that they were about to bloodstain their own hands.

The “Trial”

Witnesses, meaning the crew, were publicly called by the cryer to testify about “acts of Piracy, Felony and Robbery committed on board the Sloop Tryal, by John Baptist Jedre, alias Laverdure, John Baptist Junior, James Mews, Philip Mews and John Missel.”

Not only that, but to further inflame the situation, and justify the results, the devil was brought into the mix.

For that the said John Baptist Jedre, alias Laverdure, and John Baptist Junior, Not having the Fear of GOD before their Eyes, but being Instigated by the Devil, on the Twenty Fifth Day of August last, about the Hour of Two in the Afternoon of the said Day, together with James Mews, Philip Mews, John Missel, Indians, and others, in or near Mallegash Harbour…

Puritans viewed New England as holy ground carved out for them to build a godly society. Crimes like piracy, murder, and witchcraft were viewed as literal covenants with the Devil that polluted the community.

The men assuredly knew the charges were woven around details that may or may not have been entirely accurate. And introducing “the Devil” just inflamed everything.

“I move for dismissal, Your Honor, on grounds of prejudice. The “Devil” has poisoned this trial,” but there was no one to say that, and the Puritans certainly wouldn’t have believed it anyway. Not to mention that no one cared about a fair trial. This took place just over 30 years after the last of the Boston and Salem witch trials.

On the morning of October 4th, the two Guidry men, father and son by the same name, heard the key turn in the lock of their spike-studded jail cell door. They were probably chained as they were marched to the Old State House.

They may not have seen each other in the month since they had been placed in the prison’s dungeon.

The light would have blinded them as they emerged from the darkness.

The Old State House was badly damaged by fire in 1747, with only the brick exterior remaining, so we don’t know exactly what it looked like in 1726, although this 1791 sketch is probably close.

It was here that their fate would be sealed by men speaking a language they did not understand.

Records tell us that they would have been marched inside the building, and up the stairs. They were tried on the second floor where they would have heard the muffled voices of traders and merchants conducting business beneath them, on the building’s ground floor.

By Bestbudbrian – Own work, CC BY-SA 4.0, https://commons.wikimedia.org/w/index.php?curid=51534885

Dummer would have been seated at the head of the table, along with the rest of the wealthy merchants and politicians hearing their case.

Did the accused men even get a seat at the table?

Photo courtesy of Katherine Borges

Were they banished to the side of the room, looking out the window at the freedom they would never know?

Photo courtesy of Katherine Borges

Perhaps staring at the church across the street, wishing it were Catholic, and that they could seek shelter and solace there. Did they pray as they heard the voices that would condemn them drone on in the background in a foreign tongue they did not understand?

Indeed, many people entering the State House, where lives were changed in an instant, needed to pray, either entering or exiting, or perhaps both. Of course, Catholics would not have been welcome in the Puritan church.

Perhaps God, by whatever name, heard them anyway.

The old brick church, long gone, stood diagonally across from the Old State House, where the tall building with the arched windows stands today.

The lintel above the door indicates that this was the site of the first meeting house in Boston, where its replacement, a brick church built in 1712, stood in 1726.

During the trial, we learn that Jean-Baptiste Guidry Jr. was only 13, turning 14 that fall, and that the Guidrys did not understand English and requested a French interpreter. A local Huguenot was summoned.

The court decided that since young Jean-Baptiste was not a “madman,” he was old enough to be responsible for his actions.

The sentence, a foregone conclusion, was then pronounced:

You…are to go from hence to the place from whence you came, and thence to the place of Execution, there to be hanged up by the Neck until you are Dead, and the Lord have Mercy upon your Soul.

After Sentence was given against the Prisoners, the Marshal of the Admiralty was Ordered to remand and keep them in safe Custody within His Majesty’s Goal in Boston.

As the father and son left the State House with the guards, life outside continued as it had that morning. Horses and carts and people making their way along the streets, attending to their business.

Everyday, mundane life.

But they probably sounded different, because the father and son knew they would not hear those sounds for long. They would never hear the precious voices of their family, or the sounds of their beloved woods, again, either.

Someone assuredly informed Jacques and Philippe Mius, and John Missel back in the jail what had happened at court. The guards may have taken glee in the men’s misery.

The next morning at 10 o’clock, their cell doors clanged open, and it was their turn to walk the long block to stand before the tribunal.

Photo courtesy of Katherine Borges

The charges were read, in English, of course:

For that the said Philip Mews, James Mews, and John Missel, not having the Fear of GOD before their Eyes, but being Instigated by the Devil, on the Twenty Fifth Day of August, last, about the Hour of Two in the Afternoon of the said Day, together with John Baptist Jedre, alias Laverdure, John Baptist Junior, and others, in or near Malegash Harbour…

Ironically, the Mius men had an Indian interpreter, not a French one. Their court-provided advocate asked for time to prepare a proper defense, and he was so generously given until 3 that afternoon.

By the end of the same day, two hours later, they too had been found guilty, with absolutely no regard for the fact that at least eight of their family members had been held for a year in 1722-1723, and seven more had been kidnapped in 1723, of which at least two were still being held at Castle William.

If the two Jean-Baptiste Guidrys, Philippe and Jacques Mius, and John Missel were supposed to abide by the December 1725 treaty, which is what qualified their behavior as “piracy,” then why weren’t the Bostonians?

Why hadn’t François Mius and Paul Guidry been released from Castle William and returned to Nova Scotia?

Why wasn’t any of that considered?

Apparently, the “rules” applied only to one side, and not the other.

Why were the accusers allowed to testify, but the accused men’s explanations were discounted and dismissed, along with the circumstances surrounding the hostages?

Was justice ever the goal? Or was this always meant to be an elaborate vengeful performative political spectacle dressed up as justice?

The identical verdict awaited Jacques and Philippe Mius, and John Missel, word for exact word.

This begs the question of how much François Mius and Paul Guidry, confined helplessly at Castle William, knew about what was going on. Humans love to gossip, so I find it difficult to believe they were unaware.

François and Paul were probably equally thrilled that their families hadn’t forgotten them, or given up on obtaining their freedom, and at the same time utterly horrified. Devastated that they had essentially sacrificed their lives for nothing.

This dreadful soap opera wasn’t over yet.

In the words of Marcus Rediker, Boston and other cities “staged spectacular executions” of pirates. Five pirates, all to be hanged on the same day, would be a sight to behold. Top-flight entertainment for everyone to look forward to. A public holiday.

Sickening.

Utterly sickening.

Between the Gavel and the Gallows

The walk from the Old State House back to the prison seemed like it was into another dimension for the four men and one boy whose lives would be ended. Not justice, but injustice, revenge, had been meted out that day. They were dead men walking.

The clock was ticking, day by day, hour by hour, until their lives would be snuffed out.

They probably didn’t know which day they would die. Would it be sooner, or later? Who would decide?

Gallows had to be constructed for five executions. We don’t know whether one executioner’s platform or five separate ones were built while Boston Town watched in anticipation of the blood-sport being prepared for their mass consumption.

Just three months earlier, William Fly only had to wait eight days after his verdict before he drew his final breath.

There were no such things as appeals. Often the length of time between the sentence being passed and execution carried out was dependent on how successfully the Puritan ministers were in their spiritual counseling delivered inside the jail cells of the condemned. But these people weren’t Puritans. They were Native Americans and Catholics. The Catholics had spent the past century trying to convert the Native people. We know the Guidrys were Catholic, but the mixed family members may have practiced some combination of Catholicism and Native American traditions.

Were they afforded any religious comfort, such as Last Rites, or were they treated as less than human?

Was the promise of the Puritan version of life after death powerful enough for them to recant their beliefs?

Ironically, Puritan minister Cotton Mather, who is entombed in Copp’s Hill Burying Ground near the Old North Church, within sight of where they were hanged, was fascinated by pirates and visited them often in the gaol, attempting to extract confessions and convert them. He ultimately published several treatises about piracy and conversion, so it’s unclear how much of his zeal was concern for their souls, fodder for his pulpit and books, or fascination with the spectacle of hanging itself.

Then on the morning of November 2nd, 28 long days later, the cell doors creaked open for the final time.

Did they know in advance that this would be the day?

Their appointed date with the Grim Reaper had arrived.

Were the men hopeful of a final miracle, or were they resigned to their fate?

The Execution

I’ve learned a lot more than I ever wanted to know about executions since writing Philippe Mius’s original article, and I’ve since traced their footsteps on that fateful, final day.

Because Philippe Mius (the third), Jacques Mius, Jean-Baptiste Guidry Jr. and Sr., and John Missel were convicted of piracy in the Vice Admiralty Court, tradition required that they be hanged over the water. The Diary of Jeremiah Bumstead tells us that executions occurred on the mudflats near the Charlestown Ferry between the high and low tide marks.

Execution day was a much-anticipated social event – for the attendees – not for those unfortunate men at the center of this carnival-like spectacle.

Nearby towns were emptied of residents as they flocked to Boston. Businesses closed, except for taverns, of course, and vendors sold food, drinks, and printed copies of execution ballads to the gathered crowds.

Preachers often appeared, using the convicted as examples to convert the flocks.

Everyone lusted for morbid last dying speeches, waiting breathlessly to see what would happen.

Would the men break?

What would they say?

Peasants and laborers watched from the crowded shore or the mudflats, but the wealthy secured prime seating or even watched from their boats in the river for a premium view.

Enslaved people and indentured servants were encouraged, permitted, or perhaps forced to attend in order to internalize the lesson of complete, unquestioning obedience.

Based on historical records of Boston’s pirate executions and admiralty customs, we can glean what their last day would have been like.

On the morning of their executions, the men would have been taken from the Boston gaol and placed into open wooden carts, sometimes alongside their own coffins, then paraded through the packed streets, lined with jeering residents and visitors.

The town drum corps marched ahead of them, beating a slow, ominous rhythm to alert the neighborhoods that the condemned men were approaching so the residents could hurry to watch.

The procession started at the gaol and moved slowly past the Old State House so the authorities could watch, then threaded through the North End’s narrow streets that were most heavily populated.

The condemned men were paraded around the city so everyone could take their turn seeing the spectacle. Hostility and violence were actively encouraged by the Puritan authorities, who wanted the public to vocalize their hatred for “sin” and rebellion – qualities it was believed that these four men (and one boy) represented in the flesh.

What a macabre parade.

People crowded the doorsteps, leaned out of second-story windows, and packed the cobblestones. They aggressively shouted insults, cursed the men, and openly spat on them as the carts rolled slowly past, bumping along the cobblestones, giving everyone ample opportunity to desecrate their bodies.

The lower-class spectators typically pelted the prisoners in the carts with mud, rotting produce, dead animals, and stones scraped from the street’s gutters. The “guards” did nothing to stop this, as it was viewed as part of the public penance.

I shudder to think of the example this set for children. Whatever happened to messages that would be preached from the pulpits on Sunday, like “love thy neighbor,” and being kind?

The merchants viewed pirates as an economic threat, but these men weren’t pirates in the traditional sense. Their “crime” was about something different altogether, and the fact that François Mius and Paul Guidry were still sitting at Castle William was evidence that the English had committed the exact same crime – and that crime was still in progress. Yet, there was no justice, and no accountability for them. Someone needed to hold a mirror!

The regular townspeople saw the prisoners as lawless, bloodthirsty outlaws who had broken both the laws of the King and the laws of God. The crowd felt a righteous, religious duty to mock them and break their spirits before they reached the gallows. Cruelty seemed to be the point, the purpose, and the name of the game.

The men were probably actually relieved to be finished with that unholy gauntlet by reaching the mudflats where their execution would soon occur. And poor Jean-Baptiste Jr. That poor child.

One of the reasons that hangings occurred in the intertidal zone, between high and low tide, was that in Boston, the high tide mark was where the streets and buildings began, but where the mouth of the Charles River entered the harbor was shallow. The low tide mark extended some 1,650 feet offshore in places, nearly one-third of a mile, providing a great deal of real estate for people to gather to witness the gruesome spectacle, along with the day’s entertainment.

The shoreline has changed substantially, but the historical map overlaid on the shadowed contemporary map beneath shows the 1700s shoreline, with the buildings in red, and the subsequent development on filled land on the current map.

The procession would have passed by various cemeteries, then called burying grounds. The prisoners knew they would not be buried there.

Pirates were not wanted in Puritan cemeteries, and neither were French Catholic or Native American men. Nor were they welcome in the Old North Church, either.

As the spectacle passed by the tombstones of Copp’s Hill, descending the steep hillside as they neared the water, the men could see the harbor, river, and the mudflats where their fate awaited.

Their heartbeats must have quickened.

As they approached the streets that ran along the waterfront, they would have been able to see the gallows scaffold, towering above the water, in the distance.

Everyone could find their way to Charlestown Ferry, where the mud flats extended nearly halfway across the river to a narrow channel.

Today, part of the area shown as water along the shoreline on the early map has been filled and is part of Langone and Puopolo Parks, located directly across Commercial Street from the Copp’s Hill Burying Ground lower terraces. The elevation and historic shoreline don’t much matter, though, because the gallows would have been constructed well offshore so that everyone had a good view of the barbaric spectacle that they had come to enjoy.

Oh, the incredible irony of the marker that greets visitors to Langone Park, today.

Thousands of spectators lined the North End docks, and the river was choked with boats, all gathered to watch the horrible gallows performance.

Around noon, typically between 11 AM and 1 PM, the show got underway, with the ministers acting as showmen.

The convicted men, with only minutes left to live, were either forced up on a ladder or sometimes stood in the back of the cart.

With four men and one boy to be hanged at the same time, I’d bet that they were all five forced to climb onto the scaffold or scaffolds and up ladders so that the crowd could see better.

The executioner would place the nooses around their necks.

Then, everyone was “treated to” an execution sermon. Yes indeed, what could possibly have been lovelier or more inspiring? I wonder what God thought.

Next, they were forced to listen to fiery sermons by high-profile rival Puritan ministers like Cotton Mather and Benjamin Colman, often lasting well over an hour, frightening and capturing the imaginations of the attendees.

They exhorted the voyeurs by using the condemned men as “living examples” of what happens if one strays from God’s law.

Finally, the ministers pressured the desperate men standing with nooses around their necks, willing to do almost anything to delay the inevitable, to recant and repent, reading a script pre-written by the minister. This coerced final act of admitting their sins would supposedly “save their souls.”

Of course, the condemned men could have been incredibly brave, stood their ground and refused to participate in the charade, as actual legendary career pirate William Fly, who raided shipping fleets, had done just a few weeks earlier. Fly shocked the crowd with his belligerence, disdain, and refusal to comply – rather spoiling their day.

Fly’s body would still have been “hanging in chains” in a gruesome gibbet cage on Nixes Mate, an island in Boston Harbor, as a warning to others when our men were hanged.

We’ll never know what Jacques Mius, Philippe Mius, John Missel, Jean-Baptiste Guidry Sr., and his 13-year-old son, Jean-Baptiste Guidry Jr., did, or didn’t do – but I’d hazard a guess. At least, I hope they refused. They literally had nothing to lose at that point, except their very last shred of dignity.

I can’t help but wonder if François Mius and Paul Guidry were transported from Castle William to witness this horrific spectacle, perhaps being provided with up-front, close seats as a form of torture for them and the convicted men as well. One last well-planned indignity.

The hanged men’s final minutes of life, sometimes stretching into hours before death overtook them, were scenes of pure torture.

Years later, hangings occurred using the “long drop” method where the floor of the scaffold was dropped from beneath the feet of the condemned, and their necks snapped, providing a blessedly quick death.

Not so in 1726. Death came slowly.

Either the cart was pulled from beneath each man, or the ladder was removed, or the men were “turned off” of it, leaving them swinging by their necks. The weight of their own bodies caused the noose to tighten, depriving them of oxygen.

Death by slow strangulation was neither swift nor kind, but that was anticipated by the voyeurs as part of the spectacle. The men died slowly, struggling for air, while horrible involuntary utterances and agonizing moans escaped their bodies as the transfixed crowd watched in this torture theater.

Sometimes their faces were covered, and sometimes not.

In the Footsteps of the Executed

In August of 2026, 300 years later, I found those mudflats and walked in their footprints.

After passing that horribly ironic marker reading, “By their deeds, measure yours,” I stepped onto the boardwalk of Langone Park.

The bustling city around me faded into oblivion. I could feel the cold iron of the chains, the motion of the carts lurching through the streets, what they endured as their bodies were bruised and abused, and the fibers of the nooses on their skin. The absolute terror of the thirteen-year-old child who died here, the horror of relatives held on an island, so close, but so far away, and the crushing grief of a father hundreds of miles removed.

My body was in the present, but my heart was with them, almost exactly three centuries earlier.

The pain was overwhelming, but I knew I couldn’t look away. I had to stay. I had to finish what was started.

That is why I had been called here.

Summoned.

I walked to the water.

Looking to the left, the beautiful bridge crossing the Charles River to Charlestown belies what happened here.

The bridge and water were lovely in late August 2026, but not when they breathed their last here, on November 2, 1726.

Looking directly across the water, I could see both the Bunker Hill Monument and the USS Constitution, a tall ship similar to what our family members might have seen as they were carted onto the mud flats that fateful day.

Looking to the right was the vast shallow plain of mudflats that stretched out to the heavily trafficked shipping lanes, the gallows scene completely inescapable to any ships passing by.

My eyes were drawn to the shallow water, below.

I knew that it was here.

Here that they had hanged from their necks until they died, choking, deprived of air.

Swinging helplessly.

Deprived of life as thousands reveled in their misery.

These ancient timbers bearing witness.

And these.

I looked up and saw the flats, heard the roaring crowds, cheering for their murders – as they gasped, groaned and perhaps begged for mercy that would never come.

Especially the father for his son.

I found the old seawall, marking the high tide and bearing the footprints of time.

When their last breaths had forever escaped their earthly bodies, the rest of Boston went off to celebrate.

Practices of English admiralty law required the men be left to hang for a full day, as a spectacle, until three high tides had fully washed over them, submerging or battering the swinging corpses.

This ritual symbolized the Crown’s authority over the prisoners, allowing the sea to claim them three different times – because once just wasn’t enough.

The gallows did not just claim their breath; their customs demanded one final, grotesque act in this morbid theater.

The third tide would have receded around noon the following day, exposing their waterlogged bodies. The colonial marshals either rowed out to the scaffolds, or took the carts and cut the men down, hauling their soggy bodies into the bottom of boats.

Denied burial in a burial ground, Philippe, Jacques, Jean-Baptiste, Jean-Baptiste, and John were instead rowed across the harbor to Bird Island. They were buried like so much waste, anonymously, in the wet, marshy soil where no one could honor them, but where their family members, François and Paul, still held at Castle William, could suffer the agony of watching them be buried – fully comprehending the horror they were witnessing.

Not only had they failed to save them, but by trying, they sacrificed their own lives.

Back in Nova Scotia, Philippe awaited the official word, but he probably already knew.

Philippe was never heard from again.

Bird Island

I am here to stand witness and tell you that neither the state, the gallows, nor the mud won.

The pain of standing on this ground was excruciating and tore at the very fabric of my soul. But I did not come to relitigate their staged kangaroo trial that could not be won, grant them quarter for their heinous deeds, or give them yet another win.

I came to answer three centuries’ worth of silence.

Against all odds, I found Castle William, the gaol, the path they traveled, the execution site, and finally, the remains of Bird Island.

I walked there, along the Harborwalk.

I brought flowers to free their souls. The Universe added a feather. I heard the message loud and clear. So did they.

I came for Philippe, to deliver what he had been denied. As a father, father-in-law, and grandfather, he had been robbed of the right to tend his family in death, to observe the sacred rituals of walking on into the next realm, and to lay them to rest in this one.

I walked to the very end of what had once been Bird Island, before the sea whittled it down to Bird Island Flats. The Skyline Monument stands here today.

One bouquet for the graves of Philippe, Jacques, Jean-Baptiste Sr. and Jr., and John, with the buoy marking the end of Bird Island Flats in the water, at right.

One bouquet for François Mius, Paul Guidry, and unnamed others who were held hostage at Castle William, and those who died there.

A third bouquet over the mud and flats. To release their souls.

Philippe, my ancestor, I stand here for you.

We have done a holy thing.

Resurrecting their memories from the mud.

Beyond all doubt, I know the Universe heard.

And answered.

With unbounded beauty.

You were denied the mercy of their funerals and the sacred rituals of burial. You could not touch your boys, your daughter’s husband, or your grandson. You could not comfort them, stroke their faces, and wash away the cruelty they had endured.

You were left alone on the shores of faraway Nova Scotia to mourn an empty horizon for all the rest of your days.

In your stead, I did what you could not.

I brought the ritual to them and returned them to the sacred water that spirited them away.

The judges are all forgotten now, themselves turned to dust, having already answered to God.

The scaffolds, too, are gone, but the water remembers. It’s alive. That which can divide us also unites us.

Together, we brought them out of the shadows and lifted them up to the Creator.

We set them free.

We have spoken their names and honored them.

You are all free now.

Your work is done.

Your time here is finished.

Your tasks complete.

Soar with the Eagles

And touch the face of God.

The gallows did not win.

Rest Easy, Beloved Dolly Parton (1946-2026) – A Legacy of Love

Dolly’s gone, and my heart is broken. Dolly’s nephew shared the sad news with us today in this video, expressing his deep love for her.

I have shed so many tears to Dolly’s songs over the years, but none more than today. Dolly saw me through births, joy, excruciating loss, and so many deaths. Love and loss – and always a reason to get up and try again.

I didn’t realize just how deeply she was woven into my life and into the culture I grew up in until the world suddenly had a Dolly-shaped hole in it. Sometimes grief reveals the true impact of someone’s life.

Dolly was and remains the consummate ambassador of love and humanity – a role model for all.

Dolly inspired so many and lifted us up. Beloved is the only word I can think of that fits the moment.

Through unifying music and lyrics that captured the most universal human emotions, she brought people together despite their differences. She never hesitated to explain that she measured everything she did with the yardstick of love. Love determined what she stood for, what she supported, and how she lived – even when it wasn’t popular.

Everyone could understand the emotions she wrote and sang about because she had lived them, too. Her immediately recognizable Appalachian voice sounded like home to so many of us. Dolly was no stranger to poverty and hardship, and those experiences motivated her to help so many others escape similarly desperate circumstances. Once she started, she never stopped, spending decades lifting people up.

It’s like Dolly was always telling me that I could. Like a favorite auntie who always believes in you, even when you don’t have enough sense or maybe courage to believe in yourself.

I grew up listening to Dolly. Country music wasn’t my favorite genre, but Dolly was always one of my favorite artists because I could relate to everything she wrote about. She was always one of “us,” no matter who you were. Who among us hasn’t been sad or joyful? Her lilting voice carried that entire range of emotions home, reaching the very depths of our souls.

My favorite song of Dolly’s is “Coat of Many Colors,” which you can hear here.

Why? Because it speaks to poverty and redemption. The song isn’t really about the coat at all, but about creating and showing love from scraps that life gave her mother and gives us. Sometimes, those scraps, along with love, are all we have to work with. Life isn’t about money or worldly goods. Beauty is wherever you find it and believe it lives. Like in people’s hearts.

May we all take the scraps life gives us and stitch them into coats or quilts of warmth and love, creating something beautiful that touches people’s souls and helps those in need. We are not doing anyone a favor. We are the ones blessed with the opportunity to uplift others.

Dolly exemplified love and resilience and refused to be diminished by what others thought she, or any woman, could, ought to, or shouldn’t do. She forged her own path with indomitable determination despite what others considered improbable, improper, or, more likely, impossible.

Dolly’s music is legendary and beautiful, but the philanthropic efforts enabled by her success are her living legacy. Dolly’s website provides additional information about her life, along with a link to donate to the Imagination Library in her honor. Dolly founded the Imagination Library 31 years ago, and the program has provided more than 332 million free books to millions of children. Today, more than 3 million books are mailed each month. You can help continue that legacy, as her family requested in lieu of flowers.

Dolly’s own father never learned to read or write. Now, millions of children receive books of their own and, along with them, the opportunity to learn to read and fulfill their dreams, thanks to her.

May we all do even a fraction of the good she did in this world.

Rest easy, Dolly. We will always love you.

Pierre Goicheau (c1652-after 1698) and the Silence of Famine – 52 Ancestors #482

Pierre Goicheau was the father of Acadian founder Jean dit Tranchemontagne Garceau, who was born about (or before) 1680 and was serving as a soldier at Fort Naxouat, in present-day New Brunswick, by August 1696.

Jean’s 1703 marriage record at Port Royal to Marie Levron names his parents as Pierre Garsseaux and Jacquette Soulard, although the evidence presented here strongly suggests that Jacquette was probably his stepmother rather than his biological mother.

Additionally, his marriage entry tells us that he was a soldier serving at the garrison in Port Royal. In that record, his surname is spelled Garsseaux, but elsewhere it’s spelled Garceau and other phonetically similar surnames.

We are exceedingly fortunate that their marriage record provides the names of his parents, which is actually quite rare when the parents never left the old country.

Not only does it tell us their names, but it provides a location as well. Parish of St. René of the diocese of Poitiers.

Yippee!!!

We’re home free, right?

Nope!

As it turns out, as specific as that location sounds, it isn’t.

There isn’t a parish of St. René in the diocese of Poitiers, but there is a Saint-Rémy.

Not only that, but while one Pierre Goicheau, did marry Jacquette Soulard, it wasn’t in Saint-Rémy.

This one makes my head hurt, and my heart ache.

Normally, in my 52 Ancestors articles, I write an article for each individual parent, but in this case, I really can’t do that. What I can and will do is to present the evidence arguing in both directions. Barring the discovery of additional records, Jean Garceau’s biological mother remains unidentified.

We now have additional information about Jacquette Soulard, who married Jean’s father, Pierre Goicheau, along with other evidence that shifts our interpretation of this record.

Sometimes, the real story is not what’s actually contained IN the records. Sometimes life is shaped by the forces surrounding the records – the silence that holds heartache and tragedy.

That silence envelops the Garceau family.

What We Know

We know for sure that on August 24, 1696, Jean Gorseau dit Tranchemontagne, is on the list of soldiers serving with the military company of Claude-Sébastien de Villieu at Fort Naxouat, also called Nashwaak, a French wilderness fort that served as the Acadian administrative capital after Port Royal was captured by the English in 1690.

The log fort was located near present-day Fredericton, New Brunswick at the intersection of the St. John and Nashwaak Rivers, on the south shore across from Bowie Island. Their neighbors were the Native people.

Built in 1691 and 1692, and overlooking the river, the fort was a trading post, about 120 feet square, that became a small military base with only a few buildings and quarters for about 40 soldiers.

Given that we know Jean was on the roster on August 24th, it stands to reason that he was also with the unit on August 14th and 15th when Villieu’s unit, along with Abenaki forces, laid siege to the English fortification at Pemiquid, present day Bristol, Maine, after the English commander violated a truce, murdering several Abenaki chiefs at an assembly.

Jean was among the men who defended Fort Naxouat from an English attack that took place on October 18th, 1696. Joined by their Mi’kmaq neighbors, a few scattered French settlers, and the notorious French pirate, Captain Pierre Maisonnat dit Baptiste who arrived on foot and without a ship, they managed to fight off four times the number of English soldiers. The priest gave a final communion before the battle, because they knew they would all be slaughtered if they lost, which was certainly the expected outcome. They were both outmanned and outgunned.

In the greatest of ironies, it was the weather, a sudden, unexpected winter storm descending upon them, that saved the French garrison and Jean. The English soldiers from Boston were unprepared for the Canadian weather. The English hastily departed after two miserable days and nights, leaving two ships behind, which provided Baptiste with another vessel to resume his life of piracy. Both feared and revered, Baptiste was endeared to the French at Port Royal. He saved them more than once.

We don’t know when Jean Garceau arrived at Naxouet, but it could well have been on February 14, 1694 when “the vessel La Bretonne was fitted out to bring help…This vessel carries 10 soldiers to replace those who may be missing from among the 40 that His Majesty wishes to maintain at the said fort…” Jean Garseau dit Tranchemontagne may well have been among them, although there is no roster.

If Jean was on that ship, then he was present at the Raid on Oyster River, also called the Oyster River Massacre, on July 18, 1694, when a group of Abenaki and Maliseet. along with French soldiers, raided an English settlement at present-day Durham, New Hampshire, on the border between New England and Acadia.

The attack began at daybreak, with the small forts quickly falling to the attackers. In all, 104 inhabitants were killed and 27 taken captive, with half the dwellings, including the garrisons, pillaged and burned to the ground. Crops were destroyed and livestock killed, causing famine and destitution for survivors. Much like the English had done to the settlers at Port Royal in 1690.

The European French and English wars were brutal in the North American colonies.

Jean is again found among the 26 soldiers at Naxouat on the September-December 1697 payment roster.

In 1698, Fort Naxouat was abandoned and dismantled, and Villieu used the material to construct Fort Saint John across the bay from Port Royal which was still under English control.

Located at the mouth of the Saint John River, Fort Saint-Jean became the Acadian capital at that point, and the garrison’s soldiers were stationed there.

Then, in 1700, Port Royal was returned to the French, with Villieu as the administrator. He moved the capital of Acadia back to Port Royal, along with the soldiers who were then quartered at Fort Anne.

This move provided Jean with the opportunity to meet Marie Levron whose family lived across the river.

Jean Garceau (spelled Garsseaux in his marriage record) dit Tranchemontagne married Marie Levron in Port Royal on November 20, 1703, where the priest recorded that he was the son of Pierre Garsseaux and Jaquette Soulard of the parish of St. René in the diocese of Poitiers.

Pierre and Jacquette are neither referenced as living nor deceased. Normally, if a parent is deceased, it says so, so one would presume Pierre and Jacquette were living, although if they died after Jean left France, he would probably not have known.

Searching for Saint-Rémy

Cousin Mark, who is much more fluent in archaic French records than I am, did a lot of work to locate Pierre and Jacquette in the given parish, but he did not find them there.

He did find a very old parish church by that name in the town of Saint-Rémy just northwest of Niort in the Deux-Sèvres department. Unfortunately, those records only reach back to 1693, but the church is much older. Mark reviewed the records in three parishes, page by page, to gather what he could. But that’s not where he found Pierre and Jacquette.

Mark found Pierre Goicheau and Jacquette Soulard marrying on July 2, 1685, in Saint-Marsault in La Forêt-sur-Sèvre, Deux-Sèvres.

Saint-Rémy is 59 km, or approximately 35 miles, south of Saint-Marsault, so not exactly close, especially before the days of automobile travel.

It would be highly unusual to find two people with the exact same rather unusual names marrying, but it’s not impossible.

Mark tells us that:

There are three parish churches named Saint-Rémy in the department of Vienne, all some distance northeast of Poitiers, one in the village of Saint-Rémy-sur-Creuse and two in the villages of Chenevelles and Liegné-les-Bois, near to each other. Departmental parish records for each go back to the period of time of this research.

By Eliane Promis – Own work, CC BY-SA 3.0, https://commons.wikimedia.org/w/index.php?curid=21377477

There is also a very old parish church in the town of Saint-Rémy, just northwest of Niort in the Deux-Sèvres department. 

Unfortunately, despite the church’s obvious age, departmental parish records for Saint-Rémy, Deux-Sèvres, only go back to 1693, but I believe this is the one referenced in the marriage record, based on my review, page by page, of the parish records in the other three parishes and what I found at Filae.com.

Before I engaged in the very tedious and difficult reading of old parish records in French, I consulted and thoroughly researched Jean and his parents’ names at Filae.com. Filae is the primary genealogical site for French genealogy, similar to Ancestry.com, and was purchased by MyHeritage a couple of years ago. I’ve subscribed to it for several years, since I started my research into French origins.

They have original records, but only back to about 1700. Besides family trees, they include the database of what genealogical societies in France have researched for older records. I have found, by comparing what is listed and my own viewing of the original records, that the two in the area, Cercle Généalogique Poitevin and Cercle Généalogique des Deux-Sèvres are very reliable and comprehensive.

I searched between 1650 and 1700 for Jean Garceau and the name’s phonetic variants, and for Pierre Garceau and Jacquette Soulard between 1630 and 1730. For Jean Garceau, there were only two family trees and absolutely no records for the Vienne department. Both trees were Acadian.

Searching Deux-Sèvres, there were 14 genealogical society entries for a Jean Garceau spelled a few different ways. Based on other evidence, none could be the one we are looking for.

For Pierre Garceau, it was about the same: no records for Vienne from 1630-1730, but for Deux-Sèvres for the longer time frame, there were 51 entries by genealogical societies. This is one reason I believe it likely that the Saint-Rémy indicated was the town in Deux-Sèvres and not the three villages in Vienne. Again, however, none of the entries pointed to the Pierre we are seeking and none with a wife named either Jacquette or surnamed Soulard.

But I hit pay dirt with my search for Jacquette Soulard. While there were just three entries for Vienne, none of interest, there were 47 entries for Deux-Sèvres.

Five of them showed children’s births to her and a Pierre Gaucheau or Goicheau, between 1686 and 1698, at villages about 30 miles north of Saint-Rémy: Saint-Marsault, La Ronde, and Moncoutant.

Given the wide variations in spelling in parish records based on varied pronunciation of the names and the subtle changes over time, it is very easy to see Gaucheau becoming Garceau or Garsseaut by the time Jean arrived in Acadia.

Pay Dirt in Saint-Marsault

Mark found 47 entries for Soulard in the Saint-Marsault parish register, including Pierre Goicheau and Jacquette Soulard’s marriage. Five additional records showed their children’s births between 1686 and 1698, recorded in three villages: Saint-Marsault, La Ronde, and Moncoutant.

Their marriage record, originally translated by ChatGPT, corrected by Mark, then retranslated with a much-improved version that agrees with Mark, reads as follows:

On the same day (which was July 2, 1685 (referencing the preceding entry), Pierre Goicheau, a laborer, thirty-three years old, son of the deceased Nicolas Goicheau and Marie Cousin (or Coutin), received the nuptial blessing with Jacquette Soulard, eighteen years old, daughter of Jacques Soulard and the deceased Perrine Estancheau.

Those present were François Goicheau, the full brother of the said groom and a laborer; the said Marie Cousin (or Coutin), his mother; the said Jacques Soulard; and Pierre Soulard, paternal uncle of the said bride. The laborers declared that they did not know how to sign.

That tells us that Pierre Goicheau was born about 1652.

The Five Children of Pierre Goicheau and Jacquette Soulard

I can’t imagine why Cousin Mark is still speaking to me given the amount of work he has invested in my ancestors (who aren’t his), especially after I asked him if he could dig deeper and see what else he could discover. Miraculously, though, he is and has graciously agreed to share his meticulous research.

Mark found baptismal records for five of Pierre Goicheau and Jacquette Soulard’s children.

  • Mathurin Goicheau was baptized August 23, 1686, at Saint-Marsault, a little over a year after their marriage. Mathurin was also the name of one of Pierre’s brothers, but the brother was surprisingly not the godfather.

There was not enough time between their marriage in July of 1685 and August of 1686 for Jacquette to have given birth to Jean too.

They probably lost a child in 1688.

  • Louis Goicheau was also baptized at Saint-Marsault on May 15, 1689.
  • Jacques Gaucheau was baptized at Moncoutant on September 7, 1691.

The surname is spelled differently, and the location is just 7.5 km or about 4.5 miles east of Saint-Marsault, so still quite near where they married and the two earlier children were baptized.

The Moncoutant baptism could actually have taken place in one of two churches in close proximity to Moncoutant.

The 15th-century Church of St-Gervais and St-Protais is located in the center of Moncoutant, on the old road. It was enlarged in the 1600s and partially rebuilt in the 1800s.

All old churches were either on the main road, generally in the center of town, or at crossroads.

La Chapelle-Saint-Étienne is located slightly outside of Moncoutant in this beautiful crossroads village whose origins are lost in antiquity. You can even see the old well in the yard to the right of the church. The church dates from at least 1219 when it was mentioned in a bull of Honorius. Destroyed in the Hundred Years’ War (1337-1453), it was partially restored later.

In 1598, the year the Edict of Nantes was signed, the church was reported to be in very poor condition, and in 1686, the church was reported to be in danger of collapse, inside and out. The record further notes that:

In a chapel there is an arm in which there is a silver vase containing some linens, without the appearance of relics and which is nevertheless traditionally called the arm of Saint-Étienne.

The small cemetery, completely cut off by roads, is in the middle of the town. The priest is sick and crippled.

Going to the waters of Bourbon, he has taken as his replacement a priest named Avice, previously in Largeasse and coming from the diocese of Bayeux. The inhabitants are very unhappy about it. He let three people die (sic) at the door of the church, without giving them communion. He has no sign of a priest, neither in his clothes nor in his speech. He drinks wine very often and, in church, does nothing decent.

And then, in 1695, immediately following a famine:

The sanctuary is still in danger of ruin and has only 4 bushels of rye as income.

If this is the church closest to where Pierre Garsseau and Jacquette Soulard lived, the beleaguered condition of this ancient church and the resident priest’s lack of sobriety explain why they might well have looked elsewhere to have at least some of their children baptized.

Famine Strikes

In 1693, when Jacquette would have been expected to give birth to their next child, the Poitou suffered a catastrophic famine that lasted through 1694.

Cold, exceptionally wet weather ruined successive harvests. Grain reserves disappeared, prices soared, malnutrition spread, and disease followed. Approximately 1.5 million people died in France, roughly 10% of the population, although some estimates are double that. The crisis was intensified by Louis XIV’s war expenses, increased taxation, and military requisitions.

People, desperate for food, were reduced to eating wild herbs, roots, and contaminated bread. Peasants rioted and attacked revenue collectors, tax offices, and military units. The ravages of hunger triggered waves of fatal intestinal infections, including typhus, which quickly spread throughout the population, including churches.

The tiny, neighboring rural parishes of Moncoutant and Saint-Marsault were ground zero for the devastating convergence of Louis XIV’s oppressive policies and the 1693-1694 famine.

Peasants in these two towns resorted to eating boiled grass, thistles, acorns, and decaying roots dug out of the woods. The parish registers note a surge of deaths caused not just by starvation, but by “le mal de gorge” (severe throat/intestinal infections) and typhus brought on by eating contaminated organic matter.

Dead bodies were found lying along the roads, in ditches and fields. People walked until they couldn’t anymore, begging, and died where they dropped.

The Goicheau family would have been struggling mightily, along with their neighbors, and if starvation didn’t prevent Jacquette from becoming pregnant, they buried a child in 1693 or 1694.

Parish registers reflected many deaths and almost no births. Starving women stop ovulating.

Given that Jean was already serving in Acadia in 1696, and likely arrived in 1694, he would have been at least 15 when the famine hit, and possibly somewhat older. The famine provides a reason for Jean to enlist in the military. The official enlistment age was dropped from 18 to 16 during this time, but some recruiters, desperate to be paid in bread, turned a blind eye if boys a year or two younger joined up. Everyone needed to eat.

Jean probably enlisted in the Compagnies franches de la Marine in 1693 or 1694 to secure daily bread rations during the famine. He would have been quickly processed and shipped to New France. We don’t know when he arrived at Fort Naxouat, but it was assuredly before August 24, 1696 when he is listed on the muster roll.

This strongly suggests that Jean was born no later than 1680, and probably earlier. If born in 1680, he would only have been 16 when serving at Fort Naxouat in New Brunswick, which is extremely young.

If he arrived in 1694, then he was probably born around 1678.

If he was 16 in 1693 and enlisted to survive the famine, he would have been born in 1677, when his father was 25.

It’s amazing that Jean survived, and no wonder that he left France. His childhood, beginning in 1681 and continuing through the famine, was spent surviving one kind of trauma or another. By the time Jean was 20, he was probably a battle-hardened warrior in another land.

Pierre and Jacquette had apparently found sustenance and conceived a child in the summer of 1694.

  • Pierre Gaucheau was baptized April 1, 1695, at La Ronde, a village just west of Moncoutant and south of Saint-Marsault, likewise in the La Forêt-sur-Sèvre commune.

There is no death record, but this child apparently died because another child by the same name was born in 1698. The devastating effects of severe malnutrition don’t simply resolve when a food source is restored. Mothers’ bodies don’t recover well, and the frequency of stillbirths, low birth weight infants, and infant deaths are elevated for some time afterward.

Another child was probably born and died in 1697.

  • Their fifth child was also named Pierre Gaucheau, likely born after his brother Pierre died, and was baptized on August 26, 1698, also at La Ronde.

There, the trail goes cold.

Mark was unable to find any additional baptisms, but that doesn’t mean there weren’t additional children.

Jacquette was 18 in 1685, so in 1698 she would have only been 32, clearly young enough to bear more children. Either she died, Pierre died, they attended church elsewhere, or the records are missing.

Based on several records, we know that Pierre, and therefore Jean, lived at Saint-Marsault for some time, at least a decade, because Mark found several records placing Pierre there.

Both Pierre and his brother François witnessed their father Nicolas’s death entry on November 23, 1680, five years before Pierre married. That parish entry gave Nicolas’s age as 70, meaning he would have been born about 1610. Pierre was born when his father was about 42.

The Neighborhood

It was less than 5 miles between Moncoutant and Saint-Marsault, so Jean Garceau’s parents probably lived someplace in between.

La Ronde, where the fourth and fifth children were baptised, is dead center between Moncoutant and Saint-Marsault.

The small village of La Ronde is located at a crossroads between Moncoutant and Saint-Marsault and has its own church, L’Eglise Notre Dame La Ronde, La Forêt-sur-Sèvre, which dates from the 12th century and was rebuilt in 1478 following a fire.

This historic building at the main intersection across from the church in La Ronde probably marked the way for Jean Garceau’s parents too – although they would have been familiar and didn’t need a sign.

Today, a Madonna figure still resides in the alcove between the door and window, faithfully guarding the residents of the home and looking across the street at the church.

These quaint French villages of a few houses each are all connected by tiny one-lane roads threading their way like ribbons through farm country that has been tilled since before time was recorded. It seems that every couple of miles there’s a tiny crossroads village, so small there’s not even a stop sign, with its requisite Catholic church to serve the local villagers and farmers. Often you can see the steeples from one village to the next.

It was someplace here that Jean Garceau was born, grew up, and ultimately said goodbye to his family as a soldier. He probably remembered this scene well – the crossroads, the churches, the villages, and yes, his parents and siblings.

He would have never forgotten the hunger pains either, the hollowed-out eyes of starvation, waiting for the grim reaper to put an end to their suffering. He probably wondered if his family had survived after he joined the military. We know that thousands died, but we can’t say their names. Jean’s family members and friends perished, but his light survived.

Leaving France meant escaping the inevitable, and reserving the few scarce resources for his family members left behind. That’s all he could do for them.

Nicolas Goicheau and Marie Cousin

Mark was able to locate a few more records for Pierre Goicheau’s parents, although neither their marriage record nor the baptisms for their children were found.

Nicolas’s death record in Saint-Marsault in 1680 was witnessed by Pierre and his brother François, who, five years later, witnessed his brother Pierre’s marriage in the same church.

Nicolas and Marie also had a daughter, Jeanne Goicheau, who was married at Saint-Marsault on July 8, 1686, listing her parents as Nicolas Goicheau and Marie Cousin. Witnesses at this wedding included her brothers Pierre, François and Mathurin Goicheau, which tells us that Nicolas and Marie had at least four surviving children.

They likely welcomed several more children into their lives between 1635, or so, and about 1660, when Marie would have been 43.

Nicolas Goicheau was also recorded as godfather to a Nicolas Couzin, son of a François Couzin, clearly a relation to his wife, in January 1646 at Saint-André-sur-Sèvre, a tiny country crossroads village consisting of a few picturesque French houses, a church and cemetery to the northwest of La Forêt-sur-Sèvre, the same place where Pierre’s future wife, Jacquette Soulard, was baptized in 1666.

This church clearly served the needs of nearby farmers whose families would have walked to church.

Saint-André-sur-Sèvre is only about three and a half miles from Saint-Marsault.

Given that family records are found in both churches, they probably lived someplace along this beautiful, quaint French country road, winding through the beautiful countryside between the two towns.

François Goicheau, Nicolas and Marie’s son, was also listed as a witness to Marie’s death at Saint-Marsault in 1692, where her age is given as 75, so born about 1617. Mark notes that François is listed twice in that record, so it’s unclear if that was a clerical error or if there were two men by the same name.

Mark found 88 results for a Marie Cousin between 1600 and 1700 within just 20 km of La Forêt-sur-Sèvre, and it is likely she was a godmother to a few infants, but he could find no other records that related to Goicheau/Gaucheau. Marie Cousin seems to be a common name, unlike Nicolas Goicheau by whatever spelling.

Mark did find additional information about François, although it’s a bit confusing, but then again, everything about this family has been “interesting.”

Complicating this still further, there is a marriage record at Saint-Marsault, the acknowledged village for much of the family records, on 16 Jul 1691, of François Goicheau, age 30, so born about 1661 and a Perrine Geay, age 20. The record shows his parents as François Goicheau and Marie Cousin! – and as a witness a brother François! There are just too many men named François in this picture, and some are assuredly incorrect!

I need to locate the original Deux-Sèvres record to see what it really shows.

The groom’s father should have been Nicolas, not another François, and I doubt he had another brother with the same name, although his death record at Saint-Marsault, of 12 Jan 1695, age 35, likewise shows as a witness a brother François and sister Jeanne. In addition, Marie Cousin’s death record of 1692 shows as witnesses two sons named François! I guess it’s possible.

The famine took hold in the fall of 1692 when summer grain crops failed. The King’s soldiers had depleted any supplies that might have normally been held in reserve, so the suffering began immediately.

Marie died on May 1st of 1692, so she was spared the fate of starvation. While I’m sure they grieved her passing, I’m equally as sure that her family thanked the Lord that she did not suffer what was coming.

The death of Francois Goicheau in January of 1695 was almost assuredly a result of the famine. While the acute starvation ended in the fall of 1694, survivors would have been in terrible health, mere walking skeletons, and the famine-induced diseases and their after-effects persisted for years.

We don’t know what happened to the rest of the family.

Jacquette Soulard’s Family

While it’s extremely unlikely that Jacquette Soulard is the biological mother of Jean Garceau (Goicheau), I can’t definitively close the curtain on that possibility either.

Mark was hoping to find additional information that might reveal more. While there is nothing conclusive regarding the probability or possibility of Jacquette being Jean Garceau’s mother, I’m including Mark’s research in case one day we discover that, in fact, she is.

As I could not find any record of Pierre’s parents’ marriage, likewise I could not find any record of the marriage of Jacquette Soulard’s parents, Jacques Soulard and Perrine Estancheau, under either name or its variants, anywhere in France.

There is a record of the baptism of a Perrine Estancheau on 20 May 1623 at Montravers, about five miles northwest of Saint-André-sur-Sèvre. The parents listed were François Estancheau and Michelle Bodet. This would require that Perrine gave birth to Jacquette at around age 43, which is certainly possible.

I did find Perrine’s death record of 17 May 1668, at Saint-André-sur-Sèvre, less than two years after the birth of Jacquette. Her husband Jacques Soulard is named, and witnesses include her brother Jacques Etancheau, brother-in-law Pierre Soulard and sister Catherine Etancheau, leaving no doubt of her identity. No other children of Jacques and Perrine were found. Her death may have been as a result of childbirth if she did give birth to Jacquette at age 43 and was again pregnant.

There were 17 births of a Jacques Soulard between 1600 and 1650 within 200 km of La Forêt-sur-Sèvre, but none within the immediate area, making it impossible to determine which, if any, were relevant without a marriage record naming his parents. Jacques may have remarried a Michelle Brouard. A marriage record at Saint-André-sur-Sèvre of a Pierre Soulard on 10 Aug 1708, age 33, so born about 1675, names his parents as Jacques Soulard and Michelle Brouard. A brother François Soulard is named as a witness. I found no record of any remarriage for Jacques. It would be surprising if Jacques Soulard did not quickly remarry given Jacquette’s very young age, but without a marriage record, one has to put other pieces together to draw inferences.

I also could not find a definitive death record for Jacques. There is a death record for a Jacques Soulard on 28 Apr 1695 at Combrand, Deux-Sèvres, several miles to the north of Saint-André-sur-Sèvre. He is likely the same Jacques Soulard baptized in the same parish on 24 May 1609, although the death record shows an age of 60, so born about 1635, and married to a Françoise Guesdon or Guion. As I mentioned, there were several Jacques Soulards in the greater area so I cannot draw any clear conclusions.

Revisiting Saint-Rémy

How many times have you failed to find something where you thought it should be, then gone back and revisited that same drawer again?

Mark did the same thing:

I’ve also taken another look at the area around Saint-Rémy, keeping in mind there are no records for the parish before 1693. Saint-Rémy is close enough to La Forêt-sur-Sèvre and the surrounding villages such that most of the same records that appear within 200 km are the same for both locations. I first checked for any records for a Pierre Garceau or Goicheau. The Pierre Goicheau that married Jacquette Soulard was born about 1652 according to the marriage record.

For the name Pierre Garceau and its many spelling variants, there were no results at all within 20 km of Saint-Rémy. Within 200 km there were no baptisms around the 1650s. One occurred in 1637 and another in 1671, both at some considerable distance from Saint-Rémy. There were no marriages at all for a Pierre Garceau within 200 km. For a Pierre Goicheau, the only marriage was that to Jacquette Soulard. As I mentioned earlier, I could find no baptisms for any of the children of Nicolas Goicheau and Marie Cousin. Nor were there any Pierre Goicheau baptisms by other couples between 1638 and 1697 within 200 km. As I noted, there was an almost total lack of records for Nicolas Goicheau, the earliest being his appearance as godfather in 1646. Throughout France, there were only ten entries at Filae for a Nicolas Goicheau from 1560 to 1700, and four of those I’ve already noted.

Moreover, Filae shows no records of a Jean Garceau or Goicheau born to a Pierre Garceau or Goicheau or any spelling variants, nor a Jacquette Soulard, anywhere in France between 1620 and 1700.

Evaluating the Possibilities

When Jean Garceau married, he gave his parents’ names as Pierre Garsseaux and Jacquette Soulard. Jean did not know how to write, so the priest would have written the names as he heard them.

We know from Mark’s research that this couple was married in 1685 and had a baby in 1686, thirteen months later, and it wasn’t Jean.

Jean’s father, Pierre, was 33 in 1685 when he married, so born about 1652, although we have no baptismal record for him. Jacquette was 18, baptized on November 28, 1666, in the village/commune of Saint-André-sur-Sèvre, six km northwest of Saint-Marsault.

When Jean married in 1703, in Acadia, given that he was already serving in 1696 as a soldier, he could not have been born later than 1686. If he were born in 1687, he would have been only nine years old in 1696 as a soldier, and 16 in 1703 when he married. That’s simply impossible.

Given what we know, only a few scenarios are possible, and the situation is further complicated by upheaval in the part of the Poitou where Jean’s family lived.

Could Religious or Social Upheaval Have Affected the Records?

Jean could have been born before his parents, Pierre and Jacquette, were married. If that’s the case, then he was born in 1685 or earlier – and several years earlier given his 1696 military service.

If Jacquette was his mother, it raises the question of why his parents didn’t marry when Jacquette was pregnant with Jean, since they clearly did marry in July of 1685. French girls were considered of marriageable age at 14, and she turned 14 in 1680.

This scenario, at least on the surface, has several flies in the ointment. However, taking into consideration what was happening locally might make a difference.

Protestantism was deeply established in the Poitou, including the present-day Deux-Sèvres. This was not a distant national controversy to the local families. Moncoutant had a substantial Protestant community, and its own municipal history specifically says that the community suffered the notorious dragonnades late in the seventeenth century.

In 1681, the Poitou became the first region in which Louis XIV used the dragonnades.

Royal dragoons, shown in this 1886 painting by Jules Girardet, were forcibly quartered in Protestant homes, where they were permitted to intimidate, abuse, rob, and otherwise torment the occupants until they converted to Catholicism.

In 1681, Jacquette would have been 14 or 15.

We know Pierre and Jacquette had some connection with Moncoutant, because one of their children was later baptized there, and Jacquette was born just north of there.

We have no evidence that Pierre or Jacquette was Protestant. Their marriage received a Catholic nuptial blessing, and Jacquette was baptized in a Catholic church in 1666.

We have no marriage or baptismal records for the children of Nicolas Goicheau and Marie Cousin, nor for a first marriage for Pierre Goicheau. Nicolas witnessed a Catholic baptism in 1646 in the church at Saint-André-sur-Sèvre that includes both the Couzin and Soulard families, so he was Catholic at that time. These records substantially reduce the likelihood that either family was Catholic in the 1670s or 1680, but does not entirely remove the possibility.

Pierre and Jacquette’s children were baptized in Catholic churches, except for Jean, whose baptismal record is missing. Still, in the 1680s, they were living in upheaval –  among frightened neighbors, forced conversions, soldiers quartered in private homes, destroyed religious communities, and families fleeing or practicing their faith secretly.

Protestant baptisms and marriages could have been recorded separately before 1685. After the Protestant pastors were banished and churches destroyed, records were lost, and a Protestant background would probably have been hidden. Catholic baptism and marriage became compulsory. A missing earlier marriage or baptism might reflect religious disruption, although there is no evidence that this explains Jean’s missing baptismal record or those of the children of Nicolas Goicheau and Marie Cousin.

It does, however, provide insight into the times in which they were living.

So, what are the possibilities surrounding Jean’s birth and parents?

Possibility 1: An Earlier marriage and baptism at Saint-Étienne that were not recorded 

It’s possible that Pierre and Jacquette (or another wife) were married at nearby Saint-Étienne, and Jean was baptized there too, but neither event was recorded due to the chronically drunken condition of the priest. If the wife was Jacquette, they remarried at Saint-Marsault.

However, given that they couldn’t read or write, how would they have known that their marriage wasn’t recorded? And if that was the case, then why was Jean not rebaptized too?

This is a rather unlikely scenario, but still a possibility.

Possibility 2: Jean was born in 1680 or 1681 to Jacquette before she married Pierre

If Jean was born when Jacquette was 14 or 15, that would have been in late 1680 or 1681, which means he was only 15 or 16 by the time he was serving at Fort Naxouet in 1696, and probably two years younger when he enlisted during the famine.

This is really the only tiny sliver of a window in which we can make this scenario of Jacquette being Jean’s mother work. However, it still doesn’t explain why Jacquette and Pierre didn’t marry when she was pregnant, given that they did marry in 1685. Unless they did marry at Saint-Étienne and remarried later when they discovered their marriage hadn’t been recorded, or unless they were Protestant, which is highly unlikely.

Given Jean’s age, this scenario is highly unlikely, bordering on the nearly impossible.

Possibility 3: Pierre was previously married

A more probable scenario is that Jean’s father, Pierre, was married previously and Jean was born about 1677 or 1678 to Pierre’s first wife, who died. Pierre then married Jacquette in 1685, who was functionally Jean’s mother, so he thought nothing of listing her as such.

In this scenario, if Pierre, who was 33 in 1685 when he married Jacquette, had originally married at 25, in 1677, which was still relatively young, Jean Garceau would have been born about 1677 or 1678, so 14 or 15 when the famine struck in 1692, 18 or 19 in 1696 in Naxouet, and roughly 25 when he married Marie Levron in Acadia. That’s much more reasonable.

That said, being born out of wedlock might have been a reason for Jean to join the military relatively young too, but given the dates and that Jacquette and Pierre married in 1685, I’d wager the famine was Jean’s motivation. His parents were probably glad to see him go, not because they didn’t love him, but because it gave him a chance for survival.

There’s absolutely no way for Pierre Goicheau and Jacquette Soulard to be the parents of Jean Garceau who was serving in Naxouet in 1696 if he was born after they married. Yet, when Jean married in 1703, he clearly said they were his parents, even though the parish name given was not where Pierre and Jacquette lived when Jean left.

Saint-Rémy is improbably distant from Saint-Marsault where all of the other Garceau and Soulard records are clustered. These families were farmers and laborers, as recorded in parish registers. They didn’t simply come and go, moving around the country at will. They were tied to the land and the landowners, and their children would have been baptized in nearby churches.

Maybe Saint-René as recorded in Acadia was not Saint-Rémy, and maybe the parish given was simply wrong or misunderstood. Mark is a meticulous researcher and first tried to find a parish of either St. René or St. Rémi(y), as either could have been what was written or intended. Spelling was not standardized at that time, and he searched all over France.

Based on Mark’s findings, I believe we have enough evidence to conclude that this is the correct family, and that Jean Garceau spent his childhood and much of his formative years living on a farm near Saint-Marsault, and one way or another, was raised by his stepmother, Jacquette Soulard.

I think this is really the only reasonable possibility.

Visiting Saint-Marsault

Thanks to Mark’s exhaustive work, I was able to visit Saint-Marsault in the spring of 2024 on a bus tour.

I felt as if I was literally walking in their footsteps, and that was before Mark had discovered the additional information, including Pierre Goicheau’s children’s baptisms and his parents’ death records in the same parish.

Our guide had made room in the schedule for this detour, and our tour bus pulled up outside on the main road, at a pull-off beside a park along the village stream. Our time at this stop was limited to about 15 minutes.

These old churches are often difficult to get to, with little, if any, parking at the actual church. The original members didn’t need parking as they simply walked or perhaps rode to church in a wagon.

The church, L’Église Saint-Martial (Saint-Marsault, La Forêt-sur-Sèvre), stood on a little hill, just up from the main road. This ancient church dates back to the Middle Ages in this tiny village and was named after a third-century saint venerated for his role in the spread of Christianity in France. The church was restored in the 18th century, but the various parts date from different periods in its history. The bell tower dates from the 12th or 13th century, so it would have already been “old” when Jean and his parents attended church here in the late 1600s.

We walked up the slight hill from the contemporary road that now bypasses the church.

The priest promised to meet us, but no one was there. Our knocks echoed on the thick wooden door but went unanswered. My heart was sinking with disappointment.

I tried to console myself by telling myself that at least I was there, in that sacred place, and able to view the exterior. Parts would have looked much the same as when Jean and his parents trod this same land.

We walked around to the side when one of my Acadian cousins discovered that they had left the church’s side door open for us.

Oh, happy day!

This beautiful door looks to be original. Pierre and Jacquette would have come and gone through this door, perhaps announcing themselves to the priest through the window if they were in need of a baptism or were sent to fetch the priest for last rites for someone.

This church is stunningly beautiful. I could picture my ancestors here and hear their voices echo across time.

Young Jean was probably being hushed to stay quiet during the services. He was probably 7 or 8 when his father married Jacquette, so would have been watching as the priest united his new family.

Jean would have sat in these pews and perhaps knelt on the floor. As young boys will, his attention probably wandered as the priest’s voice droned on in Latin, and he looked out the windows at the clouds.

Of course, I took the opportunity to light a candle to honor my ancestors, exactly as they would have done. That flame of love that burns eternal, timeless, and endless.

Light and sacred prayers winging their way across the ages – 339 years from Pierre’s wedding to my return.

I always wonder if my ancestors are watching or somehow know that I’ve returned home.

Are they here with me? Silent souls in the church they loved so.

I closed my eyes, feeling them and drinking in the elixir of their devotion.

Where they celebrated life and mourned death.

Seeing what they saw in the alcove. Acadians were staunchly religious. They fought and sacrificed for the right to worship in the Catholic faith.

The priest’s door, slipping into the side chapel.

These doors were reinforced because the church served as a place of safety during times of attack.

Knowing that they sat here, stood here, knelt and worshipped here made it difficult for me to leave. I walked through that same doorway they had. Part of my soul is connected here through an invisible umbilical cord reaching across endless generations.

More than one tear slipped down my cheeks as I stepped outside and walked back down that hill.

Tears of joy, tears of longing, tears of separation from something I had just found. How could I possibly have become so connected so quickly? Or maybe it wasn’t quickly.

Maybe it was threads and ropes and bonds reaching across the centuries.

Maybe it was my ancestors holding me, calling me.

Maybe it was my own struggle to reach them, and theirs to survive.

Maybe, maybe our hands and our hearts had finally touched and bonded, here, in this sacred place.

Not just Jean Garceau and Pierre Goicheau either, but Jean’s grandparents, Nicolas Goicheau and Marie Cousin, and those unknown and unnamed who had come before. Generations who had probably trod on these same stones, under this same roof, worshipping and praying for those they loved.

I knew I had to leave, but I wasn’t ready. Something was holding me here. But our time was up.

I began my walk down the hill, back to the bus, my eyes blurred by tears. I told myself that crying like this was ridiculous.

Why was I having this visceral reaction?

Then, I noticed a pathway to the far side of the church, behind the foliage. I had to follow it. But I also needed to hurry, as everyone else was already headed for the bus and I was already bringing up the rear.

More tears flowed at my next discovery.

Alone, I walked around to the far side of the church, where I happened upon a courtyard of sorts, with a fountain. That seemed rather…odd.

I wondered what this was. I only had a quick minute, as everyone else was already boarding the bus, so I had to turn around without exploring. I was climbing the steps, on my way out, when I made the discovery that illuminated where I had just stood.

As I held onto the railing, I looked down and wondered what I was seeing. It looked quite unusual. Upon closer inspection, I realized that tombstones had been recycled into the landscaping, beneath the railing, beside the steps that led up to the front of the church. That’s when it hit me. The “garden” was the old cemetery, which, of course, was just outside the door of the church. Now it all made sense!

The most that could be recovered from this photo is “ici repose,” meaning “here rests.”

This was the parish cemetery, apparently paved over when the gravestones were recycled into the landscaping. The fountain and statue of the Madonna are all that’s left to honor those who were buried here.

This is where generations of Garceau family members rest, marked by only that fountain and the dust of their bones.

I had no idea I had just been standing on generations of my ancestors. Perhaps they summoned me. Maybe that’s why I couldn’t leave.

I hear you.

I see you.

Maybe their ache, still lingering from the horrors of famine, reached my heart. Standing there, that day, I didn’t yet know about that terrible chapter that occurred here. How many died – their deaths perhaps never recorded, and buried quickly by the few well-enough to dig a grave.

And the tiny graves of Pierre and Jacquette’s babies.

Eternal Spring

As I crossed the street to board the bus, I noticed the old well in the little park.

The lush green foliage and spring flowers were thriving along the stream that conferred life – its water sustaining and nourishing the community.

The priest drew the cool water from the well and blessed it to make it sacred, although it was already the sacred key to life and always had been.

A community well was dug near the stream to provide clean water, and everyone took their bucket to the well, where they exchanged news of the day. Today, that’s just a memory, but the well remains, as do the whispers of our ancestors, traveling on the breezes.

Children had probably played here since time immemorial.

The Goicheaus were laborers, living on a nearby farm, so they would have come and gone, traveling along this road, perhaps visiting the well when they were in the village. From time to time, they probably gathered flowers and laid them on the graves of their ancestors and family members as they passed by. In a time when graves were marked by neat wooden crosses, before gravestones were recycled as something else.

My family stood exactly in this spot – right here – some 340 years ago, and before. Probably for centuries. Today, the well housing remains in the little park beside the stream, across the main road and down the hill from the church. The park probably exists because it’s low and the stream likely floods in the spring.

Dandelions bloomed that day just as they did when spring announced itself on those long-ago spring days, too.

I noticed this stately tree and wondered if it stood witness then, or if just the well and stream remain from that time.

Did the tree shelter Pierre’s descendants who heard stories beneath its branches about the life and times of Pierre, Jacquette, and Jean? The one who went to seek his fortune across the ocean in Acadia during the starving times called the “years of misery” by the peasants?

Did Pierre’s grandchildren and great-grandchildren play beneath these protective branches, beside the stream?

Did this tree, or its ancestors, bear witness to generations of Garceau family members who married and worshipped here, as Pierre and Jacquette’s babies were baptized and some were buried beside the church?

Did it witness the funerals of Pierre and Jacquette, and Jean’s grandparents, Nicolas Goicheau and Marie Cousin?

Maybe this little park is, in reality, a living memorial to their lives. Maybe the tree, like them, was once young and has now grown old, holding cherished memories that it has no one left to share with.

That is, until one of us returns home.

_____________________________________________________________

Share the Love!

You’re always welcome to forward articles or links to friends and share on social media.

Subscribe!

If you haven’t already subscribed, it’s free. You’ll receive an e-mail whenever I publish by clicking the “follow” button at the top of the main blog page, here.

Help Keep This Blog Free

I receive a small commission when you click a vendor link in my articles and purchase that item. This does NOT increase your price but helps me keep the lights on and this informational blog free for everyone. Please click on the affiliate links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

Autosomal DNA Unlock at FamilyTreeDNA to Be Retired August 18th

The autosomal unlock for transferred (uploaded) DNA files at FamilyTreeDNA is being discontinued (retired) on August 18th.

In a nutshell, this means that if you uploaded or transferred a test from another vendor and DID NOT purchase the unlock for the advanced tools, you only have a few days left to purchase that unlock if you (or the tester) can’t retest and don’t have a usable stored sample at FamilyTreeDNA.

If the tester has previously submitted a sample and cannot retest, contact FamilyTreeDNA support to confirm that a sample is still available. Of course, DNA tests can fail, especially on older samples.

The reason for the unlock retirement is because the new Family Finder NGS test provides substantially more coverage than a transfer test, and an upgrade will be offered at a special price beginning the 18th.

Upcoming features, including Family Finder Discover, developed around the new Family Finder platform, cannot be supported on files from other vendors. Additionally, many files from other vendors cannot be transferred to FamilyTreeDNA.

A new test with better coverage and more features is great news if the tester is living and can submit a new sample, but for those who cannot retest and do not have a stored sample, I strongly recommend that you sign in and purchase the $19 unlock for those tests now.

Why purchase something that is being retired?

Having access to advanced tools is better than not having access, and these tools still work fine. You won’t be able to receive all future features, but at least you’ll have access to what is available today, especially segment and chromosome browser information. Your relatives’ tests can be just as important to your genealogy as your own test, because they carry different segments of your ancestors’ DNA.

What Features Are Included in the Unlock?

This chart shows features included in the free autosomal transfer versus with the unlock:

Feature Free Transfer – No Unlock With the $19 Unlock
Matching Yes Yes
Matrix (which matches also match each other) Yes Yes
Shared matches Yes Yes
Segment data download Yes Yes
myOrigins (ethnicity) No Yes
myOrigins segment data No Yes
Chromosome Browser No Yes
Chromosome Painter No Yes
Y-DNA Haplogroups No When SNPs are available in the other vendor’s file
ancientOrigins No Yes

This Only Pertains to Transfers Without an Unlock

To be crystal clear – This only pertains to transferred (uploaded) autosomal files from other vendors that HAVE NOT previously purchased the unlock.

  • If you have an uploaded or transferred autosomal file from another vendor and have already purchased the unlock, you won’t have received the email, and it doesn’t pertain to you.
  • If an uploaded or transferred autosomal file registered to your email has not been unlocked, you should have received this email.

It’s always better to test ON any vendor’s platform rather than upload a file from another vendor. If your tester can, and is willing to provide a new sample, or already has one on file, don’t purchase the unlock today. Wait until the 18th and purchase the Family Finder test at the special upgrade price.

If your tester does not have stored DNA and cannot retest, purchase the unlock NOWYou won’t be able to after August 17th

The Email

People who have uploaded an autosomal DNA file and have not purchased the unlock received an email with the following information:

The current Family Finder test will provide better results and new tools that another vendor’s file cannot support. Other vendors don’t test the same DNA locations as FamilyTreeDNA, and the Family Finder NGS test generates 400 times more autosomal data than the older chip technologies used for transfer files.

The Family Finder NGS upgrade will be offered for transfer files beginning on August 18th. If the tester doesn’t have a viable sample in storage, a new collection kit will need to be sent to the tester. If this pertains to you, and you or the tester can upgrade, that is absolutely the way to proceed – and $29 is a great price.

The only people who should purchase the unlock now are those who don’t have a sample in place and can’t retest. Otherwise, wait until the 18th and order the Family Finder upgrade.

_____________________________________________________________

Share the Love!

You’re always welcome to forward articles or links to friends and share on social media.

Subscribe!

If you haven’t already subscribed, it’s free. You’ll receive an e-mail whenever I publish by clicking the “follow” button at the top of the main blog page, here.

Help Keep This Blog Free

I receive a small commission when you click a vendor link in my articles and purchase that item. This does NOT increase your price but helps me keep the lights on and this informational blog free for everyone. Please click on the affiliate links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

AI Can Save Your Life

This is the sixth and final article in the AI series, and one I never dreamed I’d be writing.

For AI education, I suggest you read the first five articles in order. However, this article can stand alone.

  1. The first article, Your Wonderful AI Assistant – Sometimes Wrong, Never Unsure, Always Convincing, explains why I’m writing this series and what to expect.
  2. The second article, All About AI – What It Is, What It Isn’t, and Why It Matters, explains what AI is, where it “came from,” the different kinds of AI, how it’s “trained,” plus examples of how it does and doesn’t work well.
  3. The third article, AI Assistants – The Good, the Bad, the Ugly and the Unseen, explains how AI tools work (and fail), the different types of AI tools, and when you may encounter them, even when you don’t realize it. This article closes with examples of successfully using AI, along with AI educational resources.
  4. The fourth article, AI and Genealogy – Brick Walls, Breakthroughs and Blunders, explains how AI is being used in genealogy by vendors and by individuals personally. It includes controversial topics like photo and image generation and discusses expert GPT tools and how I’m using them successfully.
  5. The fifth article, The Dangerous, Dark Side of AI, and How to Protect Yourself, explores the dangers that we face every day as a result of AI technology and humans who misuse it, and steps you need to take to protect yourself.

The Unexpected Sixth Article

Given that I’ve been writing about AI recently, I feel that it would be disingenuous not to include this final article. I intended for the article about the dangers of AI to close the series, but, as it turned out, there was another one waiting.

I had no idea that the body of a close family member was harboring a ticking time bomb, and when it came to light, time was of the essence. They were in severe pain, and I was far away.

AI can be and is sometimes wrong, but so are humans, including physicians. I’ll take as many brain cells as I can get, even if some of them are “artificial.” That’s fine with me.

This time, it was AI that saved not only the day but my family member’s life by providing us with information that helped focus the medical team in the right direction.

If you’re wondering what an article about AI has to do with genealogy – let me be very direct. I’m not planning a funeral and entering a death date in my genealogy software. Instead, I’m writing this article.

I am being intentionally vague in some places to protect the privacy of the people involved.

Welcome to an Emergency

Text from Family Member (FM): Got a minute to talk?

Me: Sure

FM: I’m in the hospital.

Me: ??

The Backstory

Over roughly the past three to five years (I’m unclear about the exact length of time), FM had visited the hospital emergency department (ED) three previous times for intractable abdominal pain.

Each time, they looked for the most common culprits:

  • Appendicitis – nope
  • Gallbladder – nope
  • Hernia – nope

Administered pain meds. Pain subsided.

Dismissed to follow up with the primary care physician.

Don’t know. Nothing found.

Rinse and repeat a few months later.

FM became increasingly hesitant to go to the ED because no cause was ever diagnosed, going was miserable when they were in excruciating pain, and the pain subsided a few hours after taking pain meds.

FM also hates to take pain meds, so if the pain was severe enough for them to take meds, it was very severe indeed.

This time, however, after two full days of excruciating unsubsiding pain, with nothing to eat or drink, FM’s housemate took FM to the ED of a world-class hospital.

A few hours later, after they got the pain under control, FM texted me. By that time FM was pain-free again, but quite weak, and the medical team was once again checking off the potential sources.

The First Night

I began asking questions.

“Yes, I know they said you don’t have gallstones, but did they rule out a lazy gallbladder? You have all the symptoms. Can they see sludge and “sand,” not just stones?”

Google AI became my best friend. Please note that every answer or suggestion was accompanied by an important disclaimer:

“This is for informational purposes only. For medical advice or diagnosis, consult a professional. AI responses may include mistakes.”

I know you are cringing about using AI, but the doctors had supposedly ruled out several things more than once during repeat visits. There was very clearly something still wrong, and it was worse this time than ever before.

Desperation was setting in, and AI is a tool we have at our disposal.

So many questions bubbled into my mind. What would happen if FM were driving when this happened? Or camping? Or canoeing alone?

With Google AI’s help, I was able to organize my thoughts and began asking more pointed questions about possibilities that hadn’t occurred to me.

“What about a gallbladder infection or pancreatitis?”

FM went through the list of what they had ruled out and told me that the following day, they were going to do an endoscopy to rule out an ulcer. That seemed quite unlikely given FM’s symptoms, but they were clearly running out of things to rule out too.

We were quickly entering unicorn territory.

Complicating Factor

FM had undergone abdominal surgery 17 years earlier.

Google AI suggested an internal hernia. With normal external hernias, the gap in the muscle wall allows the intestines to protrude outside the abdomen.

With a rare internal hernia, a loop of intestine slips through an opening inside the abdomen and can become trapped or twisted. If its blood supply is cut off, the trapped intestine essentially gets squeezed to death. This condition is extremely difficult to diagnose, terrible when missed, and often fatal.

According to the Cleveland Clinic, an internal or strangulated hernia cuts off blood flow to the trapped tissue or intestine. Without oxygen, the trapped tissue dies (gangrene), the bowel bursts, and toxic bacteria leaks into the body. This causes severe sepsis and shock, followed by multi-organ failure.

The overall mortality rate for internal hernias can exceed 50% when diagnosis and treatment are delayed, and one of the medical team members in the hospital said it was as high as 75%. People with previous abdominal surgery, especially on the gastrointestinal system, experience the highest mortality rates.

The Cleveland Clinic reports that gangrene accompanied by a bacterial infection can lead to death within 48 hours, while untreated severe sepsis can be fatal within 12. My aunt died of this year ago, so it was uncomfortably familiar.

One of the factors that prevents internal hernias from being diagnosed is that the pain tends to come and go. Sometimes the strangulation is caused positionally. When the pain starts, everything tightens up. When powerful pain medications are administered, the abdomen and intestines relax, the trapped piece of intestine slips back out of the loop, and everything appears to be alright until the next time.

The surgeon later told us that patients with internal hernias present to the ED an average of five or six times before being diagnosed.

Those who make it to diagnosis are the lucky ones.

Panic

Panic set in about this time.

Panic and I are old “friends,” maybe “frenemies.” I panic with intention, and I can handle whatever happens until the emergency is over, then I allow myself to fall apart.

I was texting back and forth with FM.

I asked my husband to find plane tickets. He did. We had four hours to be on the plane, with an hour-long drive to the airport, and a requirement to arrive two hours early. We made it.

Google AI and I were continuing to interact. I told it that the endoscopy was clear. Here is the response thread with suggested possibilities.

These interactions are particularly useful, because they include what to ask for and explains why it matters in succinct, understandable language.

This is particularly interesting, because after the endoscopy, the doctor told FM that an internal hernia had been ruled out. It’s clear from this information that a scope alone cannot rule out an internal hernia.

A CT scan might or might not identify an internal hernia, depending on when the scan occurred.

Just having this information at my fingertips was reassuring.

When the doctor told FM that the scope was clear and the internal hernia had been ruled out, FM asked how it had been ruled out, and how many internal hernia rule-outs were false negatives. The doctor told FM that he didn’t know.

Thought bubble: Shouldn’t you know that?

One of the best features of Google AI is that it provides actionable steps under the circumstances and suggests how to advocate effectively but respectfully.

Google AI continued to ask questions and make suggestions.

The Pattern Emerges

I answered the question and provided Google AI with a list of FM’s symptoms, a rough history of the episodes, information about the prior surgery, and a list of ruled-out causes.

Based on that information, Google AI suggested that an internal hernia had been missed. This was incredibly useful information and turned out to be accurate.

I was texting this information to FM.

AI recognized the internal hernia pattern and explained why it might be happening – along with the increasing danger.

The intestines begin to die as they are strangled to death, and the pain is essentially the intestines screaming.

Next, AI explained how to guide the ED. Although FM was no longer in emergency and had already been admitted prior to the scope, the issue was ongoing and the advice was still valid.

This was critically important information.

As it turns out, Google AI was right. A specialty consult is exactly what FM needed.

Surgery

The next consult was with a specialist surgeon familiar with FM’s prior type of surgery who also teaches at the medical school. We’ll call him Doctor F.

Based on FM’s history and symptoms, Doctor F confirmed the probability of an internal hernia. We were actually relieved because we finally had a potential diagnosis, and it was something that could be fixed.

Doctor F was the one who coined the phrase, “difficult to diagnose and terrible to miss,” and was that ever an understatement.

The next day, FM underwent surgery where not one, but TWO different internal hernias were located and repaired. One in a location Doctor F suspected, and another that was entirely unexpected.

I was stunned when Doctor F told us that the transplant team would be involved too, but I realized that FM was in the best hands possible – and they were as prepared as they could be for whatever they found and anything that might happen.

The surgery took about twice as long as expected, which caused some concern, but I chose to interpret it as meaning they HAD found something and were fixing it. I was right.

When it was finally our turn to be called to the “Doctor Meeting Room,” I sat as patiently as I could. When Dr. F walked into the room, smiling from ear to ear, I knew in that second that all was well. “Incredibly relieved” doesn’t even begin to touch that moment.

I smiled too and managed not to cry from all of the pent-up anxiety combined with lack of sleep until after Dr. F finished briefing us. It was all good news, and we are so incredibly fortunate that it was caught in time. Dr. F is my hero.

FM is now at home, feels great, comparatively speaking, and can now go about their life free from this ticking time bomb and the nightmare of suddenly descending intractable pain.

Epilogue

So, if you’re wondering why one might use AI, given that it certainly can be wrong and sometimes is – this is exactly why and the perfect example of not dismissing “good” in the pursuit of perfect.

Good was good enough. In this case, FM wouldn’t have died because AI was wrong, but might well have died had we NOT used AI to guide us to ask the right questions.

AI is not a physician and should never be used in place of one, but physicians miss diagnoses and make mistakes too – even at world-class institutions. Sometimes knowing the right questions to ask is a life-and-death matter. By the time an internal hernia is evident, it’s often too late.

I’ll also add that not one person was rude or dismissive of the information we obtained through AI or our advocacy. We educated ourselves using evidence-based medical sources and advocated respectfully. FM and I both use AI routinely and are familiar with these tools. The medical school is also embracing AI in specific circumstances.

Fortunately, the ED did not try to quickly dismiss FM with pain meds, given that this episode had the hallmarks of potentially becoming fatal. It had already been two days by the time FM went to the ED, and another several hours before FM texted me. That said, the medical team was running out of things to test.

Let’s face it. AI caught something the medical team didn’t. Medicine rules out the most likely and easiest to test for first, then proceeds to less likely scenarios, which means they have less experience with them. The doctor incorrectly told FM that an internal hernia had been ruled out. Until asked how often internal hernias were falsely ruled out, FM was probably on the way to dismissal. Thankfully, that’s when Dr. F was summoned.

Once Dr. F, the right surgeon for FM’s condition, arrived on the scene, FM’s care was phenomenal.

Learn How to Use AI Before You Need It

My advice? Learn how to use and interact with AI before you really need it. I never in my wildest dreams expected I’d ever use AI in this way – but here we are – safely on the other side of a life-threatening emergency.

Sometimes we don’t realize just how close we came in that brush with death until after we manage to avoid it.

I am forever in Dr. F’s debt for not having to enter that death date in my genealogy software. For him, it was surgery on Thursday. For us, it meant life.

The Dangerous, Dark Side of AI, and How to Protect Yourself

This is the fifth article in the AI series.

  1. The first article, Your Wonderful AI Assistant – Sometimes Wrong, Never Unsure, Always Convincing, explains why I’m writing this series and what to expect.
  2. The second article, All About AI – What It Is, What It Isn’t, and Why It Matters, explains what AI is, where it “came from,” the different kinds of AI, how it’s “trained,” plus examples of how it does and doesn’t work well.
  3. The third article, AI Assistants – The Good, the Bad, the Ugly and the Unseen, explains how AI tools work (and fail), the different types of AI tools, and when you may encounter them, even when you don’t realize it. This article closes with examples of successfully using AI, along with AI educational resources.
  4. The fourth article, AI and Genealogy – Brick Walls, Breakthroughs and Blunders, explains how AI is being used in genealogy by vendors and by individuals personally. It includes controversial topics like photo and image generation and discusses expert GPT tools and how I’m using them successfully.

I suggest that you read these articles in publication order, as they build on each other.

This article is perhaps the most important of the series, is deadly serious, and merits a disclaimer.

Disclaimer: I am not a lawyer. This article and others in this series are provided for general educational and informational purposes only. Information contained in these articles does not constitute legal, financial, or cybersecurity advice. It is not intended to identify or discuss every current or future risk, scam, threat, law, protection, or recommended response. One size does not fit all, and the best response for your circumstances may differ from what is best for someone else or from what is recommended here. Technology, criminal tactics, laws, and best practices change rapidly, and some of this information will inevitably become outdated after publication. Readers should independently verify current information and consult an appropriately qualified professional when necessary.

The Dark Side

By now, you know how AI works, that it can be used for good or evil, and that Generative AI creates things.

The dangerous part is that, because AI is so convincing in ways we’ve never seen before, it’s now easier than ever for you to become a victim in a heartbeat. This can happen easily, and you’ll have no idea until it’s too late. Media, meaning videos, images, and audio, can be generated about you without your knowledge, using your voice or likeness. And yes, it’s utterly terrifying.

You may be saying to yourself, “I’ll never become a victim,” but the scope of what it means to be a victim has changed over time.

Some generative AI is created to scam you, but other AI is created to harm or manipulate you or others close to you.

Perhaps someone wants to manipulate you into doing something dangerous, buying something under false pretenses, paying a ransom, believing that something happened when it did not, or voting in a specific way. I’m not going to touch politics here – but suffice it to say that I’ve adopted a “believe nothing” position unless I can confirm whatever it is through multiple reputable sources from the time the event supposedly occurred.

The Warning Signs Have Shifted

We all thought we knew the hallmarks of scams – but all of that has changed, and our misplaced confidence is actually dangerous. Now, those fake emails no longer contain spelling errors and weird, awkward language. Instead, they look authentic, sound completely professional and may take you to fake websites that look identical to the real one, prompting you to enter your username and password. You see where this is going, right?

The bad guys know you’re still looking for those old signs and signals, so they have dramatically upped their game, allowing them to easily gain your confidence and falsely “earn” your trust.

Today’s scams are, for the most part, built on garnering your trust, then employing sophisticated trickery – and they are extremely convincing. I absolutely hate that we now have to be hypervigilant, bordering on paranoid, all the time, but we do.

In order to provide contract services to FamilyTreeDNA, I’m required to undergo periodic security and threat landscape training. Like any other mandatory training, I dread it, but it’s absolutely critical to stay on top of this because what AI can do and how it can do it are changing very rapidly. I’m grateful for the professional training from KnowBe4, a leader in the security industry, and I’m sharing what I’ve learned with you.

I am NOT mincing words here. You WILL encounter these situations, and if you’re not constantly aware and on your game, eventually, you WILL fall for one of them. Yes, there are upcoming CAPS and red letters. Yes, I’m yelling!

I’ve distilled my most recent training along with other cautions into Roberta’s Ten Rules of AI and Social Media Safety. AI and your online presence are inextricably interwoven.

Roberta’s Ten Rules of AI and Social Media Safety

Rule 1: STOP! DO NOT CLICK!

Always engage your brain before your fingers.

I don’t mean it’s OK to click from time to time because you think the email is from someone you know or a business entity you do business with.

I mean do not click ever, with very few exceptions. One example is 2FA.

2FA (two-factor authentication) and some other systems will send you a link in your email immediately after you make the request. You will receive the email or text immediately, and you will be expecting it. That’s the key here. You asked for and are expecting this interaction now. Anything else, don’t click. Not tomorrow or the next day if you didn’t request something again. Regardless of how authentic it looks.

If you receive any other type of email indicating that there is something you need to do, go to the normal website DIRECTLY by typing it in and sign in to take care of that task.

The bad guys know that you’re periodically going to receive emails from, say, your insurance company, Social Security, or your bank, and they know exactly what they look like – so they create a copy of the authentic email and insert malicious links THAT LOOK COMPLETELY LEGITIMATE. Those fake links take you to exact imitations of the website you’re used to working with.

Here’s an example that I received today.

I received this e-mail, supposedly from Backblaze, the company that I use for my offsite system backups. What do you think would happen if I clicked on the “Backup Dashboard” link or the FAQ link?

You know exactly what this “Dashboard” link would look like – the real one. The malicious dashboard is going to prompt me to sign in, which gives the crooks my user ID and password. The keys to the kingdom. What they could access or do next depends on how the attack is constructed and any other safeguards in place, but the consequences could be devastating – including backing up my entire computer system to their fake site. Literally everything.

Even the thought makes me queasy. Consider for a minute what’s on your computer. Our digital lives live there. For example, if you have a little file called “Passwords,” get rid of it.

If you’re thinking to yourself that I could easily catch this by looking at the email header, here’s what it says.

Click to enlarge any image.

Given that I’ve never received this kind of email before, how would I know what sending email address to expect? I wouldn’t, and the bad guys are counting on that.

What did I do? First, stop and breathe – but that wasn’t my first instinct – even with all this training.

It’s frightening to think my system hadn’t been backed up in two months, but on reflection, that doesn’t make any sense because I normally receive reports. So, by slowing down, and literally stopping to think, I recognized the warning signs of a malicious phishing attempt and DID NOT CLICK ON ANYTHING.

I stopped my reflexes and let my brain engage.

Respond after considerationDO NOT REACT!

Instead, I signed in to Backblaze independently, from my normal sign-in link on their website, and checked. Sure enough, I confirmed that it was a phishing attempt – and a pretty good one too. My backups are just fine, and my system had been backed up regularly.

Had I fallen for this, nothing might have happened right away, because what happens after you click on a malicious link or visit a malicious site has changed. The harm may occur silently now, not immediately, and potentially indirectly. Think about that password list. (By the way, I don’t have a file like that, but many people do.)

If you click on something and “nothing bad happened,” don’t be so quick to be relieved. Now the bad guys can install monitoring software on your computer without your knowledge. Then, when you email back and forth with, say, your real estate agent about buying that lot down the street, the bad guys spot an opportunity and send you an email from the “title company” with instructions for where to wire the money.

Or, the bad guys text you. Wait, you’re thinking, “They don’t have my phone number.” Yes, they do, and they know your name.

Whether you know it or not, your email address and phone number are already circulating publicly and are easily accessible. There’s even more information available on the dark web, including passwords from data breaches and the names of family members.

Crooks already know far more about you than you realize, and that’s exactly why phishing emails and messages are so convincing.

Rule 1: Do not click, because that’s how criminals gain entry.

Rule 2: NEVER, EVER SAVE PASSWORDS IN YOUR BROWSER FOR ANYTHING FINANCIAL.

Once criminals gain entry, they exploit their good fortune – and your misfortune.

If you have already clicked on a malicious link as described under Rule 1 and entered a password, change that password immediately.

Never store financial or other important passwords in your browser. Use a legitimate password manager instead. Forbes and Cybernews published 2026 password manager lists, or you can use Google to find current information.

While we’re on the subject of passwords, don’t reuse them. Let’s say you stored a password for a subscription site like Ancestry in your browser, but you used the same password for your bank account. You know what’s coming, right?

If one site is compromised, the bad guys will try using that sign-in information on financial and other sites. This hacking technique is called credential stuffing and is what 23andMe claimed caused its 2023 breach.

AI is getting so good at being bad that it takes less and less effort to compromise your system, retrieve and exploit this type of information, especially if you don’t have the time, resources, or desire to keep up with new and evolving threats.

Rule 2: Don’t reuse passwords, remove any password files from your computer, and never save passwords for financial sites in your browser.

Rule 3: DON’T BELIEVE YOUR EARS.

Do not assume a familiar, well-known voice belongs to the person it appears to belong to, even if sounds like a close family member.

I can’t believe I have to write this, because it sounds insane.

Generative AI may only need as little as two seconds of your voice to create a convincing voice clone that sounds exactly like you. That is not a typo, although a few more seconds, like 10 or 15, produce even better results. AI can then clone your voice and create a conversation. It takes very little tech savvy, and instructions are all over the internet.

These are known as deepfakes – which can also include videos.

Let me give you an example of how this works. You’re asleep at 3 AM. Your adult daughter calls and says she’s being held hostage and you need to come right now. Or a similar scenario. Someone is in jail, has been in a wreck, or is facing some other emergency.

You’ve been awakened from a dead sleep, and you’re groggy, confused, and terrified. The adrenaline is surging through your body, but your brain isn’t fully engaged.

It’s EXACTLY your daughter’s voice. Exactly. You have no reason to doubt it. There’s no mistaking it – that’s her on the phone, and she’s in grave danger. Your heart is pounding, you’re immediately frantic and desperate, and of course, you would do anything in the world to save her. Your body has been jerked from zero to about Mach 5 in less than two seconds

The LAST THING you’re going to do is stop and question whether it’s really her. Of course it is. You’ve known her for the past 30 years – since the day she was born. “Don’t you think I’d know my own child’s voice?”

The answer is no, you wouldn’t. And you’re the target.

STOP and assess. That’s exactly what you should do in the moment, even though your instincts are to rush and do something. It feels like betrayal to let one minute pass without moving forward, but it’s not betrayal, and that’s exactly what you need to do.

Stop, take a deep breath, and THINK!

Agree on a protocol in advance with anyone who might ever call you in this type of situation. Select either a keyword, short phrase (blueberry pie) or a couple of questions that only you and they would know the answer to and that you can easily remember. Nothing you’ve ever put on social media or used as a password or recovery information.

Select something that only they would know, and that would be impossible to guess. Safe words or phrases. Words or questions that only you and they know the answer to, but not so complex that you can’t think of the answers under pressure. Write it down and put it in your nightstand, or save it in a disguised note on your phone, if need be.

What was your first car? Maybe arrange for a specific wrong answer – like the car they wanted but didn’t have.

How old were you when you fell into the hornet’s nest? Maybe they didn’t fall into a hornet’s nest at all, which is why this question and your pre-arranged answer are good choices.

Don’t use questions that could already be compromised or guessed.

Some people use intentionally “wrong” answers as their key to indicate that the call is legitimate.

This is also sound advice for anyone who receives a call from their workplace IT department instructing them to alter something on their system or network – especially if you are not expecting the call. And yes, even if you “recognize” the caller’s voice.

Verify that the call is legitimate through a secondary method that you initiate.

Depending on the type of “emergency,” another way to determine whether a claimed family emergency is real is to enable some form of family-location tracking service on family members’ devices. There are family locator apps in the major app stores. Be sure to stay mainstream with your selection. Life360 is well-known and works on both iPhones and Android devices, although this is not an endorsement.

Rule 3: Don’t believe your ears. Slow down and stop to assess.

Rule 4: DON’T ANSWER CALLS FROM NUMBERS YOU DON’T RECOGNIZE – EVER!

Why is answering calls from unknown numbers dangerous?

I know someone who used to love to “mess with” solicitors. Guess how the bad guys obtain those 2-15 seconds of your voice? Plus, they can cut and paste your words easily now, making it sound like you agreed to something that you did not.

They call from various numbers. Don’t answer. If you answer, they know they have a live one, and then those calls only get more numerous. They never stop. I block and report every single one as spam. Every time. Every single one.

Do you have voicemail? Remove your voice greeting and use the default one provided by your carrier.

Yes, I sound paranoid, but I’ve been on the receiving end of one of those phone calls, and they are TERRIFYING.

This danger flows both ways.

If you’re a public speaker, your voice is already out there, so you need to communicate clearly with your family NOW so that if they ever receive a middle-of-the-night call “from you,” you’ve already established a safety protocol. If you don’t have one, establish one today.

Additionally, mute your phone and set your notifications to ring-through only for selected phone numbers. This helps control who can reach you. In other words, in the middle of the night, the only numbers that will wake you up are the ones you’ve preselected. That does NOT mean those numbers can’t be spoofed, but it provides you with a layer of protection.

I only have half a dozen ring-through numbers in my phone, and everyone else can wait until morning.

I did this AFTER receiving that terrifying middle-of-the-night phone call, but you can do it now.

Rule 4: Protect yourself by not answering calls from phone numbers you don’t recognize, remove your voice from recordings, and establish your safety routine with your family.

Rule 5: DON’T BELIEVE YOUR EYES EITHER.

Your eyes may betray you.

Be extremely vigilant and highly selective about what you watch and believe. Ask yourself, every time, “Is this image or video real?”

Humans are wired to believe what they hear and see “with their own eyes,” but that metric doesn’t work reliably in today’s world.

Remain on guard and decide each and every time you watch something whether it’s authentic and actually represents what it claims to represent.

If you engage on social media, many of the Reels and TikToks you’ll see now are AI-generated. I can spot them a mile away, but they improve daily, and soon, today’s telltale signs will be gone like last year’s extra fingers, misspelled words, and two left arms.

For example, recently, someone published a pair of side-by-side photos contrasting the same location, supposedly taken several years apart. A then-and-now comparison to make a point. Except that the clouds in the background are distinctive and in exactly the same position in both photos. Yeah, no. One was clearly careless AI. It would have been easy to change the clouds too.

And that was just a bad AI photo, the videos are much more convincing. MUCH.

Google Lens, which allows you to submit photos, is your friend. If Google finds the same or a similar photo attributed to a different time or place, or posted in multiple groups with different claims, you’ve probably uncovered something less than honest.

Rule 5: View everything with suspicion and don’t accept anything you see as authentic without independent verification.

Rule 6: GUARD YOUR HEARTSTRINGS BECAUSE YOUR HEARTSTRINGS ARE CONNECTED TO YOUR PURSESTRINGS.       

Emotional manipulation is a cash cow for the bad guys.

If the story starts out with a kitten or puppy being thrown out on a road and saved, a child being adopted from foster care, a soldier returning home to their dog, or a similar high-drama emotional story – and you’re literally hooked in the first sentence or two – chances are it’s AI.

One clue is that these stories often pique your curiosity and are designed to be highly emotional.

How disappointing is that? We all love happy endings.

Some scams are even more heinous and take advantage of accidents, especially severe ones. The bad guys know that locals monitor local pages and will immediately wonder who is hurt and what happened – especially if their family members aren’t all at home.

AI bots that masquerade as people on social media and entire pages with very interesting names that are entirely AI-driven are very common on Facebook and other social media platforms now. Just this morning, beneath a photo of a local accident, four different bots used exactly the same language: “got this on video. Take a Peep,” with a link, of course. If you read, click, and engage in any way, including liking a post – you’re setting yourself up to be targeted one way or another. This kind of AI-generated content is replacing yesterday’s “copy and paste” scams, although we do still see those from time to time.

On videos or posts, you may be directed to follow a page “for more” or “click a link” (red flag) to find out the ending of the story. Don’t, no matter how much you want to know the ending.

When the purpose is not to steal your credentials or install malware, links may ask you to donate for Fido or Fluffy’s surgery, etc. The ask could be inferred or implied rather than direct and could say that Fido needs surgery by Friday and they still need another $200, or something similar.

This approach doesn’t ask you to contribute, but it makes you think you’d LIKE to contribute to help Fido. Think of this as essentially financial victim grooming using your own compassion and empathy against you.

Worse yet, the link could download malware to your computer, tablet, or phone.

If you have done anything like this, change any password you entered, run an up-to-date antivirus scan, and seek professional help if you suspect malware or tracking software was installed. Also enable 2FA so that a stolen password alone is not enough to access your account.

Yes, I know it’s a pain, but not nearly as big a pain as the alternative.

Aside from the obvious attempts at theft, why do people create these links? I mean, I just want to know what happened to Fluffy.

Here’s what Google’s AI-generated search summary has to say, along with links to the sources it provided.

The really sad part is that truly legitimate organizations suffer because of the level of distrust we must maintain today. If you’re feeling generous, before doing anything, including sharing the story for others to read, check alternate sources about the legitimacy of claims and fundraisers. You don’t want to share and play a part in victimizing your friends.

For example, a few years ago, the Happy Cat Sanctuary burned, killing the owner and many cats. Friends launched a legitimate online fundraising campaign to treat the 150-200 cats that survived the fire. This incident was covered by local news and wasn’t a one-off “sad story” social media plea that couldn’t be verified. I confirmed through local news outlets that the fire occurred when claimed and that the fundraising campaign was legitimate.

If you’ve relented and clicked to watch a reel of some sort, and an ad pops up before the end of the story, or you need to click or follow something, you’ve just taken the bait – so stop right there, spit it out, and realize what makes you vulnerable.

Let’s discuss YouTube, where ads have been part of the platform forever. However, there’s a LOT of AI-generated content on YouTube that is compelling but not authentic.

For example, there’s an AI singer, Michael Bennett, also Mikhail Bennett, with AI-written songs and an AI-generated voice. The combination is very compelling and moving, and it sounds lovely.

Whoever generated that content also took advantage of America’s Got Talent by showing “Michael” competing there with extremely emotional songs. None of that is true. It’s an incredible song that resonated with so many, including me, and the friend who shared it with me, but the video was “over the top,” which was the first red flag. I also noticed the tear never moved on his cheek, and the audience didn’t appear quite “normal.” He also looked “different” in other videos, as though he’s not the same person, but similar. Another AI signal. That’s 2026. By 2027, those telltale signals will probably be gone. Forbes wrote about the fake here.

Remember, if it outrages you, piques your curiosity, or tugs at your heartstrings, that content has probably been generated for exactly that purpose. Don’t click and become a victim.

Rule 6: Guard your heartstrings, and if something seems overly emotional, weird, too much, or just “off,” trust your gut, hold on to your wallet, and verify, verify, verify.

Rule 7 – FLASHING RED NEON SIGNS THAT SAY SLOW DOWN AND STOP. 

Manipulation signals should flash like red neon signs, telling us to put the brakes on.

  • Slow Down
  • Think
  • Stop

Any email, call, text, or other content that creates any of the following reactions should trigger those brakes:

  • A sense of urgency – “If you don’t reset your password by 5 PM, you’ll lose access to…” If you click, you are probably signing into a copycat site that looks exactly like the real one – except it’s stealing your credentials so the bad guys can sign into the real site to steal more than your credentials.
  • Anything frantic – There’s activity on your credit card. “We need you to enter your password here to dispute the charge.” Or, “click here to sign in to see the charge.” Or, “call this number.” This is different from a text I received in my bank’s normal message thread confirming that I had indeed written check number xxx for $xxx.
  • Pressure, direct or implied – “Your subscription has lapsed…click here to renew.” Go to the website and renew – never, ever click, no matter how legitimate the email looks. Full stop!
  • Anything unusual from someone you know. “I’m in a restaurant and in a pickle. I forgot my billfold. Can you please Venmo me $50 so I can pay my bill?” Call them using the phone number that you already have. Do NOT reply to the text or click to call that number.
  • Manipulative instructions – “We’ve received your order. The file is attached.” This is especially effective if you HAVEN’T ordered anything because it generates both curiosity and concern. Do not, under any circumstances, click on an attachment you’re not expecting. Slam on your mental brakes!

This KnowBe4 alert arrived today and demonstrates several flashing red neon signs at once.

This scam arrives as a Facebook Messenger message masquerading as Facebook, or Meta itself. The message even includes an accurate logo, but it is not legitimate. Red flags include the concern it generates, an unexpected PDF attachment, a threat of imminent account deletion, and the sender’s name is one letter off. In the message, “verified” is spelled “verrifed,” with two Rs, but if you’re focused on the words “permanently deleted,” you’ll never notice that. You may be panicked and not thinking clearly. That’s exactly what they are counting on.

Although there are often no misspelled words in scam emails today, in this case, the misspelled username is your first clue. Two of my friends received this through Messenger today, reported it, and an hour or so later, I received the notification from KnowBe4.

The bad guys trick you by making you feel that the action is:

  • Completely safe – because it came from someplace or someone you routinely communicate or do business with (but it really didn’t and the bad guys are trying to trick you).
  • Urgent – someone is trying to compromise your account, and you need to <fill in the blank> right away (except complying compromises your security).
  • Required to avoid negative consequences – if you don’t finish this training by Monday morning, you’ll no longer have access to your accounts (except it’s a fraud, trying to get you to sign in through a very convincing authentic-looking but malicious portal).

In any of these types of situations, don’t comply or reply, and never return calls to any number they give you. Find the number on the back of your credit card, for example, or sign into the site you’re already familiar with to take care of business.

Always ask yourself:

  • Is this normal?
  • Does it feel “off”?
  • Why?
  • What am I giving away? It’s not always money. Your information is gold, too.

Rule 7: Slow down, stop, and evaluate. A sense of urgency is a flashing red neon sign designed to stop you from thinking.

Rule 8 – STOP RANDOMLY ENGAGING AND LOCK DOWN SOCIAL MEDIA.

Algorithms control what you see.

Worse yet, once you click or even expand to read, the social media algorithms send you more of the same, which is the exact intention of the creators. The phenomenon is often referred to as a social media bubble or echo chamber because it reinforces what you believe based on what you’re seeing and continue to see.

It used to be that ugly political content was restricted to election cycles, but not anymore. It’s regular daily fodder and can easily be manipulated. The key, however, is that whatever you watch or read, you’ll see more of it in your social media feed.

Another effect of reading one of those scammy but very interesting and engaging stories is that Facebook now uses AI (how ironic, right) to show you more of the same. It’s a never-ending cycle.

One time I accidentally clicked to watch a reel, and it took days of clicking on the little “X” in the upper right-hand corner of the videos (or the posts) to signal to Facebook that I really didn’t want to see anything else like that. Hint – this works with ads too.

It’s fine to read that fun public story – but you don’t have to engage by clicking and liking. Clicking DOESN’T DO ANYTHING FOR YOU, but it does provide information about you to other people, including AI bots and the social media platform itself.

If you ever “like” or comment on a public post on social media, your reaction is visible to everyone, including AI bots, and you’ve given them information about yourself that they can use to target you more effectively. Just stop.

Don’t expose any more of your personal information than is already out there – and you might be surprised just how much there actually is.

Do you use your real name? Is your birth year, or much worse yet, your complete birth date displayed in your public profile? If so, remove it.

Do yourself a favor.

  • Google your name with your state.
  • Google your phone number.
  • Google your email address.

Your information doesn’t even need to be on the dark web for someone to find very revealing data about you.

You can discover even more about yourself, or anyone else, by checking out BeenVerified.

Record aggregators such as BeenVerified also provide the names of people who live or have lived with you and with whom you’re associated. In other words, your family members.

It’s so easy to unintentionally feed the data-gathering machine.

Ancestry includes voter-registration lists, where available, complete with full names, addresses, birth dates, and other personal information through 2023.

Protect yourself, where possible, and never publicly display your birth date or year on any platform. Do note that this information can be part of recovering your account, should it become compromised, so if you include that information, privatize it.

Are you on LinkedIn? That’s another avenue for information gathering, including your employer.

There’s not much you can do about information that’s already out there, but you can stop providing more through social media.

I wrote the article titled STOP, THINK, & RUN – Stop Innocently Giving Your Information to Cybercrooks on Social Media, which explains how to lock your accounts down, and why you should.

Rule 8: Lock your social media accounts down and zip your lip.

Rule 9: LEARN THE NEW THREAT LANDSCAPE

The threat landscape has not improved for us, that’s for sure. The crooks have gotten smarter and much more effective with their AI assistants.

Yesterday’s Nigerian princes, those handsome widower generals in uniform, and buxom young women randomly targeting people who comment on public posts on social media are somehow almost all gone, although not entirely. They’ve been replaced by something much more dangerous. AI makes everything easier – including crime.

Now, the criminal’s objective is to get you to take an action that isn’t in your best interest.

AI makes both impersonation and personalization much easier and more convincing, and attacks may now involve multiple methods in tandem.

The most convincing attacks use two channels. For example, they both email and call you, which makes the communication seem more legitimate, which in turn makes you feel more secure. They may claim that your credit card has been compromised or begin with, “This is your bank…”

Worse yet, you really can’t tell and may have no way of knowing whether the communication is legitimate, so you go ahead and click because you’re tired and “it’s probably fine,” except it’s not.

The bad actors may have already compromised your system or phone if you clicked on something you shouldn’t have, and they are just waiting to exploit it by capturing your login information – including your password.

They may have been monitoring your communications for some time now, not just waiting for any opportunity, but an exceptional, highly profitable opportunity.

Never use a “call back” button, telephone number, or link supplied in the message. Call the bank or whomever directly at a number you can confirm, or use another form of communication – like walking in the door.

I was at the bank in person recently, and they are now warning people about scams before they transfer money on your behalf. You are required to click to acknowledge that you read the scam warning signs they provided. The bank was also reminding people that debit cards are a “direct siphon into your bank account” and someone can easily drain it if your card or PIN is compromised.

If someone fraudulently charges something to your credit card, you can dispute it, but if they empty your bank or retirement account, the money may be difficult or more likely impossible to recover. Report any suspicious activity to your financial institution IMMEDIATELY, regardless of the hour, because the outcome may depend partly on how quickly you report it.

Rule 9: Learn the new threat landscape and keep current.

Rule 10: NEVER UPLOAD ANYTHING WITH PRIVATE INFORMATION, INCLUDING NAMES – YOURS OR OTHER PEOPLE’S.

This includes uploading your monthly budget worksheet to AI, your tax information, your DNA match list with other people’s names from a DNA testing site, etc.

Genetic genealogists, I’m looking at you here. If the data isn’t already in the public domain, DO NOT UPLOAD IT to AI agents.

Your browser will not protect you, and neither will a VPN. I’ve had people tell me that both of these will protect what you upload when using AI. They don’t. Neither prevents an AI service from receiving information that you intentionally upload to it.

Don’t fall for companies that encourage you to “upload your DNA file” for “better” information or to learn how you match ancient specimens. Check credible sources that are well-known and respected in this industry, such as my blog, Diahan Southard at Your DNA Guide, or the Genetic Genealogy Tips and Techniques Group on Facebook. If you discover that none of us, meaning me, Diahan, or the administrators of that Facebook group are recommending a company, pause to ask yourself why.

When considering an upload, ask yourself:

  • Who are those people, anyway?
  • Where are they located?
  • What are their credentials?
  • What are they doing with your autosomal DNA file?

If you’re thinking about uploading your DNA or matches to an AI tool or to a company you know nothing about merely because it “sounds good,” just don’t.

If you’re going to err, err on the side of extreme caution because once your DNA is “out there” and exposed, you can’t just take it back like it never happened.

Rule 10: Never upload your own private information to AI or any other service that you have not thoroughly vetted, and don’t upload your match information or anyone else’s private information without their specific permission.

In Summary

I chose to address AI’s dangers after first exploring its benefits in the earlier articles because I don’t want you to think I don’t like AI. I absolutely do. I use AI in some form every day.

However, AI can also be extremely dangerous, especially for the unwary. I cannot emphasize this enough.

AI will become more advanced and “better,” which means we, as consumers, have to be even more vigilant. While the idea behind “Who are you going to believe, me or your lying eyes?” was once a Marx Brothers punch line, and “Lyin’ Eyes” later became an Eagles song, today that warning pertains to AI and social media, both separately and together.

I want you to stay safe. AI is one of the tools that we, as genealogists, can use quite successfully under some circumstances. Just don’t get out over your skis.

To recap:

  • Don’t click
  • Don’t believe your ears, or eyes either
  • Never save important passwords in your browser
  • Guard your heartstrings
  • Remain vigilant
  • Slow down, stop and assess
  • Verify independently
  • Protect yourself
  • Put a family protocol in place
  • Stop randomly engaging and lock down social media
  • Guard what cannot be recovered
  • Don’t upload private information without thoroughly vetting the service
  • Never upload other people’s private information without their permission
  • Educate yourself and stay current

While the specifics of each platform change quickly, the underlying fundamentals of safety and increased vigilance will remain constant.

As mentioned in the third AI article, follow Mark Thompson and Steve Little, the Family History AI guys, for updates.

Stay safe and enjoy the ever-evolving world of AI.

But remember…

Always, always be suspicious. You may only get to be wrong once.

_____________________________________________________________

Share the Love!

You’re always welcome to forward articles or links to friends and share on social media.

Subscribe!

If you haven’t already subscribed, it’s free. You’ll receive an e-mail whenever I publish by clicking the “follow” button at the top of the main blog page, here.

Help Keep This Blog Free

I receive a small commission when you click a vendor link in my articles and purchase that item. This does NOT increase your price but helps me keep the lights on and this informational blog free for everyone. Please click on the affiliate links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research

A Little Something for Their Final Journey

It was five years ago this week that I visited my parents’ graves for what was probably the final time.

I gathered silk flowers from my home, which was being emptied, arranged them into glorious bouquets, and took treats – for both them and me.

You don’t see it in the photo above, where I was just setting up for our picnic on the picnic quilt that always lives in my car, but it took me an entire box of Kleenex to get through that picnic and what I had to share with them that day.

This was it. I wasn’t coming back. They were already buried six hours away from where I lived then – and now that distance is measured in days, not hours. There’s no one left there to visit now, and it’s not on the way to anyplace.

Dad loved popcorn and cheese cubes with turkey and salami, and Mom absolutely lived for Hershey bars.

Of course, I knew “they” couldn’t enjoy them in the here and now, and I was probably just feeding the wildlife. It was more about the ritual, the expression of love and caring, tinged with regret that I can no longer steal cubes of Dad’s cheese (he just smiled at me) or give Mom oversized Hershey bars.

Mom smiled at me too, but for an entirely different reason.

Recalling sitting on that quilt, discussing things with Mom and Dad while baking in the summer heat, much as I remember doing on the farm, makes me smile now too.

Facebook memories brought that day back this week. As I lay in bed in the silent night, reliving that hot July day picnicking with Mom and Dad, I realized that their graves aren’t the only places I had “left them something.”

Until that night, I didn’t realize that I had done it twice, once for each of my parents, but never for anyone else.

Dad

All of my regular readers know that Dad was actually my stepfather, and that he had lost his only daughter, Linda, as a baby.

No one can ever take another person’s place, but Dad told me twice that he “got his daughter back” when he married Mom. My allergies immediately acted up.

My biological father died when I was a child, so I felt like I had hit the jackpot and lucked into the best father ever when Mom married Dean.

I worshipped the ground that man walked on.

Dad died in 1994, following a horrific, progressive disease. His death was a devastating loss. On top of another loss just the year before.

Now, Dad was well-known for his orneriness, practical jokes, and sense of humor. Perhaps what made it even funnier was that he was such a quiet man – the last person you’d expect as the culprit.

So, when we all gathered at the church for his viewing and found no casket, we patiently waited for the funeral home to show up with Dad.

But when that visitation hour passed, and there was STILL no Dad, we began to worry. Mom was frantically calling the funeral home, which was about 20 miles away, but no one answered. She was a nervous wreck.

My brother was laughing. Most people were quietly and awkwardly visiting, hoping nothing was wrong.

Our imaginations were running wild. Had there been an accident? Was Dad lying someplace beside the road in his Sunday finest? Let’s face it, Dad was already deceased – he couldn’t die twice if there was an accident, but what if, what if Dad was at the wrong church or some such thing? Did they bury him by accident?

Finally, the hearse pulled up outside the church, and we heard doors slamming. Mom rushed out and asked, in her “not my church deacon” voice, where the devil they had been. Well, devil might not have been the word she used, but whatever. I was all too personally familiar with that voice, and I knew they were in BIG TROUBLE!

As it turned out, they had gotten the times mixed up, making Dad late for his own funeral.

Perhaps it was a combination of nerves and grief, plus Mom clucking around like an angry wet hen, but that whole scene just struck me as incredibly funny, and I started to laugh.

Mom gave me the side-eye like only mothers can give, so I tried to stifle myself – which made me laugh even harder, snorting through my nose.

About this time, the men from the funeral home were trying to carry the casket in the back door and up the narrow steps into the church. At the top, there was a right-angle turn, and let’s just say the casket and the men didn’t quite make it.

Well, they kind of made it, but one of the men got pinned between the casket and the corner of the wall in a very awkward place. He was also trying very hard not to let on, but you’d have had to be both deaf and blind to miss what was happening.

My mother was following this entourage up the stairs, and even she stopped talking as the scene unfolded.

By this time, I was laughing hysterically beyond any semblance of composure, tears streaming down my face, and so were most of the guests. Laughter like that is highly contagious. Most of the men were trying to help, but we had to back Dad down the stairs to free the trapped man.

I’m laughing as I write this. I can see it all over again and just can’t help myself.

Right about that time, the most inappropriate thought popped into my head. I couldn’t help it. I wondered if Dad had paid them to ensure that he was late for his own funeral.

The ultimate prank. He certainly WOULD have done that – in a heartbeat. Only question that remained was DID HE? And of course, we’ll never know.

All things considered, with everyone still laughing and crying, we were hardly in the proper frame of mind to begin a funeral, so the minister suggested that we have the viewing and recompose ourselves before the funeral. You really can’t start a funeral with everyone laugh-crying, and we were already so late by that time that it didn’t matter.

Mom had dressed Dad in a suit. I had only ever seen him in a suit a handful of times.

His wedding to Mom, my wedding, Gary’s wedding, church pictures, and maybe one other time.

Dad hated suits. He was a dyed-in-the-overalls farmer, and those overalls would have suited him much better than a suit. However, I’d wager that Dad knew Mom would dress him in a “funeral suit” for his funeral, so maybe this was his way of commenting on that.

Regardless, by the time it was my turn to step up to the casket for the final time, as grief-stricken as I was, I certainly appreciated the levity that he had introduced that day. Yes, I’m crediting him!

I dug around in Mom’s purse and found a small pair of scissors. As an Avon lady, she had literally everything in there – her purse was bottomless. I cut a lock of my hair, found a ribbon or piece of string buried in the depths of Mom’s purse, tied it around the lock, then lovingly tucked it into Dad’s starched shirt pocket for eternity.

I patted his hand one last time and told him I loved him as I smiled through my tears. I bent close and whispered that he had done a fine job as my tears dropped onto his white shirt. I swear – I swear – I saw a smile flicker across that man’s lips just for an instant.

I hadn’t planned it, but I sent Dad on his last journey with a little bit of me in his pocket. Forever.

Mom

Mom was an Avon lady for the last quarter century of her life. She loved to dress up and look her finest, so Avon was a perfect fit for her. Plus, it gave her an excuse to check in on the elderly and those with challenges in the community. She was always taking food or something to someone. Every. Single. Day.

Mom retired in the spring of 2005 at 82.

One of her longtime customers took this photo of Mom on her last day making Avon deliveries.

Mom wanted to retire with her best sales year ever, and I purchased a lifetime supply of soap, bubble bath, and Skin-So-Soft. Maybe two lifetimes’ worth. Trust me when I tell you that I’m still using Avon products.

Every Christmas, we all received our favorite Avon items in our Christmas stockings from Mom. Plus, Avon Care Deeply chapstick. Didn’t matter – man, woman, child, elderly neighbor – someone in line at the grocery whose lips looked chapped. You got Avon chapstick.

As far as I’m concerned, one can never have too much chapstick. I have chapstick, aka lip gloss, everyplace, including one or two of Mom’s that I still cherish and keep in my nightstand and desk drawer.

When Mom retired, she was one of her own best customers and stocked up on things.

Just this past week, my husband found a little wooden box that was in a drawer in his nightstand in our old house. He opened it, and voila, there they were.

Three chapsticks from Mom.

Vintage Avon Care Deeply from 2002, 2004, and 2005. Mom really liked Jim. He received the first one even before we were married. He has now kindly given all three to me. Now that’s true love.

How can chapstick make you cry?

Mom passed away unexpectedly in the spring of 2006. She had a stroke and managed to crawl into her closet and put her “pretty shoes” mostly on. No one is quite sure how she managed that, but she did. That’s how we found her. She loved shoes.

Mom’s funeral was much more subdued than Dad’s. My brother and I met with a different undertaker, so she would actually arrive at the church on time.

I selected Mom’s clothes along with her favorite “pretty shoes.” The funeral director told us that he could not get high heels on her feet. We told him that whether he could get them fully on or not, he was to get them as far onto her feet as possible – and do something to make sure they didn’t fall off. I didn’t care if he tied them on. She needed her pretty shoes. She would haunt me forever otherwise.

Saying goodbye to a parent just before the casket is closed is one of the most difficult things you will ever do.

Mom always had everything in her purse, including spare Kleenex, which she often tucked up her sleeve at her wrist, under her watch band so they would always be quickly available.

She was always handing out Kleenex at church to anyone who needed it, and probably several people who didn’t actually need one, but she thought they might. She accused me, accurately, of never having a Kleenex when I needed one. How was I supposed to predict that?

After Mom passed, we found clean Kleenex everyplace. In her pockets and purses, of course, used as bookmarks, and even tucked into the door handles inside her car.

On the day of her funeral, I had a full box of Kleenex with me. I was clearly going to need them and couldn’t depend on Mom for that anymore. She would have been proud.

As always, I had multiple Avon chapsticks, not the imposter kind, in my purse and pockets. Somehow, Mom would have known if I cheated with something other than Avon.

Standing there, saying my final goodbyes, I realized that I could NOT send Mom off into the afterlife without Kleenex and Avon chapstick, both of which she used religiously. So, I tucked a few Kleenex into one of her crossed hands and a chapstick into the other, closed my eyes for a minute, said a little prayer, then nodded for the casket to be closed as I wiped my eyes. They had been patiently waiting for me. I was struggling. Part of my heart was in there with her.

The funeral itself was a blur. When the minister finished, Mom was loaded into the back of the black hearse for her final ride along those oh-so-familiar roads to the cemetery. The little white church was at a farm crossroads, and the cemetery was probably a dozen miles away, down country roads too narrow for center lines. No one needed them anyway. The only people out there were members of local farm families who all knew each other, slowed down, and waved.

Suddenly, the hearse slammed on the brakes. We were in the car immediately behind, and I had a very up-close view of its brake lights, just before we came so close that they disappeared from view. I waited for the crunch, but fortunately, we managed to stop with an inch or so to spare, but we were quite shaken. Both figuratively and literally.

Someone had run the stop sign in front of the hearse, which missed the car by a hair’s breadth. For me, that was déjà vu, because years before, the only life-threatening accident I had ever had occurred a few miles on down that same road, under the same circumstances – minus the funeral procession.

I couldn’t help but think about the supreme irony of potentially being killed in Mom’s funeral procession, on that same road, some two decades later. I was more than a little shaky already, given the circumstances, and that didn’t help one bit.

But then, an even worse thought struck me.

What if Mom’s chapstick had been knocked out of her hand and was rolling around beyond her reach for eternity? How could I condemn her to that fate? If you know, you know.

Did she drop her Kleenex?

But perhaps more importantly, did her shoes fall off?

ECGGC 2026: East Coast Genetic Genealogy Conference – Both In-Person and Virtual

I hope you’ll join me and a whole trove of other wonderful speakers at the East Coast Genetic Genealogy Conference August 21-23 in Boston. The in-person conference is being held at the Embassy Suites at the Boston Logan Airport, so you don’t need to worry about transportation into Boston after arrival.

The great news is that you don’t have to be present to participate, and you don’t have to worry about missing sessions you wanted to attend.

All sessions, except for the Sunday morning ISOGG meeting, are either livestreamed, then available to watch later, or are available on-demand on their scheduled day.

I love this conference because it focuses strictly on genetic genealogy and how to apply it successfully to genealogy. Not to mention, it’s like a family reunion! I can hardly wait to see everyone!

Keynotes

  • Steve Little and Mark Thompson – Friday evening: The AI Frontier in Genetic Genealogy: Where We Are and Where We’re Going
  • Jennifer Zinck – Saturday morning: It Takes a Village
  • Kevin Borland – Sunday Morning: Mining A Chromosome 22 Pile-Up: Clustering Through a Documented Colonial Lineage

Speakers

In alphabetical order, speakers include:

  • Kelli BergheimerUnderstanding Your DNA Health Reports, and, Finding an Ohio Pioneer Family Using Mitochondrial DNA
  • Katherine BorgesDNA and DAR, and, Sunday morning: ISOGG Meeting
  • Kevin BorlandMining A Chromosome 22 Pile-Up: Clustering Through a Documented Colonial Lineage (keynote)
  • Greg Clarke – Welcome and Introduction
  • Janine CloudTurning a Brick Wall into a Community: Using Documents and DNA Together, and, with Roberta Estes: Between the Records and the Results: Tracing Ancestors in Mixed Lines
  • Roberta EstesMitochondrial DNA-Z: My Results are Back, Now What?, and, at DNA Academy: Using Ancient Connections to Unlock Genealogy, and, with Janine Cloud:  Between the Records and the Results: Tracing Ancestors in Mixed Lines
  • Mags GauldenThe DNA of a Revolution
  • Kate Penney HowardWhen the Story Isn’t True: DNA and the Family Legend Problem, and, Gerald Hawley and the Silence: What Erased Ancestors Teach Us About DNA Research
  • Daniel HorowitzMyHeritage DNA Basic Level, and, MyHeritageDNA Advanced Level
  • Peggy JudeYour DNA Toolkit: Expanding Your Research with Third-Party Tools, and, Step Up to the Plate: Winning Strategies for Connecting with Your DNA Matches
  • Dawn KosmakosUnraveling the Identity of Arthur Burton
  • Steve LittleSolving a Paternity Puzzle: AI-Assisted Match List Analysis in Endogamous Appalachia, and, keynote with Mark Thompson: The AI Frontier in Genetic Genealogy: Where We Are and Where We’re Going
  • Melanie McCombUsing DNA to Identify Ancestral Origins
  • Adina NewmanNavigating Your Jewish DNA Results, and, Introduction to DNA Painter: Strategies to Enhance Your Genealogical Research
  • Jonny PerlUnderstanding the What are the Odds Tool at DNA Painter
  • Rhonda RoedererThe Power of DNA – Making Life-Changing Connections
  • Diahan SouthardI Did Everything Right. So Where’s My Ancestor?, and, There’s Always a Next Step
  • Jerome SpearsOur Genetic Explorer’s Journey
  • Mark ThompsonApplied Artificial Intelligence for Genetic Genealogists, and, keynote with Steve Little: The AI Frontier in Genetic Genealogy: Where We Are and Where We’re Going
  • David Vance – At DNA Academy: NGS Testing for Autosomal DNA
  • Rob WarthenCommon Ancestors at DNAGedcom – Building Trees
  • Jennifer ZinckIt Takes a Village (keynote), and, Unleash the Power of DNA

You can view the schedule and session information here.

For people attending in Boston, additional activities are being held at the American Ancestors office and library on Thursday.

DNA Academy

Saturday evening, the ECGGC hosts DNA Academy. Each year, this fun, interactive, advanced learning session is hosted by Mags Gaulden and includes a panel Q&A session, and speakers.

From the ECGGC agenda:

Join Mags Gaulden, Dave Vance, Roberta Estes, Rob Warthen, Katherine Borges, and Jennifer Zinck for a Q & A panel with special guests to start, then sit back and enjoy a presentation on NGS testing for autosomal DNA, by Dave Vance, and “Using Ancient Connections to Unlock Genealogy”, by Roberta Estes.

Exhibit and Vendor Hall

There are both in-person and virtual vendor exhibit halls, so visit both if attending in person. Vendors who sponsor this indispensable conference are the ones who keep it affordable for the rest of us, so be sure to stop by their booths.

Register

The conference starts in just a month, but there’s still time to register, here. In-person costs $295 and virtual is $175. Both are great values. I already have my plan in place for which sessions I’m attending in person, and I’ll watch the rest after the conference.

Hope to see you there. Please be sure to say hello.

_____________________________________________________________

Share the Love!

You’re always welcome to forward articles or links to friends and share on social media.

Subscribe!

If you haven’t already subscribed, it’s free. You’ll receive an e-mail whenever I publish by clicking the “follow” button at the top of the main blog page, here.

Help Keep This Blog Free

I receive a small commission when you click a vendor link in my articles and purchase that item. This does NOT increase your price but helps me keep the lights on and this informational blog free for everyone. Please click on the affiliate links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Uploads

Genealogy Products and Services

My Books

Genealogy Books

Genealogy Research