RootsTech 2024: DNA Academy and Ancestry Announcements

March the 1st. Remember that old saying about March? If it enters like a lamb, it will leave like a lion, and vice versa.

Look what greeted us on the morning of the second day of RootsTech.

Whoo boy.

The good news, if there was any, was that this was Friday’s forecast for Saturday, and of course, it might, just might, be wrong. Fingers crossed!

The second day of RootsTech was jam-packed, as you can see in the MyHeritage booth below. I wondered if one reason for the extra-large Friday crowd was the weather forecast for Saturday.

I had just finished my booth talk for MyHeritage titled “Leveraging Triangulation – From 3 to Many” and stepped aside to take a picture.

This half-hour presentation defined triangulation as a three-legged stool and discussed when and how to use triangulation at MyHeritage.

I covered:

  • How to use close relatives, including parents, to determine which side your matches are on.
  • Why you can’t use immediate family members for triangulation.
  • How to use triangulation with Shared Matches and the Chromosome Browser
  • How to use and verify Theories of Family Relativity with triangulation
  • AutoClusters as a triangulation roadmap
  • Using AutoClusters and triangulation to determine which DNA descends from whom
  • Bonus hints

Maybe I should turn this presentation into a blog article. What do you think?

DNA Academy aka An Afternoon in the Life of a Presenter

I only had about 45 minutes between the end of the MyHeritage session and the beginning of my class, “DNA Academy: Pulling it All Together – Tests, Vendors, Tools & You.”

I’m very grateful that RootsTech provided the opportunity for this experimental full-afternoon session, which provided the underpinnings for other DNA classes and sessions.

I had practiced and practiced to ensure the slide and topic pacing was fast enough to get through all the slides but not so fast that I would lose people.

Losing someone in a class of this duration means that they miss everything thereafter – and that could be a lot more than your normal 45 to 50-minute class.

Therefore, I needed to be prepared to take questions during the class. That’s always a bit risky because some questions are more like a short story, and you don’t want to run out of time at the end for your slides.

So, yes, I was a bit nervous. I was also concerned about technology gremlins named Murphy that seem to be ever-present. I absolutely did NOT need gremlins attending too.

There was no time between sessions for any kind of a proper lunch. No time to stand in line for food. However, I had to eat since I would have no break until after the class ended at 4, and then only after all of the attendees had left. On Sunday, I had purchased Lunchables at the local grocery store, so I bought a container of fruit and a bag of Doritos at one of those quick grab-it places on the way to my classroom and had a picnic in the back of the room as attendees began filtering in.

I headed for the front of the room with my laptop bag just as the tech person arrived to assist with setup. RootsTech encourages speakers to use RootsTech-provided equipment since they know it’s set up correctly to work with the AV equipment. That makes sense, but I always bring mine, just in case.

RootsTech also generously provided a stool so I wouldn’t have to stand for the entire afternoon.

Our first challenge was that the audio wasn’t working correctly, and never really did. We worked on it until the session started, and I even sent for the tech after the session began.

Eventually, after much fiddling around, I gave up and took the lavalier off. I held it near my mouth for the entire afternoon after finding that “sweet spot” with the assistance of everyone in attendance. We needed to find the mic position where people in the back of the room could hear me, it wasn’t so close it sounded like I was spitting, and we weren’t getting feedback. That seemed to be about a quarter-inch window. It was not ideal, but it worked, and I was very grateful for the audience’s help and patience. Teamwork!

The second challenge was that the RootsTech laptop defaulted to “Presenter View,” which means that your Powerpoint slide is in the upper left quadrant of the laptop screen, the next slide is shown at right, and “speaker notes,” if you’ve created any, appear at the bottom.

I don’t use speaker notes because I don’t want to sound like I’m reading aloud. Therefore, I never use Presenter View. I use the slides to remind me of what to say, and I know what’s coming next.

I initially thought, “Fine, so long as the slide advance works.” It wasn’t until after I began, and after the AV tech was long gone that I realized how small the RootsTech laptop screen was, meaning how SMALL my current slide was. To my horror, I realized that I couldn’t clearly see some portions of my slides.

OH NO!!!

I couldn’t exactly take my glasses off, lean over the podium, and squint. No, that would never do. I also couldn’t move the laptop closer without disrupting the setup and cables.

I also couldn’t see the movie screen to my left that attendees were viewing because I was positioned directly beside the screen and only slightly forward. I could see that the image was showing on the screen, but I couldn’t read anything on the image from that angle.

Crumb!

Therefore, I really had no good or detailed view of my own presentation – for 2.5 hours.

All I can say is that it’s a VERY good thing that I obsessively practice ahead of time, because that’s the ONLY thing that got me through.

I asked for the tech again to assist with the audio issues after trying multiple ways to adjust things myself, and he sent a message back to just move the lavalier up on my clothing. It was already as high as it could be placed, so not helpful.

Why am I telling you this? Often, people often don’t realize how much is beyond the speakers’ control and how much we just roll with the punches as best we can. Attendees are acutely aware of their experience, especially when it’s sub-optimum, and often blame the speaker.

One attendee asked if I could raise the image projection on the screen towards the top. I couldn’t control the image location at all. I knew that if one person couldn’t see because the image was too low on the screen, other people probably couldn’t either, and I felt awful.

Speakers are used to overcoming challenges, but no one wants to attempt to simultaneously overcome and compensate for several issues in the same presentation.

I wound up apologizing more than once to the class. These people had been kind enough to choose this long class and I wanted their experience to be the best possible.

I was very grateful for the people who said something positive afterward and for this person who left feedback on my blog.

A number of people were unhappy because the session wasn’t either live-streamed or recorded. Speakers have no way of knowing or influencing which sessions RootsTech selects for broader consumption. I’m sure they want to livestream a mixture of topics that would interest a variety of people.

I’ve reached out to Legacy Family Tree Webinars to see if they are interested in this class, although I would need to divide it into thirds. I want to leverage this effort and make it available to others who can benefit.

Legacy Family Tree Webinars are free to everyone for the first week, then available in the subscription library.

Does this sound like a good idea?

Ancestry Announcements

After DNA Academy ended, I headed back to the show floor. The second day of RootsTech is always the “late night” with activities until about 7:30. They close earlier, around 5, on the first day, and at 3 on the final day.

I was interested in Ancestry’s announcements and if I had missed anything from the earlier recorded session.

Of course, Ancestry was selling DNA tests. At RootsTech, Ancestry announced that it now has 25 million testers in its database.

Sitting inside the booth, I saw Crista Cowan, the Barefoot Genealogist who is also Ancestry’s corporate genealogist. I noticed the cast on her wrist and felt terrible for her, trying to navigate RootsTech and minor other activities, like, say, eating and presenting and the basic activities of daily living. Been there, done that, and it’s no fun. Crista said that she had discovered that one cannot create PowerPoint slides in a cast, especially when it’s your dominant hand. And I thought I had challenges.

Like I was saying about speakers compensating and making it happen, one way or another…

I’m not going to steal Crista’s thunder about how she became “The Barefoot Genealogist,” but if you don’t know, you can watch her RootsTech presentation here.

So, what else is in Crista’s presentation? What has Ancestry announced?

  • Family Groups. Ancestry announced the ability to create a group of people in a family who are working on a common goal, facilitating collaboration.
  • The Family Groups feature will be available to all accounts, LDS, paid, free, library, whatever.
  • You will be able to assign tasks to people in the group. For example, Mom could be assigned to scan the family photos, upload them, note who they are and other relevant information
  • A “Memories” feature will support either recording or uploading audio which can tell the story of a picture.
  • A new Family Plan, currently only available in the US, allows you to pay for one subscription and add four people. I have seen pricing, but Ancestry has many different plans, and I’m unclear what is and is not included in the Family Plan. So if you’re interested, I’d suggest reaching out to Ancestry.
  • Ancestry continues to add historical records at a rapid pace.

  • Ancestry was indexing 2-3 million records per day. With the launch of the 1950 census, which utilized handwriting recognition and AI, they are now indexing millions more each month, according to Crista’s slide.
  • Ancestry is re-imaging Newspapers.com pages using the same technology, which provides much more than OCR, which is plagued by issues such as image quality and lack of intelligence.
  • One example of new features is that previously, some people were mentioned only by association, such as Mrs. John Doe. Now, Mrs. John Doe can potentially be recognized as Susan Doe or even Susan Jones Doe, based on other articles and information.
  • Ancestry has created a new Stories and Events Index, which indexes the records by category, such as marriages or law and order.
  • However, and this is important, these new re-imaged records are NOT found when you do a global search through Ancestry because, in layman’s terms, there are so many that they crash the system.
  • Ancestry added 16 billion records from newspaper collections last year. You can find a hint or go directly to the newspaper database. Check the specific collection because you may not find the information searching generally.

You can find the Historical Newspapers Collection under the Search tab.

Crista was also being plagued by technical gremlins to this point. It’s obvious that she was well-practiced too, as she barely missed a beat.

Crista encourages people to use the Card Catalog to view the new newspaper record collections.

Here’s what’s showing in my Card Catalog Records Collection view.

  • Moving to DNA announcements, Crista stated that with 25 million people in the database, Ancestry has 88 ethnicity regions and now more than 2500 DNA Communities.

  • The 88 ethnicity regions represent ancestors 500-1000 years ago, while the 2500 communities are formed by a genetic network of people related within approximately 200 years.
  • Ancestry now has 120 million family trees that are mined for location information.
  • Ancestry introduced 203 Communities in Ireland this past year. Crista mentioned that this means that those communities are as granular as counties and that now she knows where to search for her Irish ancestor. I hope she has only one Irish ancestor, and he’s close enough in time. I’m also hoping that the granularity of Communities provides very specific hints.
  • Ancestry added 413 African American Communities in the southern US and Caribbean – some to within a 10-mile radius.
  • Ancestry added 352 Mexico Communities.
  • More Communities are planned to be released every 3-4 months or so during this next year. In other words, you’ll need to check from time to time, as there won’t be a specific large update for everyone.
  • Traits and Communities, by parent, will be added within SideView

If you recall, SideView features now require either a full subscription, or a Plus subscription for DNA features. You can read about that here and here.

Pro Tools

Crista shifted gears here to discuss Pro Tools, which she described as tools that aren’t necessarily for pros, but are new ways to view family history.

Pro Tools is NOT the same as the DNA SideView features that are behind the regular Ancestry subscription or the Plus paywall.

Pro Tools was recently introduced. Crista didn’t mention this in the video, but Pro Tools costs an ADDITIONAL $10 per month, regardless of whether or not you have a full, World, or Plus subscription. In other words, you’ll pay another $120 per year to access Pro Tools

There are two schools of thought about this.

  1. Some people are furious that Ancestry added an entirely new subscription instead of adding these functions to the full or Plus subscription level.
  2. Some people are glad that Ancestry didn’t raise the cost of the full subscription by $120 per year, allowing people NOT to subscribe to these new Pro-Tools features if they don’t want them.

New features will be added under Pro Tools soon.

New shared matches view:

  • The predicted relationship and how many cMs your shared matches share with any other shared match will be available in the first half of 2024.
  • If shared matches triangulate.

Future Enhancements

  • Ability to group shared matches into custom groups with one click using “select all”
  • Ability to sort by your matches’ closest matches
  • Highlight matches that have triangulated shared segments

Nope – No Chromosome Browser

People have been speculating for some time that Ancestry might have been going to add a Chromosome Browser. Nope, they didn’t.

Crista didn’t mention this, but discussion elsewhere revealed that the triangulated segment information will NOT include:

  • The number of triangulated segments
  • The size of triangulated segments
  • Segment location information
  • A chromosome browser

At this point, I have no plan to subscribe to Pro Tools. I feel like Ancestry is essentially teasing us. “Yes, you have a triangulated segment with two other people, but, sorry, we’re not going to tell you where it is.” It’s like they get us right up to the edge of something useful, within sight and sniffing distance, then, boom, dropped like a hot potato. To add insult to injury, we have to pay separately for the teaser, even with a full subscription. The best we could do, I think, is hope that one or some of the triangulated people have a tree so we can determine who the common ancestor or ancestral line might be. If we’re really lucky, there might be a ThruLine formed.

I’ll leave it at that, but I am not one bit happy about the features that are still excluded, and that the included features require yet another subscription.

I realize that after years of saying that segment information violates Ancestry’s perception of privacy, it would be difficult for Ancestry to reverse its position at this point.

Standing in the booth later, someone commented that they were surprised that Ancestry is going to provide estimated relationships between shared matches and shared cM amounts to each other. Crista said that Ancestry had needed to “work out some privacy stuff” first.

Perhaps this is the furthest Ancestry feels that they can move without entirely reversing their long-standing chromosome browser privacy position.

For those who want to work with segment information and a chromosome browser, you can upload your Ancestry DNA file to FamilyTreeDNA, MyHeritage, and GEDmatch. You’ll find step-by-step instructions here.

After visiting the Ancestry booth, I moved on to other vendors on the show floor.

Goldie May

I hadn’t heard of Goldie May until Drew Smith introduced me recently. Thanks Drew!

You can take a look at their genealogy organizational tools, but their best feature for genealogists who give presentations is the ability to blur names in screenshots.

This feature, available under Goldie May Pro for $24 per month, senses names and blurs them along with associated profile photos for you. The lack of blurring is one reason I never do anything live or make “how-to” videos.

Right now, this feature only works for Ancestry pages, but hopefully, it will soon work for pages of other DNA vendors and DNAPainter.

DNAPainter

Speaking of DNAPainter, they are one of my favorite third-party vendors. And just in case you’re wondering, I’m not related to Jonny, and I pay full price for my subscription, just like all of you.

I mention this only because DNAPainter appears in just about every presentation I create about autosomal DNA and matches, regardless of the vendor – except Ancestry, of course.

I saw Jonny sitting at a table, showing someone how to paint their matching segments.

One person who attended the conference agreed to a 10-minute DNAPainter lesson after dinner with a friend – only 10 minutes, though, because he was tired! Although his friend was long asleep, he was still painting at 4 AM  and had surpassed the 50% mark of his painted chromosomes assigned to known ancestors. I think we have a new convert!

You can find DNAPainter instructions here.

On the corner of the table was a shared cM relationship map, one of the free tools that Jonny offers in collaboration with others in the community.

I couldn’t resist taking this picture of Jonny in his very cool striped tennis shoes that look amazingly like painted chromosomes.

I remember the first time I saw Jonny in 2018, looking very nervous at RootsTech, standing by himself in a small booth the first year he introduced DNApainter. I had never heard of DNAPainter.

In 2018, Jonny was a candidate in the new tech innovation contest, which he won. This motivated me to try DNAPainter myself, leading to another award at the beginning of 2019.

How things have changed in six years. Now, EVERYONE knows Jonny Perl. He was included in the 25-year genetic genealogy celebration as someone who has shaped the industry, and he’s no longer standing nervously alone in his booth. Also, he has way cool shoes now!!

In fact, it’s hard to find Jonny alone at any time to take a picture.

I just love success stories!

More Friends on the Show Floor

I knew Judy Russell, The Legal Genealogist, was at RootsTech and presenting, but I hadn’t actually seen her yet. By now, I’m sure almost everyone has had the opportunity to hear Judy speak, but I’ve often said that if Judy were talking about dirt, I’d attend because it would be funny, witty, and educational.

I found Judy, in her second-generation signature pink jacket, hanging out with Janine Cloud in the FamilyTreeDNA booth.

Friday was the late evening at RootsTech. People were getting tired and hungry, and most attendees had already left by 7:30 when the Expo Hall officially closed.

In the center of the hall, near the front, FamilySearch had a “garden” or “park” area with park benches and fun games like chess.

As I was walking out, I noticed Bennett Greenspan, at left, playing park chess with Katherine Borges, Director of ISOGG, the International Society of Genetic Genealogy, at right.

I had a good chuckle as I realized that assembling the DNA of our ancestors and applying it meaningfully to our genealogy is like playing chess.

Warning

We had been hoping all day that the weather forecast would change for the better.

Maybe it wouldn’t snow at all.

Maybe it wouldn’t snow much.

Uh-oh!!

It was cold, and the wind was blowing hard as we exited the Salt Palace, whipping our hair into our faces and eyes.

Everything felt ominous. Even the locals were worried.

Attendees were heading home early, and even those who had to stay and work on Saturday were trying to change their flights to Saturday afternoon in the hope that they could escape before the brunt of the storm hit.

Airlines were contacting passengers with weather advisories, saying they could change their flights without charge. They were hoping to get people out ahead of the storm.

The various weather services showed different scenarios. One reported that it would be 33 degrees and rain until just after lunch, when it would turn to snow.

Another predicted that it would be 31 and blizzard conditions with 4-6 inches of snow and whiteout conditions by noon.

What? “Hurricane-force gusts”? You’re kidding, right? But they weren’t. This was no joke.

No one knew what to expect, and local people were bidding us adieu, saying they weren’t planning to be back on Saturday.

What would we wake up to on Saturday morning? What about flights? And hotel rooms? What would we be facing?

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

If you haven’t already subscribed (it’s free,) you can receive an e-mail whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase your price but helps me keep the lights on and this informational blog free for everyone. Please click on the 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 Book

Genealogy Books

Genealogy Research

Stop Risking Your Information: Facebook Games, Public Posts, Friend Lists & Hackers

Are you unwittingly exposing yourself and risking your information on Facebook or other social media platforms?

Bad actors are becoming increasingly problematic on social media. There’s been a HUGE UPTICK recently, and we need to keep ourselves safe. Keeping yourself safe also helps keep your friends safe, and vice versa.

Please read this article and follow these steps. Share with your friends and family too.

Please don’t think you’re immune from this. You’re not. Everyone needs to do a checkup periodically.

Sometimes Facebook changes things, and hackers get more wily and cunning all the time. Bad actors are so deceptive now that you may not realize your choices and/or behavior have exposed your information.

