FamilySearch account disabled

[ghost]

When running getmyancestors with ascent value of 6 and descent value of 7, my account was disabled, apparently for causing issues with the FamilySearch site.

Here are the options I used,

./getmyancestors.py -a 6 -d 7 -m -u -p -i -o output.ged

[Linekio]

Have you received a mail from FamilySearch about that? I never had this issue, including with a larger number of generations. Moreover, it is not theorically possible for getmyancestors to cause problems with FamilySearch since it only read (not write).

[ghost]

Indeed, received email notice from FamilySearch that my account had been disabled. I can forward/share it if you want.

[Linekio]

Yes, here's my email it if you don't want to share it in public : benoitfontaine.ba@gmail.com

[jason-costello]

Maybe it has something to do with the following note they posted at https://www.familysearch.org/developers/docs/guides/app-approval?

As of June 27, 2017, FamilySearch is suspending the approval of new applications that provide functionality for the scanning, capturing or reporting (or any combination of the three) of ordinance information, including those that are or may be available to take to the temple. As we evaluate the impact of these types of applications on the FamilySearch systems and the end-user experience; this suspension will remain in effect until further notice. Solutions that request limited read-access privileges may be considered based upon need and functionality.

[ghost]

Yes but in my case, I don't have an LDS account.. So in this case, no temple ordinance information was scanned / captured.

On Mon, Aug 26, 2019 at 9:16 AM Jason Costello notifications@github.com wrote:

Maybe it has something to do with the following note they posted at https://www.familysearch.org/developers/docs/guides/app-approval?

As of June 27, 2017, FamilySearch is suspending the approval of new applications that provide functionality for the scanning, capturing or reporting (or any combination of the three) of ordinance information, including those that are or may be available to take to the temple. As we evaluate the impact of these types of applications on the FamilySearch systems and the end-user experience; this suspension will remain in effect until further notice. Solutions that request limited read-access privileges may be considered based upon need and functionality.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Linekio/getmyancestors/issues/21?email_source=notifications&email_token=ADJRTLZPF7XXSGERCL4D6ILQGPXVFA5CNFSM4IIWRUOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5EV3XI#issuecomment-524901853, or mute the thread https://github.com/notifications/unsubscribe-auth/ADJRTL7NTEVHZW6EX5UABCTQGPXVFANCNFSM4IIWRUOA .

[jason-costello]

I’ll provide an update on my experience with this as I’m running an export for 30 generations.

jc

On Aug 26, 2019, at 10:54 AM, mhs54321 notifications@github.com<mailto:notifications@github.com> wrote:

Yes but in my case, I don't have an LDS account.. So in this case, no temple ordinance information was scanned / captured.

On Mon, Aug 26, 2019 at 9:16 AM Jason Costello notifications@github.com<mailto:notifications@github.com> wrote:

Maybe it has something to do with the following note they posted at https://www.familysearch.org/developers/docs/guides/app-approval?

As of June 27, 2017, FamilySearch is suspending the approval of new applications that provide functionality for the scanning, capturing or reporting (or any combination of the three) of ordinance information, including those that are or may be available to take to the temple. As we evaluate the impact of these types of applications on the FamilySearch systems and the end-user experience; this suspension will remain in effect until further notice. Solutions that request limited read-access privileges may be considered based upon need and functionality.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Linekio/getmyancestors/issues/21?email_source=notifications&email_token=ADJRTLZPF7XXSGERCL4D6ILQGPXVFA5CNFSM4IIWRUOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5EV3XI#issuecomment-524901853, or mute the thread https://github.com/notifications/unsubscribe-auth/ADJRTL7NTEVHZW6EX5UABCTQGPXVFANCNFSM4IIWRUOA .

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/Linekio/getmyancestors/issues/21?email_source=notifications&email_token=ABXVPCFITMLTBCECN5WOI33QGP4CJA5CNFSM4IIWRUOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5EZO4A#issuecomment-524916592, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABXVPCHPPS7SKZMRLY7TB4DQGP4CJANCNFSM4IIWRUOA.

[Linekio]

@mhs54321 has your account been reactivated?

I received this answer from FamilySearch 3 days ago:

The simple answer is that there is nothing wrong with what the script is doing. The problem is that people using it are not throttling their use so they are hitting us as hard as they can with the equipment they have. In some cases this generates so much traffic that it overwhelms the system and makes the system slow or unresponsive to all our users. We are working on some throttling on our side to prevent this from happening but it is not in place yet. If a user generates too much traffic we have no choice but to disable their account for now.

_

[ghost]

Not yet. Maybe there will be an answer from them soon?

[ghost]

An update.. My account has been unlocked. All is well

[Linekio]

Ok so I close this thread