This is the most popular online genealogy magazine in the world, as measured by Alexa.
From the Ancestry.com list of recent new and/or updated additions at https://www.ancestry.com/cs/recent-collections
|
11/6/2019
|
|
|
11/6/2019
|
|
|
11/6/2019
|
|
|
11/6/2019
|
|
|
11/5/2019
|
|
|
11/1/2019
|
|
|
11/1/2019
|
|
|
11/1/2019
|
|
|
11/1/2019
|
|
|
10/31/2019
|
|
|
10/31/2019
|
|
|
10/31/2019
|
|
|
10/29/2019
|
|
|
10/22/2019
|
|
Dick Eastman, author
Dick Eastman has been writing this genealogy newsletter for 23 years.
He has been involved in genealogy for more than 35 years. He has worked in the computer industry for more than 50 years in hardware, software, and managerial positions. By the early 1970s, Dick was already using a mainframe computer to enter his family data on punch cards. He built his first home computer in 1980.
This newsletter is sponsored by MyHeritage.
Dick Eastman is adamant that he will never write content influenced by or paid for by an advertiser. All opinions expressed here are those of Dick Eastman and him alone, unless clearly stated otherwise.
One Comment
I found your site on 11/16 when I did a Google search using the words ancestry.com recent updates. I was looking for information about why Ancestry no longer allows the ; character in Event Descriptions. It looks to me like the change happened about 11/12 or 11/13.
Are there other “improvements” that Ancestry has made to Event Descriptions? And why does Ancestry keep breaking things that don’t need fixing?
Thanks for whatever you might find out.
LikeLike