Using lots of examples, here’s what this article will do for you:

  1. Identify and explain new threats and how they work.
  2. Show you how to modify your privacy settings to prevent unauthorized access.
  3. Determine if you’ve inadvertently let the bad guys in – and how to shut that door.
  4. Explain how to stop engaging in risky behavior that you don’t even realize is risky.

Risky behavior on social media is like the flu – people who don’t take proper precautions expose others.

You may think you’re already aware of what’s risky, and what isn’t. Hopefully, that’s true – but when the bad guys change their tactics, we all need to reevaluate accounts, settings, and behaviors.

How Does Exposure Happen

My friends, even friends who should know better, are exposing themselves on Facebook and other social media – and they don’t even realize it.

How?

Lax security settings, Facebook games, innocent-looking questions, and public posts combine to create a toxic slurry of exposure – and you have absolutely no idea that anything is going on beneath the water.

However, it’s absolutely infested with sharks!

Facebook games and questions ARE CRAFTED BY CYBERCRIMINALS.

FULL STOP!!!

You are the target, and your own emotions are the bait.

Yes, I mean you!

I’ve seen almost everyone fall victim to this in one form or another – so you’re not alone. We all learn – hopefully before we have or cause a bad experience.

Did you click on a link you shouldn’t have – before thinking? Have you ever answered any of these seemingly fun questions posted by someone you don’t personally know? Or, someone you DO know whose posting was public? Do you even know if the posting was public?

Here are some examples of bait questions?

  • How far away do you live from where you were born?
  • Name a song that takes you back to high school?
  • Where was your first job?
  • Your cowboy (rock star, stripper, animal, you get the idea) name is your middle name. (Then they show you a fun picture.)
  • Your first car.
  • Thirty random things about me.

If you enter any of that information, you’re doing multiple EXTREMELY RISKY and DANGEROUS THINGS!!!

  • Giving potential answers to security questions to cybercriminals who aggregate your data from many seemingly innocent questions.
  • Posting the results of those ” fun ” picture games gives cybercriminals access to your personal information, friends, and timeline.
  • Giving cybercriminals access to your friend list so they can be targeted too
  • Serving as bait for your friends who see your answers because Facebook shows you what your friends and family members answer.
  • Serving as bait for your friends who see your AI name or cowboy name or whatever “game” you’ve played. Facebook shows people that you’ve played this game, which serves as an endorsement, especially if people trust you.

Best case, you’re attracting attention to yourself as someone who is naïve and vulnerable. These bad actors are manipulating your emotions, which in turn leads to you oversharing.

You may be hacked, your account cloned, or even lost entirely, AND you’ll be responsible for your friends also engaging in risky behavior.

An even worse case scenario is identity theft.

Here’s the best article I know of that shows several examples. IF YOU DO NOTHING ELSE TODAY, READ THIS ARTICLE, PLEASE!!!

I can hear my mother saying to me, “If everyone else jumped off the bridge, would you too?”

This is the bridge, and I’ll show you why.

That Alluringly Dangerous Bridge

Let’s look at a couple of examples. Different scams work in different ways depending on the goal of the bad actor. We will look at a few so you’re aware.

First, they catch your attention and hope you click before you think.

DO NOT CLICK.

First, lots of professional criminals troll ANY PUBLIC ANSWER.

This post and all replies are public. That little globe means the world can see the post and any comments.

Second, if you click to take this seemingly fun test, you give them lots of information about you, and the results, which are always “wonderful”, post to your feed – which provides “positive feedback” to you and lures your friends. Let’s face it; they will never tell someone they are “below average” because who would play their data-gathering game?

How do they post results to your feed? You give them permission when you click to do the “test,” even though you don’t realize you did that.

Here’s another one.

This has nothing to do with AI. It’s all hooey! Don’t be a willing victim.

NameTests

One of the most popular “games” on Facebook is some derivative of Nametests.

Seriously, do you believe some application can tell you anything useful by selecting three colors? And, ask yourself why anyone would create these “games” and purchase Sponsored Facebook ads to do something “free” for everyone. There is no such thing as a free lunch.

If you’re thinking this is just harmless fun – it’s not.

Do yourself a favor.

Type this into Google: “What is nametests on Facebook?”

Read this article, courtesy of Comparitech, an identity theft prevention company to see what you just gave away. Literally, access to everything in your profile. And you did it willingly. They didn’t have to hack your account. They simply tricked you by luring you with something free that looked like fun.

Ok, now that you’ve done it, Nametests and other similar apps have access to your account, so you need to rescind that permission.

You Just Gave Them Access to Your Friends List

I’ll step you through how to remove anything like this at the end of this article. You’ll also want to change your password and possibly enable two-factor authentication (2FA). You’ve just given some scammer the keys to your kingdom – plus your friends’ too.

That’s not the end, either. In fact, it’s just the beginning.

There’s more.

Questions, Challenges, Feel-Good and Outrage Stories

Emotions are powerful. They cause you to want to comment – or click. You throw caution to the wind. Actually, you simply forget about caution altogether. That’s the goal.

What you need to do is put the brakes on and…

STOP!

Some fishing questions may make you want to reminisce and relive the good old days.

Some look like fun. But ask yourself – why does ANYONE care about that?

Some scare you and trick you into clicking before thinking. They create a sense of either tragedy or urgency.

“Look who died.” “I can’t believe he’s gone.” And before you think, you’ve reacted with “OMG” and clicked and literally given away the farm. Not just your Facebook farm, either. Here’s how this works, with a short video from the Indiana State Attorney General.

What does the Attorney General say? “I don’t click on anything.” Me either! If you see these frightening tagged links from a friend, it means that friend’s account has been hacked or cloned. Contact them but do not message or reply to the account that sent this because you’ll be talking directly to the hacker.

Nostalgic or Emotionally Motivational Postings

Some scams are wonderful stories that make you want to share something affirming.

Some make you nostalgic.

Some make you angry or sad.

Have you seen those found dog scams where the individual claims to have found an injured dog, taken it to the vet, are trying to find the owner and need assistance with the vet bills. There’s an entire Facebook group devoted to identifying fake “found dog” posts, here.

These posts are meant to evoke strong emotions that cause you to forget about safety and just react. It’s called motivation, and these criminals are pros.

Then, because you’re a good person, you share with your friends, or maybe they shared with you so that’s even more encouragement to engage.

Sometimes, the posts don’t even ask you anything directly.

This next post had been up for less than one day, and look how many shares and comments it had.

A couple of weeks later, it had more than 4000 likes, 884 comments, and 559 shares. Just think how many comments it actually has now, scattered around the internet on various people’s pages.

It looks so innocuous and safe, but it isn’t.

You’ve just given these people, whoever they are, an approximate age, and you’ve told them you’re vulnerable to this type of trickery. Hackers gather every tidbit they can about you so that you can be targeted on this and other platforms.

Everything on this account is public, which you can tell by the little globe, meaning everyone anywhere can see what you say and what everyone says.

The recent 23andMe data exposure is a good example of how information can be aggregated and used to breach other accounts. Furthermore, with your age and city location, which may well be available on your Facebook profile page, anyone can use standard internet search tools to find an address, a phone, family members’ names, and more. Much more!

Questions Lists

You may see these question lists posted by your friends and asked to be passed on “for fun.”

Just don’t!!! Remember, your friends and (sometimes) their friends can see responses too. You have NO IDEA who is consuming this information.

Many police organizations have warned against this. Here’s an article.

Anytime you see anything that sounds or smells like these types of posts, OR posts that are public, the first thing that should pop into your mind is STOP – in a bright red neon danger sign.

Yes, I’ve used this exact same image three times now, because you need to remember to STOP. Stop and think before doing anything.

I WANT YOU TO THINK ABOUT THIS IMAGE EVERY SINGLE TIME YOU SEE THINGS LIKE THIS ON FACEBOOK!

How does this toxic material spread like wildfire anyway?

Public Posts Paint a Target on You

The most common danger is fully public posts. Hackers take advantage of public posts when unwary people post or reply publicly.

Public posts, identified by the little globe, open the post up for the entire world to see.

It also opens you up to friend requests and comments from anyone, anyplace.

Scammers troll for anything public and scrape the contents into huge databases organized by name. They know that if you’re naive enough to fall for one scam, you might well be naive enough to fall for another. They’re hoping, anyway.

Not all public posts are scams, but replying to public posts makes you a target.

Here’s an example.

My friend, Sam, reposted this link on his page to be helpful and made it public, meaning everyone can see it from any place. Sam has his security set to “require one friend in common” before you can send them a friend request. Clearly, “Shirley” doesn’t have a friend in common with Sam, so “Shirley” can’t send Sam a friend request. So “Shirley” replied with something “nice,” hoping to entice Sam into sending “Shirley” a friend request so they can gain access to Sam’s account info and friend list.

“Shirley,” who is scantily clad, isn’t “Shirley” at all, but someone trying to gain access to as many people and profiles as possible to scam people.

Comments on Public Posts

I have adopted the policy that I DO NOT, EVER comment on or reply to public posts – even if they’re posted by my friends. Here’s why.

One of my friends has a wonderful history page where he makes several public postings daily. Unfailingly, every single person who replies to his post has one of two things happen:

  • If the people who reply or comment (Linda and Douglas here) accept friend requests without a common friend, or if they have a common friend, they get friend requests from scammers (Holman and Amanda here).

If you automatically think you’re safe to accept a friend request if the requester shares a friend with you – think again. Maybe your friend has fallen victim and doesn’t realize it. It can happen to anyone.

  • If the commenter does not accept friend requests unless the requester (scammer) and commenter (i.e., the target) have a common friend, then scammers replies to their posting with a compliment and invitation to friend them.

DO NOT REPLY or add them as a friend, and DO BLOCK these people immediately.

Here are some clues to spot fake accounts:

  • Extremely attractive or enticing photos
  • Single or divorced
  • Professional, military or wealthy-looking if male
  • Sexualized or seductive if female
  • No friends or scads of friends
  • Non-substantive public posts
  • New account
  • Pictures with puppies or animals
  • Things to instill confidence – like references to God

Hackers are so “Helpful”

My friend, Pam, had her Instagram Account “hacked” and announced that to the world in a public post on Facebook. She meant to warn her friends, of course.

Truth be told, Pam had not actually been hacked, as her password would (probably) have been changed if she were truly hacked. This recently happened to another friend and he lost his entire Facebook account, including all photos accumulated over more than a dozen years.

Pam’s password was not changed, because she could sign into her account. Her account was actually cloned, meaning a second account was set up using her profile information that looked exactly like her original profile. Then her friends were messaged from the cloned account with links to click that led to malware. Her friends also received friend requests from the cloned “fake Pam” cloned account.

Unfortunately, cloning is very easy to do. Facebook photos are, by default, public. So the bad actor takes your photo, sets up a second account that “looks like you” and then sends your friends friend requests and malicious links. Your friends accept your friend request, not realizing it’s a fraud.

I wonder how a scammer might have obtained access to Pam’s friends’ profile information to determine whom to target.

Any ideas, anyone?

Let’s see:

  • Maybe public posts.
  • Maybe games
  • Maybe answering “questions”
  • Maybe Pam’s friend doing one of those things and exposing Pam’s information, too
  • Maybe accepting a friend request she shouldn’t have
  • Maybe making “too much” public, including her friends list

Let’s see what happened when Pam publicly informed the world that her Instagram account had been hacked! Just in case you think this might be no big deal.

ALL 64 REPLIES WERE FROM HACKERS!

In fact, it’s possible that the original hacker is one of those who responded, offering to “help.”

Here’s the list of all 64 comments, with my commentary in red. Notice that all 64 arrived within two hours. Many of these profiles may, in fact, be the same bad actor.

She went to work and didn’t notice any of this. However, everyone else in the world had the opportunity to reply to one of these hackers, seeking “help,” and her friends might have been lured.

If you comment, you’re at risk too.

Then, someone with a name that includes the word Cyberspy messaged my friend directly.

Oh yeah, this instills confidence, alright.

Unknown people may directly message (DM) you.

Do not reply.

BLOCK THEM ALL!!!

If someone you know messages you with a link, DO NOT CLICK ON IT. Verify another way that they actually sent you something – meaning that their account has not been cloned or hacked. Regardless, I still don’t click on unsolicited links.

Reporting to Facebook

If you know that your friend’s account has been cloned, report to Facebook by clicking on the little three dots on the cloned profile, then “Find support or report.”

Unfortunately, there’s little to be done about the hacker/scammer replies and postings. Reporting any of these fraudulent accounts to Facebook (Meta) is worse than useless – and Facebook is the only one who can take care of it. I have yet to see them take any of these accounts down.

Block all scammers or shady postings or replies.

Your best bet is to NOT fall for any of this.

Bait

This is supposedly a food page, but if you look at the postings, they are all “bait” of one sort or another.

That bait is for you – you’re what they are hoping to snag.

First of all, this post has nothing to do with food. Several posts are of the “who remembers this” type of nostalgia bait, which is particularly attractive to older people who may be less tech-savvy.

Second, they try to make you feel guilty if you’re a grandparent and DON’T “let the world know.”

Third, they are clearly targeting older people, and if you share or post on this, you’ve given them information. Some people actually said how many grandchildren they have and where they live.

Sometimes, older people are more susceptible to scams because they are more trusting.

Stop and Think!

  • Why would anyone you don’t know be interested in this information about you?
  • Why would you willingly give something this information?

Anyone hear of grandparent call scams? “I’m in trouble. Send money.” Some even go so far as to say they’ve been kidnapped. Here’s what the FCC says about “grandparent scams.”

Scammers who gain access to consumers’ personal information – by mining social media or purchasing data from cyber thieves – can create storylines to prey on the fears of grandparents.

Often the imposter claims to have been in an accident or arrested. The scammer may ask the grandparent “please don’t let mom and dad know,” and may hand the phone over to someone posing as a lawyer seeking immediate payment.

Unfortunately, according to a recent Washington Post article, bad actors can now use artificial intelligence technology “to mimic voices, convincing people, often the elderly, that their loved ones are in distress”.

The article reports that scammers can replicate a voice from just a short audio sample and then use AI tools to hold a conversation in that voice, which “speaks” whatever the imposter types.

I know someone who was targeted this way. They said they could barely understand their granddaughter because she was both crying uncontrollably and hysterical. My friend could make out the word rape. It was terrifying and paralyzing at the same time. Fortunately, her granddaughter happened to walk into the front door as this call was taking place.

What Have You Done?

Are you wondering if you have inadvertently given access to your Facebook page to scammers without realizing it?

You need to check.

Here’s how, step-by-step!

Start by clicking your profile picture, then Settings and Privacy, then Settings, then Apps and Websites – as outlined above and detailed below.

On the left, you’ll see this menu. Scroll towards the bottom.

You can click any image to enlarge.

You’ll see this information at the top, with the following apps that you’ve given access to below.

Click on “remove” to remove unwanted apps. I clicked on “Remove” for Yelp, which displayed additional information. You can remove future access, but you can’t remove any information already shared with the other application.

When you look at an app and see the ability to log in through Facebook, this is actually what you’re doing – sharing a variety of information with that application.

Under “Preferences,” disable the ability to use Facebook to log into third-party apps.

What does signing in through Facebook or Google do? How does it work?

What actually happens when you sign in using Google or Facebook? It’s convenient, but you’re giving away data about yourself that you’re unaware of.

Here’s what LifeLock has to say.

Here’s a list of Facebook privacy settings that you should change now.

Whatever you did in the past can’t be undone, but you can remove the access and prevent anything in the future.

Stop the Thieves – Lock It Down

If you’ve done something risky, you’ll need to take additional precautions.

  • Change your password. Don’t reuse passwords.
  • If your account has been cloned, change your profile photo so your friends know which account is actually yours.
  • Restrict postings to friends only.
  • Check for and disable any applications, including games like Nametest.
  • Consider implementing 2FA. It’s under “How to keep your account secure” in the Privacy Checkup.

What are your settings?

Let’s check and see.

Privacy Checkup

Facebook makes it easy to do a Privacy Checkup.

Just click on your profile photo, then “Settings and Privacy” and “Privacy Checkup.”

I recommend stepping through every one of these topics and adjusting your permissions.

I recommend locking everything down on your profile.

Begin with “Who can see what you share”.

Scroll to the bottom, where you see “Friends and following.”

CRITICAL

To protect your friends list, and disable anyone else from seeing it, select ONLY ME.

Your next selection under “Who can see what you share” selects the default audience for your Facebook posts, Stories, and limits who can see past posts. This is a critical selection because it determines who can view your posts unless you change this setting on individual posts.

Step through each of the “Privacy Checkup” tabs and do the same for People, Pages and Lists you follow.

Next, check “Profile and Tagging” under the Settings and Privacy Menu on the left-hand side.

Step through each of these sections, especially Posts and Stories, and adjust your privacy.

It’s VERY important to prevent others from viewing your friends list which you’ll find under “Profile and Tagging.”

Some people don’t let anyone post on their profile. I currently do let my friends post, or tag me, but I’m also torn about this setting.

Next, select who can see what others post on your profile?

Make sure to check the rest of the information and if it’s displayed.

I don’t provide any information, such as where I live or went to college – nor do I display my phone number. I get enough spam calls the way it is!

See What They See

Check to be sure your account displays only as much as you want.

On the dropdown menu from your profile picture, go to the Privacy Center and Click on “Manage Your Accounts,” then select “How to clean up your profile.”

Click on “View as” to see your account as someone who is not your friend. Ensure everything is locked down, and you’re not providing information to unknown people.

Best Practices for Safety

Two types of actions are necessary to keep your Facebook account and your friends safe. Both are important – some are account settings, and others are behavioral.

Think of this like driving a car. You need safety equipment like brakes – but you must also know when, where, and how to apply them to keep from crashing.

