4 ms·
> We should be asking why even an authorized API that can't stop you from copying the data doesn't count as a systemetized data breach. Is your argument that n
by traek 9y ago
> We should be asking why even an authorized API that can't stop you from copying the data doesn't count as a systemetized data breach.
Is your argument that no company should offer any developer APIs at all? It's impossible to stop apps from storing data that they have access to, given malicious intent.
This is like saying that the existence of the Google Calendar API is a "systemetized data breach" because an app could copy data from it once authorized by a user.
- heckanoobs 9y agoI'm not sure how we draw the line. But it should at least feel ethically itchy if ppl can use data you collected to statistically infer things normally considered private information. This puts Google on the wrong side of the line, wherever it is, next to other big offenders - fb, twitter, linkedin. To waffle less, I would absolutely be very cautious with who you give access to your gcal. You can tell a lot about a person knowing their schedule, who they meet with, where they meet, when they fly, etc. Lots on a calendar
- blablabla123 9y agoIt's one thing to use the friend graph to show in your app who else uses it. That's pretty legit. The other use case is to store it to some database and keep it there. FB provides since ~10 years widgets for showing who else is liking xy. I know these Social Widgets are not so customizable and thus not pretty enough to match some custom design but at least they provide some safety nets. Maybe Facebook could just provide more Social Widgets/CSS customizability instead of letting people write their own "Facebook Extensions".