2 ms·
“How on earth does Facebook justify offering deep API access on users who have literally disabled API access to their data?” Here how it seems really non-crazy
by prepend 8y ago
“How on earth does Facebook justify offering deep API access on users who have literally disabled API access to their data?”
Here how it seems really non-crazy to me as a programmer. Let’s say I make phone with a Linux OS. I want to make an app to let users check Facebook on my weird OS. I ask Facebook, they say no. I then build an app to call their API and let users do stuff.
All my app does is call the API and show it to the user. In order for the app to function it has to use private data. But the data are not retained or analyzed, just used to operate the app.
This is how all 3rd party apps work. The APIs were not for the general public, but only to trusted third parties. The alternative is that only Facebook can build and show apps.
So this is pretty much how APIs have worked forever and why you only install apps and log into apps you trust.
It would be like complaining that Adobe Reader can read private files from your laptop via Windows/Mac APIs. Of course it can, this is good. It’s bad of Adobe were to misuse the data.
- pmontra 8y agoPrivate means that I (the user of my own FB client) can see my private data. That's obvious. What must not happen is that I can also see data that my friends, or their friends, marked as private. This doesn't happen in the official FB client and must not happen with any API.
- prepend 8y agoAnd it didn’t happen with FB’s API. Your friends could see their private data. You could see yours. The apps were not able to show your private data to friends and vice versa without breaking their contract with FB. It would be like being concerned because both you friends both use Chrome to access your individual, private bank accounts. Google accesses your private information, with your permission, to display data on your screen. It’s only bad if they misuse that data.