One alone is insufficient. You need both. You also need to stop and think.

  • Lock your account down so that people you don’t know can’t see your information.
  • Lock it down so that others can’t see your friend list, so you’re not inadvertently making your friends targets.
  • Do not accept friend requests from people you don’t know.
  • View everything skeptically.
  • STOP every single time you even think about replying to something. Stop, then think. Is the post public? Who wants to know this information, and why would I give it to them?
  • If it’s public, DON’T REPLY.

Selecting Privacy for Your Posts

You select a default privacy setting for your own posts. You can also override the default and select a different privacy setting for each post if it differs from your default.

Default settings are found in the “Privacy Checkup,” under “Who can see what you share.”

You can change the privacy selection on each post as you create them. You can also change them later.

Facebook used to retain your selection for the next post, but I don’t think they do that anymore. For example, if I lost my mind for some reason and selected “public,” for this post, the default would have been “public” for subsequent posts too.

I tested this, and it appears that’s no longer the case today. That’s a good thing! You can change any individual post, but your selected default remains in effect.

It’s Time for Spring Cleaning

If your friends have their friend list exposed, they are exposing you to hackers who may want to target you. If your friend’s account is cloned, this is exactly how bad actors know to target you next.

It’s time for spring cleaning on your friend list. Let’s take stock and evaluate.

  • Are they your actual friend?
  • Why are they on your friend list?
  • If you’re undecided, check to see if their friend list is exposed. That’s the tie-breaker. If it is, they are exposing you.
  • If someone you know and care about is exposing their friend list, please send them a link to this article.

Let’s Practice

You notice a question on your friend’s feed about the name of your first-grade teacher.

You smile with warm remembrance.

What’s the first thing you’re going to do?

STOP!

THINK!

Public – Look to see if your friend’s posting is public.

If the answer is yes, STOP.

If you answer, you just gave someone information about you that can be combined and aggregated with other information from all of those types of questions you’ve inadvertently answered. Many are security questions and can lead to identity theft.

Games – Next, look to see if it’s one of those games.

If the answer is yes, STOP.

Groups – Next, check to see if the posting is from within a group that you’ve joined. If the the posting is within a restricted group or a non-public Facebook page or group, that may be a more controlled environment, depending on the join criteria and how closely the group is monitored by administrators. I do participate in several closed groups.

Non-public groups are designated by an icon of three people.

Friends Only – If the posting is “friends” only, the two-person icon, the threat is reduced, unless, of course, your friend has inadvertently given access to one of those scam games and, in doing so, has granted access to their entire profile. There’s no way to know. I evaluate the friend and the topic at hand when deciding to reply.

My “go to” response now, on social media, is simply “don’t reply,” unless someone has asked me a direct, non-public, question that makes sense and doesn’t relay any information that even might be useful.

So, if your friend who visited last week asks for a pudding recipe that you made for dessert, and the posting isn’t public, that’s probably just fine.

If your cousin can’t remember your daughter’s middle name and wants it for genealogy, I’m sure that’s fine to answer too, just not in any kind of a public forum. To some degree, Facebook is always public. It’s social media, after all. Message, email or call your cousin with the answer. Don’t post it.

Vigilance as a Way of Life

I know you’re going to hate me for a bit when you see that red STOP as you scroll through your Facebook feed. Right about now, you’re saying, “Roberta, please stop!”

That’s OK. Getting you to see and do that is my entire reason for writing this article. I want it to pop into your mind! I’d rather you be irritated with me than have your account compromised or lost entirely and expose your loved ones in the process. 😊

We must be ever more vigilant as scams and scammers become increasingly sophisticated. Your “scam antennae” should always be up and on high alert.

And yes, I know some of you will tell me that you don’t want to live like that. I understand. Neither do I, but if you want to stay safe – and for your friends and family to remain safe, too – you must be ever-vigilant, alert, and chronically suspicious.

If you see family members acting unsafely on social media, they probably aren’t aware, so please feel free to share this article.

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

If you haven’t already subscribed (it’s free,) you can receive an email whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase your price but helps me keep the lights on and this informational blog free for everyone. Please click on the 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 Book

Genealogy Books

Genealogy Research

Bennett Greenspan: Meet My Extended Family & Discover Extraordinary Deep Heritage

“My ancestors are in my soul. I can’t get them out of my mind.”

Bennett Greenspan

“And yes, I brake for cemeteries.”

Bennett Greenspan gave an incredibly interesting presentation at the 15th International Genetic Genealogy Conference held by FamilyTreeDNA in November 2023. Since his retirement in January 2021, he has been able to focus on his genealogy. Once a genealogist, always a genealogist.

Bennett said some things I hadn’t thought about, and now I’m viewing Y-DNA matches with a different perspective – based on how he’s using his results.

Ever since I met him, Bennett’s focus has been to use genetics to unravel his complex Jewish heritage.

The questions that drive Bennett are the same ones that motivate most genealogists:

  1. Who are we?
  2. Where did we come from?
  3. Where were we before we were there?
  4. How did my ancestors get there?

Bennett “lost his family lines” before the mid-1800s due to his Jewish heritage, exacerbated in the 1930s by the devastation wrought by the Holocaust. Families were either killed or scattered to survive. It has been through Y-DNA in particular that he has been able to establish unquestionable and confirmed connections with other Greenspan men, sometimes by similar but different surnames, like Green, and sometimes with other surnames entirely.

When Bennett first started down this path, he tested more than 62 men before actually finding one a decade later that matched his Y-DNA. Bennet commented that it was “a little frustrating.”

Persistence is the key, and sometimes, genealogy is a waiting game, but that’s small comfort to genealogists during that unproductive waiting period.

Eventually, Bennett reassembled his family, at least somewhat, but it was a long journey. Here’s Bennett’s incredible story, including surprises, as he tells it.

Bennett discovered genealogy at age 12 and, like many genealogists, created a pedigree chart by talking to his family.

I love the mark-outs. How many of us still have our first chart with its edits?

This is the young Bennett Greenspan, whose interest in genealogy would one day unlock secrets for all of us!

It was a long way from a decade with no matches to finding his genetic kin in Ukraine.

The Big Y-700 Time Tree shows Bennett’s lineage in Ukraine, but stepping back in time, some descendants of his ancestors are found in adjacent locations.

Bennett was passionately discussing his matches on the time tree and in the Greenspan project, so I visited the Greenspan DNA Project, where the earliest known ancestors of Bennett’s Big Y matches are shown on the Group Time Tree.

Bennett’s closest matches are shown as descendants of haplogroup J-ZS1718. He has additional matches who are not in the Greenspan project. Since this is the Group Time Tree, it only displays the people in that project, along with their earliest known ancestors, Isaac and Usher Greenspan.

12-Marker Matches

Bennett never fails to amaze me. He said something very important and profound about 12-marker matches that I really hadn’t thought about – at least not this way.

As a community, we are often guilty of discounting 12-marker matches, those that don’t match us at 25-markers or above, or with different surnames, as “too far back in time” or otherwise irrelevant. I always look at the names and earliest known ancestors of 12-marker matches, because that person may have tested back in the day when fewer markers were available. But if I don’t recognize something, I move on.

However, Bennett said that, ”Y-12 matches reach back to a common ancestor. 12-marker matches are not a quirk. They are related to you, just further back in time. You share a common ancestor with them, someplace. They may be more distant, but they are still your close matches.”

I’ve been in too much of a hurry for a quick win, and ignoring the (apparently not so) obvious.

Determining when and where their ancestors lived also paves the way to discover yours. Your Y-DNA and theirs were in the same place at the same time.

Of Bennett’s 171 12-marker matches, 107 have upgraded to the Big Y, probably mostly due to his encouragement. This benefits both them and Bennett by fleshing out the history of that entire group of men, including how they got to where they are found in the first available records. The Time Tree shows when Big Y testers shared a common ancestor, and based on Earliest Known Ancestor (EKA) locations, where. This provides further information about the lives of ancestors before contemporary records – in other words – people that we can never identify by name. It’s a window into ancestors before surnames.

Bennett notes that testers need to know their ancestral village or location to be most useful within the project, and of course, they need to enter their EKA information. Location information is how the Migration Map, Matches Map, and Discover tools, including the Time Tree, are built.

What Happened in Spain?

Bennett’s ancestors and those of his 12-marker matches are found in Spain, and as Bennett says, “One son stayed and one left about the year 296.”

While we have no idea of their names, based on the Time Tree combined with the cluster of earliest known ancestors, we know that they were in Spain, and when.

Their family story is revealed in the bifurcation of the tree found beneath haplogroup J-L823, formed about 296 CE. One line stayed in Spain, and Bennett’s line migrated to eastern Europe where that man’s descendants, including Bennett’s family, are found in the Russian Federation, Belarus, Poland, Lithuania, Sweden, Slovakia, Ukraine, Germany, Romania, the Czech Republic, and other eastern European locations. The closer to you in the tree and in time, the more relevant to your more recent ancestral story.

However, Bennett’s deeper ancestry, the migration of his ancestors to Spain, was only revealed by testing those more distantly related men. Those same men could well have been ignored entirely because they only matched at 12 markers.

According to Bennett, “Y-12 markers are important because these are the men most closely related to you in a database of 1 million men.”

How incredibly profound. How much have I been cavalierly overlooking?

How does this actually apply to Bennett’s results?

Bennett’s Spanish Matches

Bennett has the following STR panel matches who indicate that their EKA are from Spain. You can see that they match Bennett on a variety of panels.

  • X = yes, match
  • No = no match
  • Blank = not tested at that level.

In the Big Y GD column, the genetic distance (GD) is displayed as 15/660 where 15 is the number of mismatches, or the cumulative genetic distance ABOVE the 111 panel, and 660 is the number of STR markers above 111 with results.

The Big Y-500 test guaranteed a minimum of 500 total STR markers, and the Big Y-700 guarantees a minimum of 700 total STR markers, plus multiple scans of the balance of the Y chromosome for SNP mutations that define haplogroups. Testers don’t receive the same number of markers because the scan technology sometimes doesn’t read a specific location.

Tester 12 25 37 67 111 Big Y Test Big Y GD Big Y Match Haplogroup
AA X X X No No Yes 15/660 No J-FTD8826
DT X X No No X Yes 17/664 No J-FTE50318
JG X X No No
AR No No X X No No
ELR X X X No No
EL X X Yes 17/666 No J-FTE50318
GC X X X X No No
JC X No No
JLG X X No No No Yes 14/662 No J-FTE23540
MF X X No X No Yes 15/665 No J-FTD91126
MT X X X X No No
BE X X X X X Yes 20/664 No J-BY1795
DR X X X X X Yes 16/660 No J-FTC87344
EC X X X X X Yes 15/665 No J-FTC87344
GM X X No No No Yes 16/650 No J-FTD28153
GM X X X X No Yes 17/664 No J-FTD11019
LS X X No No No Yes 18/666 No J-FTD28153
NE X X X X X Yes 23/597 No J-BY1795
NC X No No
RR X X X No X Yes 22/659 No J-BY1795
TT X X X X X Yes 16/647 No J-FTC87344
XG X X X No No Yes 17/523 No J-BY167283
JA X X No No No Yes 15/646 No J-FTD11019

Of those 23 Spanish matches, sixteen have upgraded to Big Y tests, 14 of which are Big Y-700s, resulting in nine different haplogroups, all of which are descendants of Haplogroup J-L823. How cool is that?

The “Nos” in the Big Y Match Column aren’t mistakes. That’s right – none of these men match Bennett on the Big Y test, meaning they had more than a 30 mutation difference between them and Bennett on the Big Y test.

At first glance, you’d think that Bennett would have been disappointed, but that’s not the case at all! In fact, it was the information provided by these distant Spanish matches that provided Bennett with the information that his line had split sometime around the year 296 CE, with one branch remaining in Spain and his branch migrating to Eastern Europe, where he has lots of matches.

DNA Plus History

What was happening in Spain or the Iberian peninsula that involved the Jewish people about that time? Historical records exist of Jews living in that region before the fall of the Second Temple in about 70 CE, including records of Jews being expelled from Rome in 139 for their “corrupting influence.”

Furthermore, the Ancient DNA Connections for haplogroup J-L823, the most recent common ancestor (MRCA) for all of those branches, includes connections to multiple burials from:

  • Lebanon
  • Iran
  • Rome (from 1-400 CE)
  • Turkey
  • Jordan

Clearly, Bennett’s ancestor was in the Iberian peninsula around or before 296 CE. One branch stayed, winding up in Spain, and one headed for Europe.

Without these matches, some who didn’t match above the 12 or 25 marker level, how would Bennett have EVER known that his Jewish ancestors left the Middle East for Spain in the early years? How would he have known they migrated from Spain to Eastern Europe, and how would he have known that his line did not migrate directly from the Levant to Eastern Europe in the 9th century?

Big Y matches are typically within about 1500 years, but non-matches are still INCREDIBLY valuable. Without them, you can’t completely assemble your family story.

I noticed on the Time Tree that in Bennett’s Eastern European line, one of his ancestor’s brother lineages includes the Katzenellenbogen Rabbinic Lineage derived from ancient DNA samples.

Bennett’s successes have resulted from contacting his matches and encouraging upgrades. So how did he do it? What’s the magic sauce?

Contacting Matches

How to contact matches successfully is a question I see often. In fact, FamilyTreeDNA recently wrote about that in an article, here.

Bennett’s methodology for contacting his matches to encourage an upgrade is that he sends an email explaining why he’s encouraging them to upgrade, followed by a 2nd email three days later.

Bennett tells the recipient that we are at an inflection point in time. “It’s winter, the wind is blowing hard, and many of the leaves are gone.”

In other words, we need to cast the net wider and capture what we can, while we can. Unfortunately, many early testers have died, and with them, chapters of history are perishing.

Collaboration is key. In addition to encouraging upgrades, Bennett also offers Zoom calls to these groups of men to explain the results if they are interested.

What a GREAT idea! I need to begin offering that as well.

Upgrade Request

Bennett reaches out to his matches at various levels, but he expects his closer STR matches, meaning at the 67 and 111 marker level with the fewest mismatches, to match him on a Big Y-700 test and connect someplace between 300-600 years ago, which helps everyone flesh out their tree.

Bennett’s email:

Hello <name>,

Since you have already made a sizable investment in your Y-DNA, you now know that we come from the dominant male Middle Eastern group (Haplogroup J) of men who <subject here>.

What’s really neat is that our Y-DNA has recently been found in an archaeological site in Northwestern Jordan dated to about 4200 years ago. I know this because I upgraded to the Big Y, which tests SNPs, looking at several million locations on the Y chromosome of each man.

One academic customer recently compared this new technology as the difference between looking into space with binoculars versus the Hubble Telescope.

I don’t know if you are familiar with your list of matches at the highest level you’ve tested for, either Y-67 or Y-111. If you are, you should recognize my name and the names of others who have taken the Big Y test.

You’ll see what you’ll gain by letting me upgrade your test for you and determining whether you are related to my line – probably between about 200 years and 500 years.

This might be the second time that I have written to you on this matter; can I presume if I don’t hear from you that you’re not really interested in the Y-DNA subject anymore?

Can I run the test so that I can see how closely we are related – at my expense? (Of course, you get to see how closely related we are, too).

Please reply to me and say “yes.” You don’t even have to put a 🙂 if you don’t want to.

I started this company and this industry over 20 years ago. I predict that you will be happy with the history of YOU that this upgrade will uncover.

Best,

Bennett Greenspan

As you can see, this email can easily be personalized further and adapted to matches at the 37, 25, and 12 marker levels – or even Family Finder matches, now that intermediate-range haplogroups are being reported.

What’s Next?

I’m going back to every one of the kits I sponsored or that represent descendants of one of my ancestors to review their matches again – focusing not just on the closest matches with common surnames, but also on locations – and specifically at lower matching levels. I’ll also be checking their Family Finder matches for male surname matches, or similar surnames.

As is evident from Bennett’s tests, an entire mine of diamonds is out there, just waiting to be unearthed by a Big Y test.

And to think that some people have been advising people to ignore 12-marker matches out-of-hand because they are “entirely irrelevant.” They aren’t – for two reasons.

  1. First, some early testers only tested to that level
  2. Second, because of the deeper history that Big Y tests from those matches will uncover

You can view your Y-DNA matches, upgrade your own Y-DNA test, or order a Big Y-700 test if you haven’t yet tested by clicking here. What’s your next step?

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

If you haven’t already subscribed (it’s free,) you can receive an email whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase your price but helps me keep the lights on and this informational blog free for everyone. Please click on the 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 Book

Genealogy Books

Genealogy Research

What Subjects Should We Explore in 2024?

DNA testing is all about solving genealogy puzzles!

After we test, we need to fully understand what those test results are telling us.

To help, I need to know about your genealogy dreams! Who are you dreaming of finding, and what tools do you need to understand better to achieve that goal?

I have some articles planned for 2024, but I’d like to know what topics you’d like to see covered.

Of course, I always cover “breaking news” in genetic genealogy. I’ll be covering RootsTech as well.

Here are a few articles that I have in the works for 2024.

  • DNA and Pedigree Collapse
  • Big Y March of the Ages, by Dr. Paul Maier from the FamilyTreeDNA Conference
  • Highlights from Ancient Connections, by Dr. Miguel Vilar from the FamilyTreeDNA Conference
  • Meet My Extended Family – Leveraging Y DNA Testing, by Bennett Greenspan from the FamilyTreeDNA Conference

Focus

To help focus my efforts, I made a list of my own “genealogy dreams” by reviewing each ancestor and asking myself what I need to know about their life. For example, do I have the Y-DNA and mitochondrial DNA haplogroups for each line? How can I figure out who their parents are? Do I have representatives of this line in every database? How can I address each of these things?

I’ve already started my 2024 research from a focus list I created. So far, I’ve:

  • Upgraded two cousins who took a Y-DNA test to the Family Finder, so I can use those two tests together. I need to know how closely related those two men might be, and who they match in common.
  • Upgraded a cousin to the Big Y-700 from a Y-67, hoping to discover when two lines from our common, unknown ancestor, split. That may help me know where to look, and when.
  • Encouraged a 95-year-old cousin to upload their Ancestry DNA test to FamilyTreeDNA and join the appropriate surname project. They did! Now we can compare their results within a project, which may very well solve a long-standing mystery of an unknown father all the way back in 1809! Fingers crossed!
  • Asked several cousins to also upload their DNA files to both FamilyTreeDNA and MyHeritage. You’ll find free step-by-step instructions for how to do that, here.

