Which makes me really sad. It seems like the potential for abuse is significantly lower if you move the exports features out of the general directory and into LCR. Right now there is no way to download a simple CSV of the members of my quorum. It seems like the benefit/cost ratio is pretty high for that one.
It is actually possible to create a simple csv. What I did is to get the membership pdf report and use Regex to extract the data. I believe I'm not breaking any policy because this process is similar to as using a paper and a pencil to copy the names
to a piece of paper. Instead of that tedious process, I use the computer to do the "copy" (using regex) And, only names are being extracted which is what the current LDS app lets you do, copy a list of names.
Interesting. So why detail them on the public Wiki in the first place? It seems like if it were for internal use only, it would have been documented via internal means. I hate to even bring it up, lest it get taken away. "... but from him that hath not shall be taken away even that which he hath." (Matthew 25:29)
I agree with this. The public site http://tech.lds.org/wiki/LDS_Tools_Web_Services
should be only accessible to anyone who is contributing to Church approved apps and not the rest. I'm not contributing to any church-approved apps so this site should be restricted to me. Many LDS developers will encounter this same issue and spend time asking the same questions in tech.lds.org. Because, I too was confused and went on requesting JSON data through the API.