Re:Facebook and Speech
by throwaway381728 on Friday October 18, 2019 @01:18PM
(#21293205)
The problem with open API access is preventing Cambridge Analytica like abuse.
[ Parent
| on HN ]
Except Cambridge Analytica occurred in a closed-access scenario. It's a problem either way.
CA scraped Facebook APIs. It's only "closed" in the sense that you needed an account and token to access the open API.
Exactly my point. Facebook's APIs were not designed for CA's style of scraping, but they took advantage of it anyway. You can try limiting access to data but infiltrators will find a way to abuse it anyway.
And that's also my point - you don't accidentally leave an API open. It was purposefully built this way. What CA did with Facebooks API was by design.
> CA scraped Facebook APIs
what does it mean to scrape an API. I usually hear that word for html website scraping.
Normal API use is to read information about the people directly interacting with a post or an app, for the purpose of facilitating that interaction.
Cambridge Analytica used posts to get API access to all users (and friends-of-friends) who interacted with those posts, in order to incrementally build a copy of the complete social graph. The process is similar to scraping.
This is still an ACL issue - that Facebook allowed CA to pull data they weren’t authorized for doesn’t mean making API access is a bad idea.
It increases the attack surface but publicly to everyone.
If I share some information with a friend of a friend, should that information be viewable by an app that the friend of a friend activated? For Cambridge Analytica, the answer was "yes", so Cambridge Analytica was able to scrape a bunch of stuff.
If we make the answer "no", then it won't be possible to build alternate UIs, because the Facebook UI will be able to show my friend of a friend my information, but an alternate UI won't be able to do so.