It’s Your Turn

What mysteries are you focused on solving using DNA? Who are you searching for in your tree?

Please note that already published articles are available by using the search function on the main DNAexplain blog page, here. Those articles may prove quite helpful.

What topics would you like to see covered in 2024 that will assist with your journey?

Here’s to a wonderful 2024 and finding lots of ancestors!

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

If you haven’t already subscribed (it’s free,) you can receive an email whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase your price but helps me keep the lights on and this informational blog free for everyone. Please click on the 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 Book

Genealogy Books

Genealogy Research

FamilyTreeDNA 2023 Update – Past, Present and Future

At the FamilyTreeDNA International Conference on Genetic Genealogy, held November 3-5 in Houston for group project administrators, product and feature updates were scattered across both days in various presentations.

I’ve combined the updates from FamilyTreeDNA into one article.

I’ve already written two articles that pertain to the conference.

FamilyTreeDNA has already begun rolling the new Y DNA haplogroups from Family Finder autosomal tests, which I wrote about here:

I still have at least two more articles to publish from this conference that was chocked full of wonderful information from a wide range of talented speakers.

Past, Present, and Future with Katy Rowe-Schurwanz

Katy Rowe-Schurwanz, FamilyTreeDNA’s Product Manager, provided an update on what has been accomplished in the four and a half years since the last conference, what’s underway now, and her wish list for 2024.

Please note the word “wish list.” Wish list items are NOT commitments.

Recent Milestones

A lot has been happening at FamilyTreeDNA since the last conference.

Acquisition and Wellness Bundles

As everyone is aware, at the end of 2020, myDNA acquired Gene by Gene, the parent company of FamilyTreeDNA, which included the lab. As a result, the FamilyTreeDNA product menu has expanded, and wellness bundles are now available for FamilyTreeDNA customers.

If you’re interested, you can order the Wellness product in a bundle with a Family Finder test, here.

You can add the Wellness product for $39 if you’ve already tested.

New TIP (Time Prediction) STR Report

Did you notice that the old TIP report for Y DNA STR markers was replaced with an updated version several months ago?

To view the new report, sign on and select your Y DNA matches. At the far right of each match you’ll see these three icons representing a pedigree chart, notes, and the TIP (Time Predictor) report.

The updated TIP report includes wonderful new graphs and age estimates for each match category, which you can read about, here. Each category, such as 67-marker matches, has time estimates in which a common ancestor might have lived at each possible genetic distance.

Math is our friend, and thankfully, someone else has done it for us!

Please note that the Big Y SNP dates are MUCH more accurate for a variety of reasons, not limited to the instability and rapid mutation rate of STR mutations.

MyOrigins3

MyOrigins3, FamilyTreeDNA’s ethnicity offering, added over 60 new reference populations for a total of 90, plus chromosome painting. You can read about MyOrigins features here, and the white paper, here.

This is one of my favorite improvements because it allows me to identify the segment location of my population ancestries, which in turn allows me to identify people who share my minority segments such as Native American and African.

Due to a lack of records, these relationships are often exceedingly difficult to identify, and MyOrigins3 helps immensely.

Additional Releases

Additional products and features released since the last conference include:

Discover

Released in July 2022, Discover is the amazing new free product that details your ancestor’s Y DNA “story” and his walk through time and across the globe.

In the past 18 months, all of the Discover features are new, so I’m only making a brief list here. The great thing is that everyone can use Discover if you know or can discover (pardon the pun) the haplogroup of your ancestral lines. Surname projects are often beneficial for finding your lineages.

  • Haplogroup Story includes haplogroup location, ages derived from the earliest known ancestor (EKA) of your matches, and ancient DNA samples. Please be sure you’ve entered or updated your EKA, and that the information is current. You can find instructions for how to update or add your EKA here.
  • A recent addition to the haplogroup story includes Haplogroup Badges.
  • Country Frequency showing where this haplogroup is found with either a table view or an interactive map
  • Famous and infamous Notable Connections, including Mayflower passengers, Patriots from the American Revolution, US presidents, royal houses, artists, musicians, authors, pirates, sports figures, scientists, and more.

If you know of a proven connection to a notable figure, contact customer support and let them know! Notable connections are added every week.

One famous Discover connection is Ludwig von Beethoven which resulted from a joint academic study between FamilyTreeDNA and academic researchers. It’s quite a story and includes both a mystery and misattributed parentage. You can see if you match on Discover and read about the study, here.

  • Updated Migration Map, including locations of select ancient DNA sites
  • The Time Tree, probably the most popular Discover report, shows the most current version of the Y DNA phylotree, updated weekly, plus scientifically calculated ages for each branch. Tree node locations are determined by your matches and their EKA countries of origin. I wrote about the Time Tree, here.
  • Anticipated in early 2024, the EKA and block tree matches will also be shown on the Time Tree in Discover for individual Big Y testers, meaning they will need to sign in through their kits.
  • The Group Time Tree, visible through group projects, takes the Time Tree a step further by including the names of the EKA of each person on the Time Tree within a specific project. Information is only displayed for project members who have given permission to include their data. You can select specific project groupings to view, or the entire project. I wrote about the Group Time Tree here and here.
  • Globetrekker is an exclusive Big Y mapping feature discussed here, here, here, and here.
  • Ancient Connections includes more than 6,100 ancient Y DNA results from across the globe, which have been individually analyzed and added for matching in Discover. Ancient Connections serve to anchor haplogroups and provide important clues about matches, migration paths and culture. New connections are added weekly or as academic papers with adequate Y DNA coverage are released.
  • Your Ancestral Path, which lists the haplogroups through every step from the tester back to Y Adam and beyond. Additional information for each haplogroup in your path includes “Time Passed” between haplogroups, and “Immediate Descendants,” meaning haplogroups that descend from each subclade. New columns recently added include “Tested Modern Descendants” and “Ancient Connections.”
  • Suggested Projects include surname, haplogroup, and geographic projects. Katy said that people joining projects are more likely to collaborate and upgrade their tests. You can also see which projects other men with this haplogroup have joined, which may well be projects you want to join too.
  • Scientific Details provides additional information, such as each branch’s confidence intervals and equivalent variables (SNPs). You can read more here.
  • Compare Haplogroups is the most recent new feature, added just last month, which allows you to enter any two haplogroups and compare them to determine their most recent common ancestral haplogroup. You can read about Compare Haplogroups, here.

Please note that the Studies feature is coming soon, providing information about studies whose data has been included in Discover.

You can read about Discover here, here, here, and here.

If you’re interested, FamilyTreeDNA has released a one-minute introduction to Y DNA and Discover that would interest new testers, here.

Earliest Known Ancestor (EKA) Improvement

Another improvement is that the earliest known ancestor is MUCH easier to enter now, and the process has been simplified. The EKAs are critical for Discover, so PLEASE be sure you’ve entered and updated your EKA.

Under the dropdown beside your name in the upper right-hand corner of your personal page, select Account Settings, then Genealogy and Earliest Known Ancestors. Complete the information, then click on “Update Location” to find or enter the location on a map to record the coordinates.

It’s easy. Just type or drop a pin and “Save.”

Saving will take you back to the original EKA page. Save that page, too.

Recommended Projects on Haplogroups & SNPs Page

You’re probably aware that Discover suggests projects for Y DNA testers to join, but recommended haplogroup projects are available on each tester’s pages, under the Y DNA Haplotree & SNPs page, in the Y DNA STR results section.

If there isn’t a project for your immediate haplogroup, just scroll up to find the closest upstream project. You can also view this page by Variants, Surnames and Countries.

This is a super easy tool to use to view which surnames are clustered with and upstream of your haplogroup. With Family Finder haplogroups being assigned now, I check my upstream haplogroups almost daily to see what has been added.

For example, my Big Y Estes results are ten branches below R-DF49, but several men, including Estes testers, have been assigned at this level, thanks to Y DNA haplogroups from Family Finder testing. I can now look for these haplogroups in the STR and Family Finder matches lists and see if those men are receptive to Big Y testing.

Abandoned Projects

Sometimes group project administrators can no longer function in that capacity, resulting in the project becoming abandoned. FamilyTreeDNA has implemented a feature to help remedy that situation.

If you discover an abandoned project, you can adopt the project, spruce things up, and select the new project settings. Furthermore, administrators can choose to display this message to recruit co-administrators. I need to do this for several projects where I have no co-admin.

If you are looking for help with your project, you can choose to display the button
through the Project Profile page in GAP. For non-project administrators, if you’d like to help, please email the current project administrators.

New Kit Manager Feature

FamilyTreeDNA has added a “Kit Manager” feature so that an individual can designate another person as the manager of their kit.

This new setting provides an avenue for you to designate someone else as the manager of your DNA test. This alerts FamilyTreeDNA that they can share information with both of you – essentially treating your designated kit manager the same as you.

If you’re the kit manager for someone else, you NEED to be sure this is completed. If that person is unavailable for some reason, and support needs to verify that you have legitimate access to this kit, this form and the Beneficiary form are the ONLY ways they can do that.

If your family member has simply given you their kit number and password, and for some reason, a password reset is required, and their email address is the primary contact – you may be shut out of this kit if you don’t complete this form.

Beneficiary Page

Additionally, everyone needs to be sure to complete the Beneficiary page so that in the event of your demise, FamilyTreeDNA knows who you’ve designated to access and manage your DNA account in perpetuity. If you’ve inherited a kit, you need to add a beneficiary to take over in the event of your death as well.

What is FamilyTreeDNA working on now?

Currently in the Works

Katy moved on to what’s currently underway.

Privacy and Security

Clearly, the unauthorized customer data exposure breach at 23andMe has reverberated through the entire online community, not just genetic genealogy. You can read about the incident here, here, here, and here.

FamilyTreeDNA has already taken several steps, and others are in development and will be released shortly.

Clearly, in this fast-moving situation, everything is subject to change.

Here’s what has happened and is currently planned as of today:

  • Group Project Administrators will be required to reset their password soon.

Why is this necessary?

Unauthorized access was gained to 23andMe accounts by people using the same password for multiple accounts, combined with their email as their user ID. Many people use the same password for every account so that they can remember it. That means that all a hacker needs to do is breach one account, and they can use that same information to “legitimately” sign in to other accounts. There is no way for the vendor to recognize this as unauthorized since they have both your user ID and password.

That’s exactly what happened at 23andMe. In other breaches, this information was exposed, and hackers simply tried the same username and password combination at 23andMe, exposing the entire account of the person whose account they signed in “as.” This includes all of their matches, genetic tree, shared matches, matches of matches, ethnicity, and segments. They could also have downloaded both the match list and the raw DNA file of the compromised account.

At FamilyTreeDNA, project administrators can select their own username, which could be their email, so they will be required to reset their password.

Additional precautions have been put in place on an interim basis:

  • A pause in the ability to download match and segment information.
  • A pause in accepting 23andMe uploads.

Administrators will also be required to use two-factor authentication (2FA.) To date, two of the four major vendors are requiring 2FA. I would not be surprised to see it more broadly. Facebook recently required me to implement 2FA there, too, due to the “reach” of my postings, but 2FA is not required of everyone on Facebook.

Please note that if you received an email or message that is supposedly from any vendor requiring 2FA, GO DIRECTLY TO THAT VENDOR SITE AND SIGN IN.  Never click on a link in an email you weren’t expecting. Bad actors exploit everything.

Customers who are not signing in as administrators are not required to implement 2FA, nor will they be required to reset their password.

Personally, I will implement 2FA as soon as it’s available.

While 2FA is an extra step, it’s easy to get used to, and it has already literally saved one of my friends from an authorized hack on their primary and backup email accounts this week. Another friend just lost their entire account on Facebook because someone signed in as them. Their account was gone within 15 minutes.

2FA is one of those things you don’t appreciate (at all) until it saves you, and then, suddenly, you’re incredibly grateful.

At this point in time, FamilyTreeDNA users will NOT be required to do a password reset or implement 2FA. This is because customers use a kit number for sign-in and not a username or email address. I would strongly recommend changing your password to something “not easy.” Never reuse passwords between accounts.

I really, really want you to visit this link at TechRepublic and scroll down to Figure A, which shows how long it takes a hacker to crack your password. I guarantee you, it’s MUCH quicker than you’d ever expect.

Kim Komando wrote about this topic two years ago, so compare the two charts to see how much easier this has become in just two years.

Again, if you receive an email about resetting your password, don’t click on a link. Sign in independently to the vendor’s system, but DO reset your password.

FamilyTreeDNA also engages in additional security efforts, such as ongoing penetration testing.

New Permissions

Additionally, at FamilyTreeDNA, changes were already in the works to separate out at least two permissions that testers can opt-in to without granting project administrators Advanced rights.

  • Download data
  • Purchase tests

The ability to purchase tests can be very important because it allows administrators to order and pay for tests or upgrades on behalf of this tester anytime in the future.

Family Finder Haplogroups

FamilyTreeDNA has already begun releasing mid-level Y DNA haplogroups for autosomal testers in a staggered rollout of several thousand a day.

I wrote about this in the article, FamilyTreeDNA Provides Y DNA Haplogroups from Family Finder Autosomal Tests, so I’m not repeating all of that information here – just highlights.

  • The Family Finder haplogroup rollout is being staggered and began with customers on the most recent version of the testing chip, which was implemented in March of 2019.
  • Last will be transfers/uploads from third parties.
  • Haplogroups resulting from tests performed in the FTDNA labs will be visible to matches and within projects. They will also be used in both Discover and the haplotree statistics. This includes Family Finder plus MyHeritage and Vitagene uploads.
  • Both MyHeritage and Vitagene are uploaded or “transferred” via an intracompany secure link, meaning FamilyTreeDNA knows that their information is credible and has not been manipulated.
  • Haplogroups derived from tests performed elsewhere will only be visible to the user or a group administrator viewing a kit within a project. They will not be visible to matches or used in trees or for statistics.
  • Any man who has taken a Y DNA STR test will receive a SNP-confirmed, updated haplogroup from their Family Finder test that replaces their predicted haplogroup from the STR test.

Please read this article for more information.

New Discover Tools and Updates

Discover content continues to be updated, and new features are added regularly, creating an increasingly robust user experience.

Soon, group administrators will be able to view all Discover features (like Globetrekker) when viewing kits of project members who have granted an appropriate level of access.

Ancient and Notable connects are added weekly, and a new feature, Study Connections, will be added shortly.

Study Connections is a feature requested by customers that will show you which study your academic matches came from. Today, those results are used in the Y DNA tree, but the source is not detailed.

Anticipated in early 2024, the EKA and block tree matches will also be shown on the Time Tree in Discover for individual Big Y testers (not publicly).

Big Y FaceBook Group

FamilyTreeDNA has ramped up its social media presence. They launched the Big Y Facebook group in July 2023, here, which currently has just under 9000 members. Several project administrators have volunteered their time to help manage the group.

FamilyTreeDNA Blog

In addition, FamilyTreeDNA is publishing at least one blog article each week, and sometimes more. You can view or subscribe here. Some articles are written by FamilyTreeDNA staff, but project administrators and customers author other content.

Multi-Language Support

Translation of the main FamilyTreeDNA website and results pages to Spanish has begun, with more languages planned soon.

Paypal, Payments, and Gift Cards

Paypal has been added as a payment selection, along with a PayPal option that provides the ability to make payments.

Additionally, a gift card can be purchased from the main page.

Million Mito Project & Mitotree

Work on the Million Mito Project is ongoing.

The Million Mito Project was launched in 2020 as a collaborative effort between FamilyTreeDNA’s Research & Development Team and the scientific portion of the Genographic Project. I’m a team member and wrote about the Million Mito Project, here.

We’re picking up from where the Phylotree left off in 2016, analyzing 20 times more mtDNA full sequences and reimagining the mtDNA Haplotree. By examining more mtDNA data and applying the processes that allowed FamilyTreeDNA to build the world’s largest Y DNA Haplotree, we can also create the world’s largest Mitotree.

In 2022, the first update was released, authored by the Million Mito team, with the discovery of haplogroup L7. You can read about this amazing discovery rooted deep in the tree here, here, and here. (Full disclosure: I’m a co-author.)

Not only that, but “Nature Scientific Reports” selected this article as one of five named Editor’s Choice in the Mitogenomics category, here. In the science world, that’s a HUGE deal – like the genetic Emmy.

Here’s one example of the type of improvements that can be expected. Currently, the formation of haplogroup U5a2b2a reaches back to about 5000 years ago, but after reanalysis, current branches originated between 500 and 2,500 years ago, and testers are clustered more closely together.

This is SOOO exciting!!!

Just as Discover for Y DNA results was built one feature at a time, the same will be true for MitoDiscover. That’s my name, not theirs.

As the new Mitotree is rolled out, the user interface will also be updated, and matching will function somewhat differently. Specifically, it’s expected that many more haplogroups will be named, so today’s matching that requires an exact haplogroup match to be a full sequence match will no longer work. That and other matching adjustments will need to be made.

I can hardly wait. I have so many results I need to be able to view in a tree format and to place in a timeframe.

You can be included in this exciting project, learn more about your matrilineal (mother’s) line, and hopefully break down some of those brick walls by taking the full sequence mitochondrial DNA test, here.

After the new Mitotree is rolled out and the Y DNA Family Finder haplogroups are completed, Family Finder customers, where possible, will also receive at least a basic-level mitochondrial haplogroup. Not all upload files from other vendors include mtDNA SNPs in their autosomal files. The mitochondrial Family Finder haplogroup feature isn’t expected until sometime in 2025, after the new tree and MitoDiscover are complete.

