Geni discussions update: fork fixes some burning issues, redesigned MH still not working

[nlof]

To sum up the latest discussions on Geni (starting from here):

1. @pquenee Pierre's fork V4.11.3.934 fixes the "Json" errors which prevent the current main branch V4.11.3.1 from simultaneously copying multiple generations on Ancestry.
2. Pierre's fork also fixes (for the most part) on all sites the copied profiles history, the lack of which makes the current main branch version very difficult to use. The older Firefox version V4.10.29 was also saving that copied profiles history (and was preferrable to the newest branch here for Chrome on all other sites except Ancestry where the old Firefox version doesn't work at all).

Remaining issues:

1. the slow motion of Ancestry tree reading since the new Ancestry fix was implemented here Ancestry stopped working #121
2. the current version still doesn't work at all on the new redesigned MyHeritage pages from nearly a year ago MyHeritage Redesign - need to adjust code #110 Fix MyHeritage with new design #115 .
   Thankfully it still works on MH search results and Smart Matches which preserve the old design for now.
3. There are some remaining smaller reported bugs in that Geni discussion thread.

Thanks all for continuing to develop this very useful tool.

[GuyKh]

Just to reference MyHeritage issue (2) - the main problem there is that the link to the siblings/children/parents are hidden behind React onClick() actions (and not accessible by pure html) - I think the approach here would be one of two:

1. Don't create relatives (at all)
2. Create relatives with minimum information (Name + Year), without links to their profiles (which means also that traversing the family tree would become complicated.

BTW. @eljeffeg - I suggest for you to enable Discussion in this GitHub repo (through Settings) - as this is a discussion, not an issue.

[eljeffeg]

@GuyKh thanks, I've turned on discussions.