Questions I won't get answers to, but about which I'm curious anyway: 1. How many end-users are affected? 2. How many devs are affected? 3. What is the annua

Questions I won't get answers to, but about which I'm curious anyway: 1. How many end-users are affected? 2. How many devs are affected? 3. What is the annual transaction volume that is affected? Depending on the magnitude of the answers to these questions, I can see turning this API off being either a good thing or a bad thing. If hundreds of users are affected, well. Sad, but sometimes unpopular things get turned off. If hundreds of thousands of users are affected, this is an eyebrow-raising decision. Developers are also important, but less so than users. It would be nice to keep the lights on just to let people tinker, but that same openness creates security risks and costs money. Many on this site praise Apple when they make restrictive decisions that harm devs, as long as those decisions are justified in terms of end-user privacy and security. I think the transaction volume question gets at the heart of the issue, at least for me. If there is a lot of economic activity here, that's a signal that user needs might not be accounted for in this decision, or at least are not its primary driver. On the other hand, if only $1M or $2M per year is changing hands in the affected part of the ecosystem, well . . . again, nothing lasts forever.