The Future

What’s coming later in 2024, or is ongoing?

Privacy Laws

Most people aren’t aware of the new privacy laws in various states, each of which has to be evaluated and complied with.

The effects of these changes will be felt in various areas as they are implemented.

New Kits Opted Out of IGG

Since late August, all new FTDNA kits are automatically opted OUT of Investigative Genetic Genealogy (IGG) by default.

Regular matching consent and IGG matching consent have been separated during onboarding.

Biobanking Separate Consent

Another consent change is to have your sample biobanked. FamilyTreeDNA has always maintained your sample for “roughly 25 years.” You could always ask to have your sample destroyed, but going forward, you will be asked initially if you want your sample to be retained (biobanked.) It’s still free.

Remember, if someone declines the biobanking option, their DNA will be disposed of after testing. They can’t order upgrades without submitting a new sample. Neither can their family after they’re gone. I ordered my mother’s Family Finder test many years after she had gone on to meet our ancestors – and I’m incredibly grateful every single day.

MyHeritage Tree Integration

An exciting change coming next year is tree integration with MyHeritage.

And no, before any rumors get started, FAMILYTREEDNA IS NOT MERGING WITH MYHERITAGE. It’s a beneficial marriage of convenience for both parties.

In essence, one of the primary focuses of MyHeritage is trees, and they do that very well. FamilyTreeDNA is focused on DNA testing and their existing trees have had issues for years. MyHeritage trees are excellent, support pedigree collapse, provide search capabilities that are NOT case sensitive, SmartMatching, and much more.

If you don’t have a MyHeritage account, creating one is free, and you will be able to either port your existing FamilyTreeDNA tree, or begin one there. If you’re already a MyHeritage member, FamilyTreeDNA and MyHeritage are planning together for a smooth integration for you. More detailed information will be forthcoming as the integration progressed and is released to customers.

You’ll be able to connect multiple kits to your tree at MyHeritage, just like you can at FamilyTreeDNA today, which enables family matching, aka bucketing.

You can also have an unlimited number of different trees at MyHeritage on the same account. You’re not limited to one.

After you link your initial FamilyTreeDNA kit to the proper person in your MyHeritage tree, you’ll be able to relink any currently linked kits.

MyHeritage will NOT receive any DNA information or match information from FamilyTreeDNA, and yes, you’ll be able to use the same tree independently at MyHeritage for their DNA matching.

You’ll still be able to view your matches’ trees, except it will actually be the MyHeritage tree that will be opened at FamilyTreeDNA in a new tab.

To the best of my knowledge, this is a win-win-win, and customers of both companies aren’t losing anything.

One concern is that some FamilyTreeDNA testers have passed away and cannot transition their tree, so a view-only copy of their tree will remain at FamilyTreeDNA so that their matches can still see their tree.

Big Y Infrastructure

Katy mentioned that internal discussions are taking place to see what changes could be made to improve things like matching and test processing times.

No changes are planned for SNP or STR coverage, but discussions are taking place about a potential update to the Telomere to Telomere (T2T) reference. No promises about if or when this might occur. The last part of the human genome to be fully sequenced, the T2T reference model includes the notoriously messy and unreliable region of the Y chromosome with many repeats, duplications, gaps, and deletions. Some data from this region is probably salvageable but has previously been omitted due to the inherent problems.

I’m not sure this shouldn’t be in the next section, the Wishlist.

Wishlist

There are lots of good things on the Wishlist – all of which I’d love.

I’d have difficulty prioritizing, but I’d really appreciate some Family Finder features in addition to the items already discussed. I’d also like to see some GAP (administrator) tool updates.

Which items do you want to see most?

Katy said that FamilyTreeDNA is NOT planning to offer a Whole Genome Sequencing (WGS) test anytime soon. So, if you’re holding your breath, please don’t. Based on what Katy did say, WGS is very clearly not a consideration in 2024 and I don’t expect to see it in 2025 either unless something changes drastically in terms of technology AND pricing.

While WGS prices have come down, those consumer tests are NOT scanned at the depth and quality required for advanced tests like the Big Y or even Family Finder. Normally consumer-grade WGS tests are scanned between 2 and 10 times, where the FamilyTreeDNA lab scans up to 30 times in order to obtain a quality read. 30X scans are in the same category as medical or clinical grade whole genome scans. Significantly higher quality scans mean significantly higher prices, too, so WGS isn’t ready for genealogy prime time yet.

Additionally, commercially available WGS tests are returned to the customer “as is,” and you’re left to extract the relevant SNPs and arrange them into files, or find someone else to do that. Not to mention, in order to preserve the integrity of their database, FamilyTreeDNA does not accept Y or mitochondrial DNA uploads.

Recently, I saw two WGS files with a 20-25% no-call rate for the autosomal SNPs required for the Family Finder test. Needless to say, that’s completely unacceptable. Some tools attempt to “fix” that mess by filling in the blanks in the format of either a 23andMe or Ancestry file so you can upload to vendors, but that means you’re receiving VERY unreliable matches.

The reason none of the major four vendors offer WGS testing for genealogists is because it’s not financially feasible nor technologically beneficial. The raw data file alone won’t fit on most home computers. WGS is just not soup yet, and it won’t be for the general consuming public, including relevant tools, for at least a few years.

I’ve had my whole genome sequenced, and trust me, I wish it were feasible now, but it just isn’t.

Suggestions Welcomed

Katy said that if you have suggestions for items NOT on the wishlist today to contact her through support.

I would add that if you wish to emphasize any specific feature or need above others, please send that feedback, politely, to support as well.

Katy ended by thanking the various teams and individuals whose joint efforts together produce the products we use and enjoy today.

Lab Update

Normally, DNA testing companies don’t provide lab updates, but this conference is focused on group project administrators, who are often the most dedicated to DNA testing.

A lab update has become a tradition over the years.

Linda Jones, Lab Manager, provided a lab update.

You may or may not know that the FamilyTreeDNA lab shifted gears and stepped up to handle Covid testing.

Supply-chain shortages interfered, but the lab ran 24×7 between 2020 and 2022.

Today, the lab continues to make improvements to processes with the goal of delivering the highest quality results in a timely manner.

On Monday, after the conference, attendees could sign up for a lab tour. You might say we are a rather geeky bunch and really enjoy the science behind the scenes.

Q&A and Thank You

At the end of the conference, the FamilyTreeDNA management team answered questions from attendees.

Left to right, Daniel Au, CTO; Linda Jones, Lab Manager; Katy Rowe-Schurwanz, Product Manager; Clayton Conder, VP Marketing; Goran Runfeldt, Head of R&D; and Andrew Gefre, Development Manager. Not pictured, Jeremy Balkin, Support Manager; Kelly Jenkins, VP of Operations; and Janine Cloud, Group Projects Manager. Janine is also responsible for conferences and events, without whom there would have been no 2023 FamilyTreeDNA conference. Janine, I can’t thank you enough!

A huge thanks to all of these people and many others, including the presenters, CSRs,  IT, and other FamilyTreeDNA team members for their support during the conference, enabling us to enjoy the conference and replenish the well of knowledge.

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

If you haven’t already subscribed (it’s free,) you can receive an email whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase your price but helps me keep the lights on and this informational blog free for everyone. Please click on the 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 Book

Genealogy Books

Genealogy Research

Y-DNA Haplogroup O – When and How Did It Get to the Americas?

Y-DNA Haplogroup O has been found in male testers descended from a Native American ancestor, or in Native American tribes in the Americas – but sometimes things are more complex than they seem. The story of when and how haplogroup O arrived in the Americas is fascinating – and not at all what you might think.

Introduction

The concept of Native American heritage and indigenous people can be confusing. For example, European Y-DNA haplogroup R is found among some Native American men. Those men may be tribal members based on their mother’s line, or their haplogroup R European Y-DNA may have been introduced either through adoption practices or traders after the arrival of Europeans.

There is unquestionable genetic evidence that the origin of Haplogroup R in the Americas was through colonization, with no evidence of pre-contact indigenous origins.

Y-DNA testing and matching, specifically the Big Y-700 test, with its ability to date the formation of haplogroups very granularly, has successfully identified the genesis of Y-DNA haplogroups and their movement through time.

We’ve spent years trying to unravel several instances of Native American Y-DNA Haplogroup O and their origins. Native American, in this context, means that men with haplogroup O are confirmed to be Native American at some point in documented records. This could include early records, such as court or probate records, or present-day members of tribes. There is no question that these men are recognized as Native American in post-contact records or are tribal members, or their descendants.

What has not been clear is how and when haplogroup O entered the Native American population of these various lineages, groups, or tribes. In other words, are they indigenous? Were they here from the earliest times, before the arrival of colonists, similar to Y-DNA haplogroups C and Q?

This topic has been of great interest for several years, and we have been waiting for additional information to elucidate the matter, which could manifest in several ways:

  1. Ancient pre-contact DNA samples of haplogroup O in the Americas, but none have been found.
  2. Current haplogroup O testers in Native American peoples across the North and South American continents, forming a connecting trail genetically, geographically, and linearly through time. This has not occurred.
  3. Big-Y DNA matches within the Americas between Haplogroup O Native American lines unrelated in a genealogical timeframe whose haplogroup formation pre-dates European contact. This has not occurred.
  4. Big-Y DNA matches between Haplogroup O men whose haplogroups were formed in the Americas after the Beringian migration and expansion that scientists agree occurred at least 12-16K years ago, and possibly began earlier. Earlier human lineages, if they existed, may not have survived. A later Inuit and Na-Dené speaker circumpolar migration occurred 4-7K years ago. This has not occurred.
  5. Big-Y DNA matches with men whose most recent common ancestor haplogroup formation dates connect them with continental populations in other locations, outside of North and South America. This would preclude their presence in the Americas after the migrations that populated the Americas. This has occurred.

The Beringian migration took place across a now-submerged land bridge connecting the Chutkin Peninsula in Russia across the Bering Strait with the Seward Peninsula in Alaska.

By Erika Tamm et al – Tamm E, Kivisild T, Reidla M, Metspalu M, Smith DG, et al. (2007) Beringian Standstill and Spread of Native American Founders. PLoS ONE 2(9): e829. doi:10.1371/journal.pone.0000829. Also available from PubMed Central., CC BY 2.5, https://commons.wikimedia.org/w/index.php?curid=16975303

Haplogroup O is clearly Native American in some instances, meaning that it occurs in men who are members of or descend from specific Native American tribes or peoples. One man, James Revels, is confirmed in court records as early as 1656. However, ancestors of James Revels fall into category #5, as their upstream parental haplogroup is found in the Pacific islands outside the Americas after the migration period.

Based on available evidence, the introduction of haplogroup O appears to be post-contact. Therefore, haplogroup O is not indigenous to the Americans in the same sense as haplogroups Q and C that are found widespread throughout the Americas in current testers who are tribal members, descendants of tribal members, and pre-contact ancient DNA as mapped in the book, DNA for Native American Genealogy.

Ancient DNA

Haplogroup C is found in both North and South America today, as are these ancient DNA locations.

Haplogroup Q is more prevalent than Haplogroup C, and ancient DNA remains are found throughout North and South America before colonization.

No ancient DNA for Haplogroup O has been discovered in the Americas. We do find contemporary haplogroup O testers in regional clusters, which we will analyze individually.

Let’s take a look at what we have learned recently.

Wesley Revels’ Lineage

Wesley Revels was the initial Y-DNA tester whose results identified Haplogroup O as Native American, proven by a court record. That documentation was critical, and we are very grateful to Wesley for sharing both his information and results.

Wesley’s ancestor, James Revels, was Native American, born about 1656 and bound to European planter, Edward Revell. James was proven in court to be an Accomack “Indian boy” from “Matomkin,” age 11 in 1667. James was bound, not enslaved, until age 24, at which time he was to be freed and receive corn and clothes.

James had died by 1681 when he was named several times in the Accomack County records as both “James, an Indian” and “James Revell, Indian,” in reference to his estate. James lived near Edward Revell, his greatest creditor and, therefore, administrator of his estate, and interacted with other Indian people near Great Matompkin Neck. Marie Rundquist did an excellent job of documenting that here. Additional information about the Revels family and Matomkin region can be found here.

The location where Edward Revell lived, Manokin Hundred, was on the water directly adjacent the Great Matomkin (now Folly Creek) and Little Matomkin Creeks, inside the Metomkin Inlet. The very early date tells us that James Revels’s paternal ancestor was in the colonies by 1656 and probably born about 1636, or perhaps earlier.

Lewis and Revels men are later associated with the Lumbee Tribe, now found in Robeson and neighboring counties in North Carolina. The Lewis line descends from the Revels lineage, as documented by Marie and Wesley. Other men from this line have tested and match on lower-level STR markers, but have not taken the much more granular and informative Big-Y test.

Until recently, the men who matched Wesley Revels closely on the Big-Y test were connected with the Revels line and/or the Lumbee.

Wesley has a 37-marker STR match to a man with a different surname who had not tested beyond that level, in addition to several 12-marker STR matches to men from various locations. Men who provided known ancestral or current locations include one from Bahrain, two from the Philippines, and three from China. Those men have not taken the Big-Y, and their haplogroups are all predicted from STR results to O-M175 which was formed in Asia about 31,000 years ago.

12-marker matches can reach thousands of years back in time. Unless the matches share ancestors and match at higher levels, 12-marker matches are only useful for geographic history, if that. The Big Y-700 test refines haplogroup results and ages from 10s of thousands of years to (generally) within a genealogically relevant timeframe, often within a couple hundred years.

One of Wesley’s STR matches, Mr. Luo, has taken a Big Y-700 test. Mr. Luo descends directly from Indonesia in the current generation and is haplogroup O-CTS716, originating about 244 BCE, or 2244-ish years ago. Mr. Luo does not match Wesley on the Big-Y test, meaning that Wesley and Mr. Luo have 30 or more SNP differences in their Big-Y results, which equates to about 1,500 years. The common ancestor of Wesley Revels and Mr. Luo existed more than 1,500 years ago in Indonesia. It’s evident that Mr. Luo is not Native American, but his location is relevant in a broader analysis.

There is no question that Wesley’s ancestor, James Revels, was Native American based on the court evidence. There is also no question that the Revels’ paternal lineage was not in the Americas with the Native American migration group 12-16K years ago.

The remaining question is how and when James Revels’ haplogroup O ancestor came to be found on the Atlantic seaboard in the early/mid 1600s, only a few years after the founding of Jamestown.

The results of other Haplogroup O men may help answer this question.

Mr. Lynn

Another haplogroup O man, Mr. Lynn, matches Wesley on STR markers, but not on the Big-Y test.

Mr. Lynn identified his Y-DNA line as Native American, although he did not post detailed genealogy. More specifically, we don’t know if Mr. Lynn identified that he was Native on his paternal line because he matches Wesley, or if the Native history information was passed down within his family, or from genealogical research. Mr. Lynn could also have meant generally that he was Native, or that he was Native “on Dad’s side,” not specifically his direct patrilineal Y-line.

Based on Mr. Lynn’s stated Earliest Known Ancestor (EKA) and additional genealogical research performed, his ancestor was John Wesley Lynn (born approximately 1861, died 1945), whose father was Victor Lynn. John’s death certificate, census, and his family photos on Ancestry indicate that he was African American. According to his death certificate, his father, Victor Lynn, was born in Chatham Co., NC, just west of Durham.

Family members are found in Baldwin Township, shown above.

I did not locate the family in either the 1860 or 1870 census. In 1860, the only Lynn/Linn family in Chatham County was 50-year-old Mary Linn and 17-year-old Jane, living with her, presumably a daughter. Both are listed as “mulatto” (historical term) with the occupation of “domestic.” They may or may not be related to John Wesley Lynn.

In 1870, the only Linn/Lynn in Chatham County is John, black, age 12 or 13 (so born in 1857 or 1858), farm labor, living with a white family. This is probably not John Wesley Lynn given that he is found with his mother in 1880 and the ages don’t match.

In 1880. I find Mary Lynn in Chatham County, age 48, single, black, with daughter Eliza Anne, 20, mulatto, sons John Wesley, 14 so born about 1866, and Charles 12, both black. Additionally, she is living with her nieces and nephews, Cephus, black, 12, Lizzie, 7, mulatto, Malcom, 4, mulatto, William H, 3, mulatto (I think, written over,) and John age 4, mulatto. The children aged 12 and above are farm labor.

In 1880, I also find Jack Lynn, age 28, black, married with 3 children, living beside William Lynn, 25, also married, but with no children.

Trying to find the family in 1870 by using first name searches only, I find no black Mary in 1870 or a mulatto Mary with a child named Jack or any person named Cephus by any surname. I don’t find Jack or any Lynn/Linn family in Chatham County.

The 1890 census does not exist.

In the 1900 census, I find Wesley Lynn in Chatham County, born in January of 1863, age 37, single, a boarder working on the farm of John Harris who lives beside Jack Lynn, age 43, born in April of 1857. Both Lynn men are black. I would assume some connection, given their ages, possibly or probably brothers.

In 1940, John Wesley Lynn, age 74, negro (historical term), is living beside Victor Lynn, age 37, most likely his son.

I could not find Victor Lynn, John Wesley Lynn’s father in any census, so he was likely deceased before 1880 but after 1867, given that Mary’s son Charles Lynn was born in 1868, assuming Mary’s children had the same father. The fact that Mary was listed as single, not married nor widowed suggests enslavement, given that enslaved people were prohibited from legally marrying.

About the only other assumption we can make about Victor Sr. is that he was probably born about 1832 or earlier, probably in Chatham County, NC based on John Wesley’s death certificate, and he was likely enslaved.

Subclades of Haplogroup O

Both the Revels and Lynn men are subclades of haplogroup O and both claim Native heritage – Wesley based on the Revels genealogy and court documents, and Mr. Lynn based on the Native category he selected to represent his earliest known paternal ancestor at FamilyTreeDNA.

