Not only that, but there seems to be a strong belief among certain people that everyone in England before about 1600 was titled and/or descended from royalty, which is probably a consequence of there being more surviving records for the "posh" than for ordinary folk. An awful lot of people have been retrospectively knighted by some modern researchers!Yes there seems to be some tree owners who think they're related to Royalty!
ome people can be very persistent in their mistaken ideas, though, usually when they’ve found a titled family with the same surname elsewhere in England, and are unwilling to let go of their imagined link to these titled families.
It depends what a profile is. Ancestry has over 100 million trees. If a profile is an individual, then Wikitree is far closer to LostCousins than Ancestry.They've just emailed me to say: There are now 36 million profiles on our shared tree. Thank you for helping us reach another milestone! Must be closing on Ancestry?
As far as I can tell, a profile is an individual within the collaborative tree, so (using your figures) a long way short of Ancestry.It depends what a profile is
You don't need to have a tree. let alone any records attached to your tree, to find DNA matches. DNA matches are based entirely on DNA.Obviously he should have got it right, but I have lots of 1939 records on my private tree and thought that was necessary for finding DNA matches.
But they are NOT his relatives, not even distant relatives - if they were, he would have been able to take my tree back more than three generations, and there would be some overlap with his own tree.Referring to Peter’s post #29, anyone can legitimately add any of their relatives (however distant) to any online tree, the only restriction usually being that living people must be kept private.
Absolutely, they are only hints, and should be checked like any other hints.Although ancestry will suggest how a DNA match links into my tree, I like to check the record myself.
Sorry, since your earlier post was an image, it wasn’t clear you were the writer. I guess it may be like Findagrave in that respect - people just add whatever records they come across (legitimately or otherwise) regardless of whether they are related or not. I don’t know if Wikitree contributors likewise get rated according to how many profiles they add.But they are NOT his relatives, not even distant relatives - if they were, he would have been able to take my tree back more than three generations, and there would be some overlap with his own tree.
I understand all of this, however my difficulty is that I have learned, or confirmed, via DNA that some of my recent 'direct ancestors' were not genetically related to me at all. I do know who my actual genetic direct ancestors were. If I were to have a public tree with 'direct ancestors' it would either contain some people that I know I am not genetically related to or it would potentially deeply upset some of my living relatives who are not aware that we are not genetically related. I have good reasons for wanting to keep this information private. I know that I'm not alone in this, so I wouldn't overlook someone with a private tree if they were a fairly close match. I'd try to work out who they might be and often I can do that.When Ancestry search for Common Ancestors and ThruLines hints they look at ALL searchable trees, private or public, which is why I often get a Common Ancestors connection with someone who only has 3 or 4 people in their tree. I doubt it makes any difference to Ancestry whether you connect your complete tree to your DNA results or do what I have done. My focus is on making life easier for my cousins....
The disadvantage of connecting a private tree to your DNA results is that your cousins cannot see your tree. They may discover that you have this or that ancestral surname in your tree, but they won't be able to find where those ancestors came from except by trial-and-error, which can be tedious, and can give erratic results. Having limited time I tend to ignore people with private trees unless Ancestry has found a Common Ancestor - there are plenty of other matches to work with.
What your cousins really need to know is who your ancestors were and where they came from: attaching a direct ancestors-only public tree to your results achieves that. With any public tree there is a risk that people who are not cousins will copy the information, but if I take my own tree as an example, my direct ancestors tree is less than one-twentieth the size of my main tree, so that eliminates at least 95% of the copying that might otherwise have occurred.
What a public direct ancestors-only tree won't do is compromise the privacy of your extended family. Even though Ancestry don't show information for living people the ready availability of BMD indexes for England & Wales makes it easy for others to figure out the hidden names - I do this all the time with my DNA matches so that I can add them to my tree without asking them for the information.
You do have good reasons for keeping the information private, and I wouldn't suggest that you do otherwise.I understand all of this, however my difficulty is that I have learned, or confirmed, via DNA that some of my recent 'direct ancestors' were not genetically related to me at all. I do know who my actual genetic direct ancestors were. If I were to have a public tree with 'direct ancestors' it would either contain some people that I know I am not genetically related to or it would potentially deeply upset some of my living relatives who are not aware that we are not genetically related. I have good reasons for wanting to keep this information private.
Most people are not in your position, so they ignore matches who have private trees - it requires 10 times as much effort, with no guarantee of learning anything useful.I know that I'm not alone in this, so I wouldn't overlook someone with a private tree if they were a fairly close match. I'd try to work out who they might be and often I can do that.