Duplicate Merging as a Service
"The FamilySearch shared tree uniquely strives to have just one public profile for every deceased person who has ever lived."
I love this principle and its implementation! However, duplicates in the World Tree abound. I was wondering if it is possible to review and merge possible duplicates as a service to the World Tree? I have often wondered what happens when ordinances are performed twice or even thrice for duplicates; or when they are performed on profiles who are really two different people merged in one (I've seen it happen! in fact I have been defending one profile in particular for long...).
I was also wondering separately, if anyone knows, what programming language would be best to write in for using the API and making programs to help with research? To my understanding, JSON requests are used to fetch data from the tree. Thank you for your time in responding!