Both men have joined various projects, including the American Indian Project, which provides Marie and me, along with our other project co-administrators, the ability to work with and view both of their results at the level they have selected.

How Closely Related Are These Haplogroup O Men?

How closely related are these two men?

By Viajes_de_colon.svg: Phirosiberiaderivative work: Phirosiberia (talk) – Viajes_de_colon.svg, CC BY-SA 3.0, https://commons.wikimedia.org/w/index.php?curid=8849049

  • Do the haplogroups of the Revels men and Mr. Lynn converge in a common ancestor in a timeframe BEFORE colonialization, meaning before Columbus “discovered” the Caribbean islands when colonization and the slave trade both began?
  • Do the haplogroups converge on North or South American soil or elsewhere?
  • Is there anything in the haplogroup and Time Tree information that precludes haplogroup O from being Native prior to the era of colonization?
  • Is there anything that confirms that a haplogroup O male or males were among the groups of indigenous people that settled the Americas sometime between 12 and 26 thousand years ago? Or even a later panArctic or circumpolar migration wave?

Haplogroup O is well known in East Asia, Indonesia, and the South Pacific.

Another potential source of haplogroup O is via Madagascar and the slave trade.

The Malagasy Roots Project has several haplogroup O individuals, including the Lynn and Revels men, who may have joined to see if they have matches. We don’t know why the various haplogroup O men in the project joined. Other haplogroup O men in the project may or may not have proven Malagasay heritage.

Information provided by the project administrators is as follows:

The people of Madagascar have a fascinating history embedded in their DNA. 17 known slave ships came from Madagascar to North America during the Transatlantic Slave Trade. As a result, we find Malagasy DNA in the African American descendants of enslaved people, often of Southeast Asian origin. One of the goals of this project is to discover the Malagasy roots of African Americans and connect them with their cousins from Madagascar. Please join us in this fascinating endeavor. mtDNA Haplogroups of interest include: B4a1a1b – the “Malagasy Motif”, M23, M7c3c, F3b1, R9 and others Y-DNA Haplogroups include: O1a2 – M50, O2a1 – M95/M88, O3a2c – P164 and others

Resources:

http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2987306/  http://www.ncbi.nlm.nih.gov/pmc/articles/PMC1199379/  http://mbe.oxfordjournals.org/cgi/pmidlookup?view=long&pmid=19535740  http://www.biomedcentral.com/1471-2156/15/77  http://www.biomedcentral.com/1471-2164/10/605

The Malagasy group only has one other man who is haplogroup O and took the Big-Y test, producing haplogroup O-FTC77008. Of course, we don’t know if he has confirmed Madagascar ancestry, and his haplogroup is quite distant from both Revels and Lynn in terms of when his haplogroup was formed.

Viewing the Malagasy Project’s Group Time Tree, above, the common ancestor between those three men lived about 28K BCE, or 30,000 years ago.

Haplogroup O Project Group Time Tree

The Haplogroup O Project Time Tree provides a better representation of haplogroup O in general given that it has a much wider range of samples.

On this tree, I’ve labeled the haplogroup formation dates, along with the Revels/Lewis line which descends from O-FT45548. This haplogroup includes one additional group member whose surname is locked, as he hasn’t given publication permission. The haplogroup formation date of 1766 occurs approximately 85 years after James Revel’s birth, so is attributable to some, but not all of his descendants. At least one descendant falls into the older Haplogroup O-BY60500.

The common ancestor of all three, meaning Revels, Lewis, and the man whose name is locked and does not know his genealogy, is haplogroup O-BY60500, born about 1741.

Their ancestral haplogroup before that, O-FT11768, is much older.

Two Filipino results are shown on and descending from the parent branch of O-FT11768, formed about 3183 BCE, or about 5183 years ago. This tells us that the ancestors of all these men were in the same place, most likely the Philippines, at that time.

3183 BCE (5180 years ago) is well after the Native American migration into the Americas.

Discover Time Tree

Obviously, not every tester joins a project, so now I’m switching to the Discover Time Tree which includes all Y-DNA haplogroup branches. Their common haplogroup, O-FT11768, has many branches, not all of which are shown below. I’m summarized unseen branch locations at bottom left.

Expanding the Time Tree further to view all of the descendant haplogroups of O-FT11768, we see that this was a major branch with many South Pacific results, including the branch of O-FT22410, bracketed in red, which has three members.

One is Mr. Lynn whose feather indicates Native American as his EKA country selection, one is a man whose ancestor is from Singapore, and one is an unknown individual who did not enter his ancestor’s country of origin.

Geography

Wesley’s STR match list, which can reflect matches further back in time than the Big-Y test, includes islands near Singapore. This geography aligns with what is known about haplogroup O.

The distance between this Asian region and continental America, 9000+ miles distant by air, is remarkable and clearly only navigable at that time by ship, meaning ships with experienced crew, able to navigate long distances with supplies and water.

We know that in 760 CE, about 1240 years ago, Mr. Lynn’s haplogroup O-F24410 was formed someplace in the South Pacific – probably in Malaysia or a nearby island. This region, including the Philippines, is home to many haplogroup O men. The majority of haplogroup O is found in Asia, the South Pacific, and Diaspora regions.

We know that Hawaii was populated by Polynesian people about 1600 years ago, prior to the age of colonization. Hawaii is almost 7000 miles from Singapore.

Here’s the challenge. How did these haplogroup O men get from the South Pacific to Virginia? Mr. Lynn and the Singapore tester share a common ancestor about 1240 years ago, or 760 CE.

There is no known or theorized Native American settlement wave across Beringia as late as 760 CE. We know that the parent haplogroup was someplace near Singapore in approximately 760 CE.

Two Filipino men and the Revels’ ancestors were in the same location in the Pacific Islands 5180 years ago. How did they arrive on the Eastern Shore in Virginia, found in the Native population, either in or before 1656 when James Revels was born?

What happened in the 3500 years between those dates that might explain how James Revel’s ancestor made that journey?

Academic Papers

In recent years, there has been discussion of possible shoreline migration routes along the Russian coast, Island hopping along Alaska, Canada, and what is now the US, known as the Kelp Highway or Coastal Migration Route – but that has yet to be proven.

Even if that is the case, and it’s certainly a possibility, how did this particular group of men get from the Pacific across the continent to the Atlantic shore in such a short time, leaving no telltale signs along the way? The Coastal Migration Theory hypothesis states that this migration occurred from 12-16 thousand years ago, and then expanded inland over the next 3-5K years. They could not have expanded eastward until the glaciers receded. Regardless, the parent haplogroup and associated ancestors are still found in the Philippines and South Pacific 5000 years ago – after that migration and expansion had already occurred.

The conclusion of the paper is that there is no strong evidence for a Pacific shoreline migration. Regardless, that’s still thousands of years before the time range we’re observing.

We know that the Lynn ancestor was with men from Indonesia in 760 CE, and the Revels ancestor was with men from the Pacific Islands, probably the Philippines, 5180 years ago. They couldn’t have been in two places at the same time, so the ancestors of Revels and Lynn were not in the Americas then.

A 2020 paper shows that remains from Easter Island (Rapa Nui) show Native American DNA, and suggests that initial contact occurred between the two cultures about 1200 CE, or about 800 years ago, but there is not yet any pre-contact or post-contact ancient Y-DNA found in the Americas that shows Polynesian DNA. Furthermore, the hypothesis is that the DNA found on Easter Island came from the Americas, not vice versa. The jury is still out, but this does show that trans-Pacific contact between the two cultures was taking place 800 years ago, at least two hundred years pre-European contact.

Australasian migration to South America is also suggested by one set of remains found in Brazil dating from more than 9000 years ago, but there have been no other remains found indicating this heritage, either in Brazil, or elsewhere in the Americas.

Based on the Time Tree dates of the Haplogroup O testers in our samples, we know they were in the Islands of Southeast Asia after this time period. Additionally, there are no Australia/New Zealand matches.

The Spanish

The Spanish established an early trade route between Manila and Acapulco beginning in 1565. Consequently, east Asian men left their genetic signature in Mexico, as described in this paper.

Historians estimate that 40-129K immigrants arrived from Manilla to colonial Mexico between 1565 and 1815, with most being enslaved upon arrival. Approximately one-third of the population in Manilla was already enslaved. Unfortunately, this paper focused only on autosomal genome-wide results and did not include either Y-DNA, nor mitochondrial. However, the paper quantifies the high degree of trade, and indicates that the Philippines and other Asian population haplotypes are still prevalent in the Mexican population.

In 2016, Dr. Miguel Vilar, the lead scientist with the National Geographic Genographic project lectured in Guam about the surprising Native American DNA found in the Guam population and nearby islands. He kindly provided this link to an article about the event.

Guam was colonized by Spain. In the image from the Boxer Codex, above, the local Chamorro people greet the Manila Galleon in the Ladrones Islands, as the Marianas were called by the Spanish, about 1590.

Native Hawaiians descend from Polynesian ancestors who arrived in the islands about 400 CE, or about 1600 years ago. Captain Cook, began the age of European contact in Hawaii in 1778.

Five Possibilities

There are five possible origins of haplogroup O in the Americas.

  • Traditional migration across Beringia with the known migrations, estimated to have occurred about 12-16K years ago.
  • A Kelp Highway Coastal Migration which may have occurred about 12-16K years ago and dispersed over the next 3-5K years.
  • Circumpolar migration – specifically Inuit and Na-Dene speakers, about 4-6K years ago.
  • Post-contact incorporation from the Pacific Islands resulting from shipping trade on colonial era ships sometime after 1565.
  • Post-contact incorporation from Madagascar resulting from the importation of humans who may or may not have been enslaved upon arrival.

Do we have any additional evidence?

Other Haplogroup O DNA

From my book, DNA for Native American Genealogy:

Testers in haplogroup O-BY60500 and subclade O-FT45548 have proven Native American heritage.

We have multiple confirmed men from a common ancestor who is proven to be an enslaved Accomack “Indian boy,” James Revell, born in 1656, “belonging to the Motomkin” village, according to the Accomack County, Virginia court records. These men tested as members of haplogroup O-F3288 initially, after taking the Big Y-500 test. However, upgrading to the Big Y-700 produced more granular results and branches reflecting mutations that occurred since their progenitor was born in 1656.

Unfortunately, other than known descendants, these men have few close Y-DNA or Big Y-700 matches.

Without additional men testing from different unrelated lines, or ancient haplogroup O being discovered, we cannot confirm that this haplogroup O male’s ancestor was not introduced into the Matomkin Tribe in some way post-contact. Today, one descendant from this line is a member of the Lumbee Tribe.

However, that isn’t the end of the haplogroup O story.

The Genographic Project data shows one Haplogroup O Tlingit tribal member from Taku, Alaska, along with several testers from Mexico that indicate their paternal line is indigenous. Some people from Texas identify their paternal line as Hispanic.

Another individual indicates they were born on the Fountain Indian Reserve, in British Columbia and speaks the St’at’imcets language, an interior branch of Coastal Salish.

Haplogroup O has been identified as Native American in other locations as well.

Much of the information about Haplogroup O testers was courtesy of the Genographic Project, meaning we can’t contact those people to request upgraded tests, and we can’t obtain additional information in addition to what they provided when they tested. As an affiliate researcher, I’m very grateful to the National Geographic Society’s Genographic project for providing collaborative data.

When the book was published, the Discover Time Tree had not yet been released. We have additional information available today, including the dates of haplogroup formation.

FamilyTreeDNA Haplotree and Discover

The FamilyTreeDNA Haplotree (not to be confused with the Discover Time Tree) shows 10 people at the O-M175 level in Mexico, 10 people in the US report Native American heritage, 2 in Jamaica, and one each in Peru, Panama, and Cuba. There’s also one tester from Madagascar.

Altogether, this gives us about 35 haplogroup O males in the Americas, several with Native heritage.

Please note that I’ve omitted Hawaii in this analysis and included only North and South America. The one individual selecting Native Hawaiian (Kanaka Maoli) is in haplogroup O-M133.

Let’s look at our three distinct clusters.

Cluster 1 – Pacific Northwest – Alaska and Canada

We have a cluster of three individuals along the Pacific Coast in Alaska and Canada who have self-identified as Native, provided a tribal affiliation, and, in some cases, the spoken language.

How might haplogroup O have arrived in or near Vancouver, Washington? We know that James Cook “discovered” Hawaii in 1778, naming it the Sandwich Islands. By 1787, a female Hawaiian died en route to the Pacific Northwest, and the following year, a male arrived. Hawaii had become a provisioning stop, and the Spanish took Hawaiians onto ships as replacement workers.

Hawaiian seamen, whalers, and laborers began intermarrying with the Native people along the West Coast as early as 1811. Their presence expanded from Oregon to Alaska. Migration and intermarriage along the Pacific coast began slowly, but turned into a steady stream 30 years later when we have confirmed recruitment and migration of Hawaiian people

In 1839, John Sutter recruited a small group of 10 Hawaiians to travel with him to the then-Mexican colony of Alta, California.

By the mid-1800s, hundreds of Hawaiians lived in Canada and California. In 1847, it was reported that 10% of San Francisco’s residents were Hawaiian. Some of those people integrated with the Native American people, particularly the Miwok and Maidu. The village of Verona, California was tri-lingual: Hawaiian, a Native language, and English, and is today the Sacramento-Verona Tribe.

This article provides a history of the British Company who administered Fort Vancouver, near Vancouver, Washington, that included French-Canadians, Native Americans and Hawaiians. In 1845, 119 Hawaiians were employed at the fort. One of the 119, Opunuia, had signed on as an “engagé,” meaning some type of hired hand or employee, with the Hudson Bay Company for three years, after which he would be free to return home to Honolulu or establish himself in the Oregon Country. He married a woman from the Cascade Tribe.

The descendants of the Hawaiian men and Native women were considered tribal members. In most tribes, children took the tribal status and affiliation of the mother.

The Taku and Sitka, Alaska men on the map are Tlingit, and the man from British Columbia is from the Fountain Indian Reserve.

Hawaiian recruitment is the most likely scenario by which haplogroup O arrived in the tribes of the Pacific Northwest. In that sense, haplogroup O is indeed Native American but not indigenous to that region. The origins of haplogorup O in the Pacific Northwest are likely found in Hawaii, where it is indigenous, and before that, Polynesia – not due to a Beringian crossing.

Cluster 2 – Mexico

We find a particularly interesting small cluster of 4 haplogroup O individuals in interior Mexico.

In the 1500s, Spain established a trade route between Mexico and Manilla in the Philippines.

In 1564, four ships left Mexico to cross the Pacific to claim Guam and the Philippines for King Philip II of Spain. The spice trade, back and forth between Mexico and the Philippines began the following year and continued for the next 250.

Landings occurred along the California coast and the western Mexican coastline. The majority of the galleon crews were Malaysian and Filipino who were paid less than the Spanish sailors. Slaves, including people from the Marianas were part of the lucrative cargo.

One individual in Texas reports haplogroup O and indicates their paternal ancestors were Hispanic/Native from Mexico. A haplogroup O cluster claiming Native heritage is found near Zacatecas, Fresnillo and San Luis Potosi in central Mexico. Additionally, mitochondrial haplogroup F, also Asian, is found there as well. Acapulco is the lime green pin.

An additional haplogroup O tester with Native heritage is found in Lima, Peru.

Haplogroup O men are found in Panama, Jamaica and Cuba, but do not indicate the heritage of their paternal ancestral line. None of these men have taken Big-Y tests, and some may well have arrived on the slave ships from Madagascar, especially in the Caribbean. This source attributes some enslaved people in Jamaica to Hawaiian voyages.

I strongly suspect that the Mexican/Peru grouping in close proximity to the Pacific coastline is the result of the Manilla-Mexico 250-year trade route. The Spanish also plied those waters regularly. Big Y testing of those men would help flesh-out their stories – when and how haplogroup O arrived in the local population.

Cluster 3 – East Coast

At first glance, the East Coast grouping of men with a genetic affinity to the people of the Philippines and Indonesia seems more difficult to explain, but perhaps not.

On the East Coast, we have confirmed reports of whalers near Nantucket as early as 1765 utilizing crewmen from Hawaii, known then as the Sandwich Islands, Tahiti, and the Cape Verde Islands off of Africa. A thorough review of early literature might well reveal additional information about early connections with the Sandwich Islands, and in particular, sailors, crew, or enslaved people.

The Spanish and French were the first to colonize the Philippines by the late 1500s. They had discovered the Solomon Islands, Melanesia, and other Polynesian Islands, and by the early 1600s, the Dutch were involved as well.

The Encyclopedia Britanica further reports that Vasco Balboa first sailed into the Pacific in 1513 and seven years later, Ferdinand Magellan rounded the tip of South America. The Spanish followed, establishing a galley trade between Manila, in the Philippines and Acapulco in western Mexico.

While I found nothing specific stating that the earliest voyages brought men from the Philippines and Oceania back to their European home ports with them, we know that early European captains on exploratory voyages took Native people from the east coast of the Americas on their return journey, so there’s nothing to preclude them from doing the same from the Pacific. The early explorers stayed for months among the Oceanic Native peoples. If they were short on sailors for their return voyage, Polynesian men filled the void.

We know that the Spanish took slaves as part of their trade. We know that the ships in the Pacific took sailors from the islands. If the men themselves didn’t stay in the locations they visited, it’s certainly within the realm of possibility that they fathered children with local, Native women. Furthermore, given that the slave trade was lucrative, it’s also possible that some Pacific Island slaves were taken not as crew but with the intention of being sold into bondage. Other men may have escaped the ships and hidden among the Native Tribes along the eastern seaboard.

Fishing in Newfoundland and exploration in what would become the US was occurring by 1500, so it’s certainly possible that some of the indigenous people from Indonesia and the Philippines were either stranded, sold to enslavers, escaped, or chose to join the Native people along the coastline in North America. Ships had to stop to resupply rations and take on fresh water.

We know that by the mid-1600s, James Revels, whose father carried haplogroup O, had been born on the Atlantic coast of Virginia or Maryland, probably on the Delmarva Peninsula, short for Delaware, Maryland, Virginia, where the Accomac people lived.

There are other instances of haplogroup O found along the east coast.

On the eastern portion of the haplogroup O map from the book, DNA for Native American Genealogy, we find the following locations:

  • Hillburn, NY – man identified as “Native American Black.”
  • Chichester County, PA – Genographic tester identified the location of his earliest known ancestor – included here because O is not typically found in the states.
  • Accomack County, VA – Delmarva peninsula – James Revels lineage
  • Robeson County, NC – Lewis and Revels surname associated with the Lumbee
  • Chatham County, NC – Lynn ancestor’s earliest known location
  • Greene County, NC – enslaved Blount ancestor’s EKA in 1849

The genesis of Mr. Blount’s enslaved ancestor is unclear. Fortunately, he took a Big Y-700 test.

Mr. Blount’s only Big-Y match is to a man from the United Arab Emirates (UAE), but the haplogroup history includes Thailand, which is the likely source of both his and his UAE matches’ ancestors at some point in time. Their common ancestor was in Thailand in 336 CE, almost 1700 years ago.

All surrounding branches of haplogroup O on the Time Tree have Asian testers, except for the one UAE gentleman.

The Blount Haplogroup O-FTC77008 does not connect with the common ancestral haplogroup of Lynn and Revels, so these lineages are only related someplace in Oceana prior to O-F265, or more about  30,000 years ago. Their only commonality other than their Asian origins is that they arrived on the East Coast of the Americas.

We know that the Spanish were exploring the Atlantic coastline in the 1500s and were attempting to establish colonies. In 1566, a Spanish expedition reached the Delmarva Peninsula. This spit of land was contested and changed hands several times, belonging variously to the Spanish, Dutch, and British by 1664.

Furthermore, we also know that the ships were utilizing slave labor. One of the Spanish ships wrecked in the waters off North Carolina near Hatteras or Roanoke Island before the Lost Colony was abandoned on Roanoke Island in 1587. The Croatan Indians reported that in memorable history, several men, some of whom were reported to be slaves, had survived the wreck and “disappeared” into the hinterlands – clearly running for their lives.

These men, if they survived, would have been incorporated into the Native population as there were no other settlements at the time. Variations of this scenario may have played out many times.

James Revels’ ancestor could have arrived on any ship, beginning with exploration and colonization in the early 1500s through the mid-1650s.

By the time the chief bound the Indian boy who was given the English name James to Edward Revell, James’s Oceanic paternal ancestor could have been 4, 5 or 6 generations in the past – or could have been his father.

The Accomack was a small tribe, loosely affiliated with the Powhatan Confederacy along the Eastern Shore. By 1700, their population had declined by approximately 90% due to disease. A subgroup, the Gingaskins, intermarried with African Americans living nearby. After Nat Turner’s slave rebellion of 1831, they were expelled from their homelands.

The swamps near Lumberton in Robeson County, NC, became a safe haven for many mixed-race Native, African, and European people. The swamps protected them, and they existed, more or less undisturbed, for decades. Revels and Lewis descendants are both found there.

Many Native Americans were permanently enslaved alongside African people – and within a generation or so, their descendants knew they were Native and African, but lost track of which ancestors descended from which groups. Life was extremely difficult back then. Generations were short, and enslaved people were moved from place to place and sold indiscriminately, severing their family ties entirely, including heritage stories.

Returning to the Discover Time Tree Maps

Wesley Revels has STR matches with several men from Indonesia, China, and the Philippines. It would be very helpful if those men would upgrade to the Big Y-700 so that we can more fully complete the haplogroup O branches of the Time Tree.

The common Revels/Lewis ancestor, accompanied by two descendant men on different genetic branches from the Philippines, was born about 5180 years ago. There is no evidence to suggest Haplogroup O-FT11768 was born anyplace other than in the Philippines.

How did the descendant haplogroups of O-FT45548 (Revels, Lewis, and an unnamed man) and O-F22410 (Lynn) arrive in Virginia or anyplace along the Atlantic seaboard?

Hawaii wasn’t settled until about 1600 years ago. We know Hawaiians integrated with the Pacific Coast Native tribes in the 1800s, but James Revels was in Virginia in 1656..

We know that the Spanish established a mid-1500s trade route between Manila and Acapulco, leaving their genetic signature in western Mexico.

None of these events fit the narrative for the Revels or the Lynn paternal ancestor.

Furthermore, the Revels and Lynn lines do not connect on North American soil, as both descend from the same parent haplogroup, O-FT11768, 5180 years ago in the Philippines. This location and history suggest a connection with the Spanish galleon trade era. The haplogroup formation clearly predates that trade, which means those men were still in the Philippines, not already living on the American continents. Therefore, the descendants of the haplogroup O-FT11768 arrived in Virginia and North Carolina sometime after that haplogroup formation 5100 years ago.

The Lynn ancestor connects with a man from Singapore in 760 CE, or just 1240 years ago. A descendant of haplogroup O-F22410 arrived in North Carolina sometime later.

It does not appear, at least not on the surface, that there is a connection through Madagascar, although we can’t rule that out without additional testers. If the connection is through Madagascar, then their ancestors were likely transported from Indonesia to Madagascar, then as enslaved people from Madagascar to the Atlantic colonies to be sold. However, James Revels was not enslaved. He was clearly Native and bound to a European plantation owner, who did, in fact, free him as agreed and subsequently loaned him money.

Based on the dates involved, and when we know they were in Oceania, an arrival along the west coast, followed by a quick migration across the country to a peninsula of land in the Atlantic, is probably the least likely scenario. There is also no historical or ancient haplogroup O DNA found anyplace between the west and east coasts, nor in the Inuit or Na-Dene speakers. The Navajo, who speak the Na-Dené language, migrated to the Southwest US around 1400 CE, but haplogroup O has not been found among Na-Dené speakers.

It’s a long way from Singapore and the Philippines to Madagascar, so while the coastal migration scenario is not impossible, it’s also not probable, especially given what we know about the Spanish Pacific trade that existed profitably for 250 years.

However, one haplogroup O subgroup arrived in the UAE by some methodology after 336 CE.

It’s entirely possible, indeed probable, that haplogroup O arrived in the Americas for various reasons, on different paths, in different timeframes.

Haplogroup O was found in people in the Americas after colonization had begun. There has been no ancient Haplogroup O DNA discovered, and there’s evidence indicating that these instances of haplogroup O could not have arrived in any of the known Beringia migrations nor the theorized Coastal or Kelp migration. We know the East Coast Cluster is not a result of the West Coast 19th-century migration because James Revels was in court one hundred and fifty years before the Hawaiians were living among the Native people along the Pacific coastline.

There’s nothing to indicate that the Mexican group that likely arrived beginning in the mid-1500s for the next 250 years as a result of the Indonesian trade route migrated to the east coast, or vice versa. That’s also highly unlikely.

The most likely scenario is that Mr. Lynn’s, Mr. Blount’s, and James Revels’ ancestors were brought on trade ships, either as sailors or enslaved men. They may not have stayed, simply visited. They may each have arrived in a completely different scenario, meaning Mr. Blount’s ancestors could have been enslaved arrivals from Madagascar, Mr. Lynn’s from Indonesia, and Mr. Revel’s as a crew member on a Spanish ship. We simply don’t know.

James Revels’ descendants were Native through his mother’s tribe, as confirmed in the 1667 court records. However, the Revels and Lynn lineages weren’t Native as a result of their paternal haplogroup O ancestors crossing Beringia into the Americas with Native American haplogroups Q and C. Instead, the Lynn and Revels migration story is quite different. Their ancestors arrived by ship. The journey was long, perilous, and far more unique than we could have imagined, taking them halfway around the world by water.

Timeline

There’s a lot of information to digest, so I’ve compiled a timeline incorporating both genetic and historical information for easy reference.

  • 30,000 years ago (28,000 BCE) – haplogroup O-F265, common Asian ancestor  of Mr. Blount, the Revels/Lewis group, Mr. Lynn, and an unknown Big-Y tester in the Malagasy group project
  • 12,000-16,000 years ago – Indigenous Americans arrived across now-submerged Beringia
  • 12,000-16,000 years ago – possible Coastal Migration route may have facilitated a secondary source of indigenous arrival along the Pacific coastline of the Americas
  • 4000-7000 years ago – circumpolar migration arrival of Inuit and Na-Dené speakers found in the Arctic polar region and the Navajo in the Southwest who migrated from Alaska/Canada about 1400 CE
  • 5180 years ago (3180 BCE) – haplogroup O-FT11768, the common ancestor of Mr. Lynn and the Revels/Lewis group with many subgroups in the Philippines, Hawaii, Singapore, Brunei, China, Sumatra, and Thailand
  • 2244 years ago (244 BCE) – haplogroup O-CTS716, the common ancestor of Wesley Revels and Mr. Luo from Indonesia
  • The year 336 CE, 1684 years ago – haplogroup O-FTC77008, the common ancestor of Mr. Blount, UAE tester and a man from Thailand
  • 400 CE, 1600 years ago  –  Hawaii populated by Polynesian people
  • 760 CE, 1240 years ago – haplogroup O-F22410, common ancestor of Mr. Lynn with a Singapore man
  • 1492 CE, 528 years ago – Columbus begins his voyages to the “New World,” arriving in the Caribbean
  • By 1504 CE – European fishing began off of Newfoundland
  • 1565 – Spain claimed Guam and the Philippines
  • 1565 – Spanish trade between Manilla and Acapulco begins and continues for 250 years, until 1815, using crews of men from Guam, the Philippines, and enslaved people from the Marianas.
  • 1565 – St. Augustine (Florida) was founded by the Spanish as a base for trade and conquest along the eastern seaboard
  • 1566 – A Spanish expedition reached the Delmarva peninsula intending to establish a colony, but bad weather thwarted that attempt.
  • 1585-1587 – voyages of discovery by the English and the Lost Colony on Roanoke Island, North Carolina
  • 1603 – English first explored the Delmarva Peninsula, home to the Accomac people, now Accomack County, VA, where James Revels’s court record was found in 1667
  • 1607 – Jamestown, Virginia, founded by the English
  • 1608 – Colonists first arrived on the Delmarva Peninsula and allied with Debedeavon, whom they called the “laughing King” of the Accomac people. At that time, the Accomac had 80 warriors. Debedeavon was a close friend to the colonists and saved them from a massacre in 1622. He died in 1657.
  • 1620 – The Mayflower arrived near present-day Provincetown, Massachusetts
  • 1631-1638 – Dutch West India Company established a colony on the Delmarva Peninsula, but after conflicts, it was destroyed by Native Americans in 1638. The Swede’s colony followed, and the region was under Dutch and Swedish control until it shifted to British control in 1664
  • 1656 – Birth of James Revels, confirmed in a 1667 court record stating that he was an Accomack “Indian boy” from “Matomkin,” judged to be age 11, bound to Edward Revell. This location is on the Delmarva Peninsula.
  • 1741 CE –  Haplogroup O-BY60500 formation date that includes all of the Revels and Lewis testers who descend from James Revels born in 1656
  • 1765 – Whalers near Nantucket using crewmen from Hawaii (Sandwich Islands), Tahiti, and the Cape Verde Islands off of Africa
  • 1766 CE – Formation date for haplogroup O-FT45548, child haplogroup of O-BY60500, for some of the Lewis and Revels men who all descend from James Revels born in 1656
  • 1778 – Captain Cook makes contact with Hawaiian people
  • 1787 – The first male arrived in the Pacific Northwest from Hawaii
  • 1811 – Hawaiian seamen begin intermarrying with Native American females along the Pacific shore, eventually expanding their presence from Oregon to Alaska
  • 1839 – John Suter recruits Hawaiian men to travel with him to California
  • 1845 – Hawaiians employed by Fort Vancouver, with some marrying Native American women

Conclusions

It’s without question that James Revels was Native American very early in the settlement of the Delmarva Peninsula, now Accomack County, Virginia, but his common ancestor with Filipino men 5100 years ago precludes his direct paternal ancestor’s presence in the Americas at that time. In other words, his Revel male ancestor did not arrive in the Beringian indigenous migration 12,000-16,000 years ago. His ancestor likely arrived post-contact, based on a combination of both historical and genetic evidence.

Haplogroup O is not found in the Arctic Inuit nor the Na-Dene speakers, precluding a connection with either group, and has never been found in ancient DNA in the Americas.

Haplogroup O in the Revels lineage is most likely connected with the Spanish galleon trade with the Philippines and the early Spanish attempts to colonize the Americas.

The source of Haplogroup O in the Pacific Northwest group is likely found in the recruitment of Hawaiian men in the early/mid-1800s.

The Mexican Haplogroup O group likely originated with the Manilla/Mexico Spanish galleon trade.

The source of the Blount Haplogroup O remains uncertain, other than to say it originated in Thailand thousands of years ago and is also found in the UAE. The common Blount, UAE, and Thailand ancestor’s haplogroup dates to 336 CE, so they were all likely in or near Thailand at that date, about 1687 years ago.

What’s Next?

Science continuously evolves, revealing new details as we learn more, often clarifying or shifting our knowledge. Before the Discover tool provided haplogroup ages based on tests from men around the world, we didn’t have the necessary haplogroup origin and age data to understand the genesis of haplogroup O in the Americas. Now, we do, but there is invariably more to learn.

New evidence is always welcome and builds our knowledge base. Haplogroup O ancient DNA findings would be especially relevant and could further refine what we know, depending on the location, dates of the remains, who they match, and historical context.

Additional Big Y-700 tests of haplogroup O men, especially those with known genealogy or ancestor location, including Madagascar, would be very beneficial and allow the haplogroup formation dates to be further refined.

If you are a male with haplogroup O, please consider upgrading to the Big Y-700 test, here.

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

If you haven’t already subscribed (it’s free,) you can receive an email whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the 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 Book

Genealogy Books

Genealogy Research

East Coast Genetic Genealogy Conference – In Person and Virtual – October 6-8, 2023

There’s a conference focused solely on genetic genealogy, and you’re invited!! Now that’s talking my language!!!

The second annual East Coast Genetic Genealogy Conference (ECGGC) will take place on October 6-8, 2023, at the Maritime Conference Center in Linthicum Heights, Maryland, just outside Baltimore.

This year’s conference is a hybrid affair, with both in-person and virtual speaker sessions and vendor booths.

The in-person conference includes lunch and costs $225, while the virtual conference is $175.

As the name suggests, this conference caters to genetic genealogists. The lineup includes wonderful speakers who I’m sure you’ll recognize, here. I can hardly wait to attend some of these sessions. The great news is that you really don’t have to pick and choose from the more than 40 sessions, because you can view recorded sessions after the conference.

Please note that while my session on Sunday at 11, Wringing Every Drop Out of Mitochondrial DNA, is listed as In-Person, it is not. Due to a change in plans, it’s virtual.

Be sure to check out the DNA Academy on Saturday evening from 6 to 8:30 PM. This event was quite popular last year.

Is there a presentation or a few that you’re particularly looking forward to?

Recorded sessions will be available until December 31st, so even if you can’t join us that weekend, or you’re on the other side of the world and the timing just doesn’t work, you don’t have to miss out. Often, in-person sessions aren’t recorded and available later, but at ECGGC, both in-person and virtual sessions will be recorded so you can watch any session through year-end. Thanks to the fine folks on the ECGGC conference committee for providing this benefit.

You can purchase a ticket, here.

This is a wonderful opportunity, and I hope to see you there.

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

If you haven’t already subscribed (it’s free,) you can receive an email whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the 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 Book

Genealogy Books

Genealogy Research

Reminder – Free Discover Webinar Through September 5th

Wow – has this ever been a week!!! This article should be subtitled, “Never Argue With a Woman Named Idalia.” Trust me, Idalia will be the least popular baby name for 2023.

But first things first.

I want to provide a friendly reminder that the webinar, Y-DNA Discover Tool – What News Can Your Haplogroup Reveal? is free through September 5th at Legacy Family Tree Webinars and will be available in their library for subscribers thereafter.

Discover is a free Y-DNA tool provided by FamilyTreeDNA.

Anyone can use Discover. You don’t need to have taken a Y-DNA test, but the greatest benefit will be realized with Big Y-700 test results. Don’t worry about that now, though, because I explain the differences between tests in the webinar. You can get a lot out of Discover, even if you only know a base-level haplogroup.

Normally, these webinars are live, but those plans were interrupted by Hurricane Idalia.

Idalia developed so quickly – and we really weren’t sure where it was going until just a day or so in advance – or how severe it would be. It was ugly, and as I write this, Idalia is still torturing the east coast.

When I realized the possible impact, and that the probability of having both power and internet were very remote, I contacted Legacy Family Tree Webinars and discussed options.

We really didn’t want to reschedule since more than 2000 people from around the world had signed up for the webinar. We decided that the best option was to record the webinar in advance as a precaution. Then, if possible and Idalia targeted her wrath elsewhere, I would still give it live.

Needless to say, doing anything live wasn’t in the cards on Wednesday. I should add that I am safe and dry with minimal damage – just some branches and small trees down – but others nearby aren’t nearly so fortunate. Flooding was recorded in feet of water, roads are still closed to vehicles, boats rescuing people who didn’t evacuate are zipping down the flooded streets in many places, and there’s just a massive mess. Thousands of people are displaced.

However, as they say, “the show must go on,” and it did. The webinar was presented even though I couldn’t be there for Q&A. Anticipating that possibility, I recorded a lot of detail for you.

I hope I didn’t sound as rattled as I felt, because I was recording in the midst of hurricane prep and the first bands of wind and rain were already lashing the windows. I knew that we were facing a monster storm. That’s very unsettling.. All things considered, I think the webinar went quite well. I was afraid the power would go out while we were recording, but fortunately, it didn’t.

At the end of the webinar, I pulled everything from all of the Discover tools, the Block Tree, and the Group Time Tree together, then added historical migration records along with known, proven family genealogy.

Given that:

  • How did Discover do?
  • Was it useful?
  • Is it accurate?
  • How accurate?
  • What has it done for the Estes paternal line genealogy?
  • What do I know about my Estes lineage that I didn’t know before?
  • What’s the next step?
  • What can Discover do for you?

I really encourage you to tune in and take advantage of this free educational webinar through September 5th, maybe even over the Labor Day weekend.

Please feel free to share this article and information about the webinar with interested groups and organizations!!!

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

If you haven’t already subscribed (it’s free,) you can receive an email whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the 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 Book

Genealogy Books

Genealogy Research

Y-DNA Discover Tool – Free Webinar

You’re invited to join me for a free, live webinar about the Y-DNA Discover tool on Wednesday, August 30th, at 2 PM EDT, courtesy of Legacy Family Tree Webinars.

FamilyTreeDNA‘s Discover tool can be used with any Y-DNA haplogroup. I’ve written about Discover here and the newest feature, Globetrekker, here. 

Y-DNA Discover Tool – What News Can Your Haplogroup Reveal? will be free next Wednesday and for the following seven days. After that, this webinar, along with the rest of Legacy Family Tree’s extensive webinar library is available via an annual subscription of $49.95. I think my new webinar will be webinar number 2042 in their library.

A subscription also provides access to the webinar handouts, the webinar chat logs, and a subscribers-only door prize during each webinar. If you’re interested, you can subscribe here.

What’s In the Discover Webinar?

Discover is an amazing tool, but I think many people are missing ways to use it for genealogy. I’ll cover both the free Discover version and the additional functionality for Big Y testers.

Everyone can use Discover for any Y-DNA haplogroup, no matter the haplogroup source. Of course, the more granular or refined the haplogroup, the more relevant the haplogroup will be to your most recent ancestors. Y-DNA haplogroups are available through the following types of tests:

  • Autosomal at 23andMe, LivingDNA – base or midrange level haplogroup derived from target testing a few Y-DNA locations in an autosomal test. These haplogroups are generally at least a few thousand years old. Think tree branches.
  • Haplogroup estimate when taking the 12, 25, 37, 67, or 111 STR marker Y-DNA tests at FamilyTreeDNA. Think tree branches.
  • The Big-Y DNA test, also at FamilyTreeDNA, provides the most refined and detailed haplogroup. Think twigs and leaves that are very specific to your family at the ends of each larger branch.

After briefly introducing Y-DNA, how it works, and why you care, I’ll be stepping through each Discover feature and function. This includes the Group Time Tree, which isn’t part of Discover but is available through FamilyTreeDNA‘s projects and uses the Discover technology.

  • Haplogroup story – description and overview
  • Country Frequency – where this haplogroup and related haplogroups are found in the world
  • Notable Connections – the famous and infamous, and what that means to you
  • Migration Map –  short story, complete with ancient DNA sites
  • Globetrekker – animated, refined story with lots of detail and several options. Paths your ancestors may have taken to arrive where your line is first found.
  • Ancient Connections – ancient Y-DNA that anchors haplogroups
  • Time Tree – when and where haplogroups were born and how they connect
  • Ancestral Path – every step from you to Y-Adam, when and where that step occurred
  • Suggested Projects – relevant projects for collaboration (and buried hints)
  • Scientific Details –  haplogroup age estimates, age ranges, and your haplogroup’s mutations
  • Group Time Tree – for project members only – the Time Tree complete with all Big-Y testers who’ve opted-in to this project and provided a location, plus earliest known ancestors, displayed in groups
  • What you can do to help yourself

I’ll discuss using the various Discover features to understand what the information means to you, why it’s important, and how to utilize it for your genealogy. I’ll also talk about how to incorporate Block Tree information and projects.

If you’d like to listen and educate yourself, that’s great, but you might want to take this opportunity to think of a male-line brick wall you’d like to work on or learn more about. Don’t we all want to know more about every line – even if we’ve run out of known ancestors and records? Keep your focus line in mind as we apply the tools one-by-one to my Estes lineage, building evidence, during the webinar. Discover helps us peel back the veil of time.

At the end, I’ll provide hints and tips about constructing your plan of attack – how to locate testers and what to do next.

Mark your calendar, and don’t forget to convert the time to where you live. Next Wednesday, August 30, at 2 EDT. See you then!!

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

If you haven’t already subscribed (it’s free,) you can receive an email whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on, and this informational blog free for everyone. Please click on the 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 Book

Genealogy Books

Genealogy Research

Haplogroups: DNA SNPs Are Breadcrumbs – Follow Their Path

Recently a reader asked some great questions.

If Y-DNA is unchanged, then why isn’t the Y-DNA of every man the same today? And if it’s not the same, then how do we know that all men descend from Y-Adam? Are the scientists just guessing?

The scientists aren’t guessing, and the recent scientific innovations behind how this works is pretty amazing, so let’s unravel these questions one at a time.

The first thing we need to understand is how Y-DNA is inherited differently from autosomal DNA, and how it mutates.

First, a reminder that:

  • Y-DNA tests the Y chromosome passed from father to son in every generation, unmixed with any DNA of the mother. This article focuses on Y-DNA.
  • Mitochondrial DNA tests the mitochondria passed from mothers to all of their children, but is only passed on by the females, unmixed with the DNA of the father. This article also pertains to mitochondrial SNPS, but we will cover that more specifically later in another article.
  • Autosomal DNA is passed from both parents to their children. Each child inherits half of each parent’s autosomal DNA.

Let’s look at how this works.

Autosomal vs Y-DNA Inheritance

Click on image to enlarge

Autosomal DNA, shown here with the green (male) and pink (female) images, divides in each generation as it’s passed from the parent to their child. Each child inherits half of each parent’s autosomal DNA, meaning chromosomes 1-22. For this discussion, each descendant shown above is a male and has a Y chromosome.

This means that in the first generation, which would be the great-grandfather, about 700,000 locations of his green autosomal DNA are tested for genealogy purposes.

His female partner (pink) also has about 700,000 locations. During recombination, they each contribute about 350,000 SNPs (Single Nucleotide Polymorphisms) of autosomal DNA to their child. Their offspring then has a total of 700,000 SNPs, 350,000 green and 350,000 pink contributed by each parent.

This process is repeated for each child, whether male or female (with the exception of the X chromosome, which is beyond the scope of this article), but each child does not receive exactly the same half of their parents’ autosomal DNA. Recombination is random.

In the four generations shown above, the green autosomal DNA of generation one, the great-grandfather, has been divided and recombined three times. The original 700,000 locations of great-grandfather’s green DNA has now been whittled down to about 87,500 locations of his green DNA.

Y-DNA in the Same Generation

Looking now at the blue Y-DNA at left, the Y-DNA remains the same in each generation with the exception of one mutation approximately every two or three generations.

As you can see in the chart, in the exact same number of generations, the Y-DNA of each male, which he inherited from his father:

  • Never recombines with any DNA from the mother
  • Never divides and gets smaller in subsequent generations
  • Remains essentially unchanged in each generation

The key word here is “essentially.”

Y-DNA

The Y chromosome consists of about 59 million locations or SNPs of DNA. STR tests, Short Tandem Repeats, which are essentially insertions and deletions, test limited numbers of carefully curated markers selected for the fact that they mutate in a genealogically relevant timeframe. These markers are combined in panels of either 67 or 111 marker tests available for purchase at FamilyTreeDNA today, or historically 12, 25, 37, 67, and 111 marker panels. The STR test was the original Y-DNA test for genealogy and is still used as an introductory test or to see if a male matches a specific line, or not.

From the STR tests, in addition to matching, FamilyTreeDNA can reliably predict a relatively high-level haplogroup, or genetic clan, based on the frequency of the combinations of those marker values in specific STR locations.

SNPs are much more reliable than STRs, which tend to be comparatively unstable, mutating at an unreliable rate, and back mutating, which can be very disconcerting for genealogy. We need reliable consistency to be able to assign a male tester to a specific lineage with confidence. We can, however, find genealogically relevant matches that may be quite important, so I never disregard STR tests or testers. STR tests aren’t relevant for deeper history, nor can they reliably discern a specific lineage within a surname. SNP tests can and do.

The Big Y-700 SNP test gives us that and more, along with the earlier Big Y-500 test which scanned about 30 million locations. The Big Y-700 is a significant improvement; men can upgrade from the Big Y-500 or STR tests.

The Big Y-700 test scans about 50 million Y-DNA locations, known as the gold standard region, for all mutations. It reports 700 or more STR markers for matching, but more importantly, it scans for all SNP mutations in those 50 million locations.

All mutations are confirmed by at least five positive repeat scans and are then assigned a haplogroup name if found in two or more men.

Y-DNA Testing

If Y-DNA remained exactly the same, then the Y-DNA of men today would be entirely indistinguishable from each other – essentially all matching humankind’s first common ancestor. With no changes, Y-DNA would not be useful for genealogy. We need inherited mutations to be able to compare men and determine their level of relatedness to each other.

Fortunately, Y-DNA SNPs do mutate. Y-DNA is never divided or combined, so it stays essentially the same except for occasional mutations which are inherited by the following generations.

Using SNP markers scanned in the Big Y test, one new mutation happens on the average of every two or three generations. Of course, that means that sometimes there are no mutations for a few generations, and sometimes there are two mutations between father and son.

What this does, though, very effectively, is provide a trail of SNP mutations – breadcrumbs essentially – that we can use for matching, AND for tracking our mutations, which equate to ancestors, back in time.

Estes Male Breadcrumb Trail

I’ve tested several Estes men of known lineage, so I’m going to use this line as an example of how mutations act as breadcrumbs, allowing us to track our ancestors back in time and across the globe.

Multiple cousins in my Estes line have taken the Big Y-700 test.

My closest male cousin matches two other men on a unique mutation. That SNP has been named haplogroup R-ZS3700.

We know, based on our genealogy, that this mutation occurred in Virginia and is found in the sons of Moses Estes born in 1711.

How do we know that?

We know that because three of Moses’s descendants have tested and all three of those men have the same mutation, R-ZS3700, and none of the sons of Moses’s brothers have that mutation.

I’ve created a chart to illustrate the Estes pedigree chart, and the haplogroups assigned to those men. So, it’s a DNA pedigree chart too. This is exactly what the Big-Y DNA test does for us.

In the red-bordered block of testers, you can see the three men that all have R-ZS3700 (in red), and all are sons of Moses born in 1711. I have not typed the names of all the men in each generation because, for purposes of this illustration, names aren’t important. However, the concept and the fact that we have been able to connect them genealogically, either before or because of Y-DNA testing, is crucial.

Directly above Moses born in 1711, you can see his father Abraham born in 1647, along with Moses’ brothers at right and left; John, Richard, Sylvester, and Elisha whose descendants have taken the Big Y-700 test. Moses’s brothers’ descendants all have haplogroup R-BY490 (in blue), but NOT R-ZS3700. That tells us that the mutation responsible for R-ZS3700 happened between Abraham born in 1647, and Moses born in 1711. Otherwise, Moses’s brothers would have the mutation if his father had the mutation.

Moses’s descendants also have R-BY490, but it’s NOT the last SNP or haplogroup in their lineage. For Moses’s descendants, R-ZS3700 occurred after R-BY490.

You can see haplogroup R-BY490 boxed in blue.

We know that Moses and his father, Abraham, both have haplogroup R-BY490 because all of Abraham’s sons have this haplogroup. Additionally, we know that Abraham’s father, Silvester also had haplogroup R-BY490.

How do we know that?

Abraham’s brother, Richard’s descendant, tested and he has haplogroup R-BY490.

However, Silvester’s father, Robert born in 1555 did NOT have R-BY490, so it formed between him and his son, Silvester.

How do we know that?

Robert’s other son, Robert born in 1603 has a descendant who tested and has haplogroup R-BY482, but does NOT have R-BY490 or R-ZS3700.

All of the other Eates testers also have R-BY482, blocked in green, in addition to R-BY490, so we know that the mutation of R-BY490 developed between Robert born in 1555 and his son, Silvester born in 1600, because his other son’s descendant does not have it.

Looking at only the descent of the haplogroups, in order, we have

  • R-BY482 (green) found in Robert born in 1555 and all of his descendants.
  • R-BY490 (blue) found in Silvester born in 1600 and all of his descendants, but not his brother
  • R-ZS3700 (red) found in Moses born in 1711 and all of his descendants, but not his brothers

If we had Estes men who descend from the two additional documented generations upstream of Robert born in 1555, we might discover when R-BY482 occurred, but to date, we don’t have any additional testers from those lines.

Now that we understand the genesis of these three haplogroups in the Estes lineage, what else can we discover through our haplogroup breadcrumbs?

The Discover Reports

By entering the haplogroup in the Discover tool, either on the public page, here, or clicking on Discover on your personal page at FamilyTreeDNA if you’ve taken the Big-Y test, you will see several reports for your haplogroup.

I strongly suggest reviewing each category, because they cumulatively act as chapters to the book of your haplogroup story, but we’re going to skip directly to the breadcrumbs, which is called the Ancestral Path.

The Ancestral Path begins with your haplogroup in Line 1 then lists the first upstream or parent haplogroup in Line 2. In this case, the haplogroup I entered is R-ZS3700.

You can see the estimated age of the haplogroup, meaning when it formed, at about 1700 CE. Moses Estes who was born in 1711 is the first Estes man to carry haplogroup R-ZS3700, so that’s extremely close.

Line 2, R-BY490 occurred or was born about 1650, and we know that it actually occurred between Robert and Silvester born in 1600, so that’s close too.

Scanning down to Line 3, R-BY482 is estimated to have occurred about 1500 CE, and we know for sure it had occurred by 1555 when Robert was born.

We see the parent haplogroup of R-BY487 on Line 4, dating from about 750 CE. Of course, if more men test, it’s possible that more haplogroups will emerge between BY482 and BY487, forming a new branch. Given the time involved, those men wouldn’t be expected to carry the Estes surname, as surnames hadn’t yet been adopted in that timeframe.

Moving down to Line 9, we see R-ZP18 from 2250 BCE, or about 4250 years ago. Looking at the right column, there’s one ancient sample with that haplogroup. The location of ancient samples anchors haplogroups definitively in a particular location at a specific time.

Haplogroup by haplogroup, step by step, we can follow the breadcrumbs back in time to Y-Adam, the first homo sapiens male known to have descendants today, meaning he’s the MRCA, or most recent common ancestor for all men.

Neanderthals and Denisovans follow, but their Y-DNA is only available through ancient samples. They have no known direct male survivors, but someday, maybe someone will test and their Y-DNA will be found to descend from Neanderthals or Denisovans.

Now that we know when those haplogroups occurred, how did our ancestors get from Africa 232,000 years ago to Kent, England, in the 1400s? What path did they take?

The new Globetrekker tool answers that question.

The Breadcrumb Trail

In Globetrekker, each haplogroup’s location is placed by a combination of testers’ results, their identified earliest known ancestor (EKA) country and location, combined with ancient samples, climatic factors like glaciers and sea levels, and geographic features. You can read about Globetrekker here and here.

To view the Globetrekker tool, you must sign it to an account that has taken the Big Y test. It’s a tool exclusively provided for Big-Y testers.

You can click at the bottom of your Globetrekker map to play the animated video.

Beginning in Africa, our ancestors began their journey with Y-Adam, then migrated through the Near East, South Asia, East Asia, then west through central Asia into Europe. The Estes ancestors crossed the English Channel and migrated around what is now England before settling in Deal, on the east coast.

Clicking on any haplogroup provides a description of that haplogroup and how it was placed in that location.

Enabling the option for ancient DNA shows those locations as well, near the haplogroups they represent when the animation is playing.

Clicking on the shovel icon explains about that particular ancient DNA sample, what is known, and how it relates to the haplogroup it’s connected to by a dotted line on the map.

Pretty cool, huh!!

End to End

As you can see from this example, Big Y results are an end-to-end tool.

We can use the Big Y-700 haplogroups very successfully for recent genealogy – assigning testers to specific lines in a genealogy timeframe. Some haplogroups are so specific that, without additional information, we can place a man in his exact generation, or within a generation or two.

Not shown in my Estes pedigree chart is an adoptee with a different surname, of course. We know that he descends from Moses’s line because he carries haplogroup R-ZS3700, but we are still working on the more recent generations using autosomal DNA to connect him accurately.  If more of Moses’s descendants tested, we could probably place him very specifically. Without the Big Y-700 test, he wouldn’t know his biological surname or that he descends from Moses. That’s a HUGE breakthrough for him.

There’s more about the Estes line to learn, however.

If our Estes cousins tested their brothers, uncles or other Estes males in their line, they would likely receive a more refined haplogroup that’s relevant only to that line.

Using Big-Y test results, we can place men within a couple of generations and identify a common ancestor, even when all men within a haplogroup don’t know their genealogical lineage. Using those same test results, we can follow the breadcrumbs all 50 steps back in time more than 230,000 years to Y-Adam.

End to end, the Big-Y test coupled with breadcrumbs in Discover, Globetrekker, and other amazing tools is absolutely the most informative and powerful test available to male testers for their paternal line genealogy.

These amazing innovations tracking more than 50,000 haplogroups across the globe answer the original questions about how we know.

The more people who take or upgrade to the Big Y-700 test, the more haplogroup branches will be added, and the more refined the breadcrumbs, ages, and maps will become. In other words, there’s still more to learn.

Test if you haven’t, and check back often for new matches and breadcrumbs, aka updates.

_____________________________________________________________

Follow DNAexplain on Facebook, here.

Share the Love!

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

If you haven’t already subscribed (it’s free,) you can receive an email whenever I publish by clicking the “follow” button on the main blog page, here.

You Can Help Keep This Blog Free

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the 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 Book

 

Genealogy Books

  • com – Lots of wonderful genealogy research books
  • American Ancestors – Wonderful selection of genealogy books

Genealogy Research