4 ms·
What kind of safeguards would you introduce? At the very start of Facebook platform the API would anonymize the user's email address, the app would get an app-
by prostoalex 9y ago
What kind of safeguards would you introduce?
At the very start of Facebook platform the API would anonymize the user's email address, the app would get an app-specific hash, e.g. abcdefg-app123456@facebook.net It was a working email address with Facebook handling the forwarding.
This proved futile as the very first thing that apps then did was to ask users for their real email address.
- bobthepanda 9y agoThen make "no requests for users email" part of the terms of using the API?
- asah 9y agoWhich they flagrantly violated...
- prostoalex 9y agoBut there are many legitimate use cases of sharing email addresses. Just scratching the surface, * someone used Facebook Connect to login to NYTimes Web site, curious about their Food & Recipes newsletter, wants to sign up * someone logging into e-commerce shop through Facebook Connect, making a purchase and then deciding that yes, they would like to track and manage their order on the retailer's Web site, and they will even sign up for an account with retailer to do that
- bobthepanda 9y agoWhich is fine. But most apps that I remember of this type (back when I used Facebook apps) would ask you for it on landing. Nothing ever has to be black-and-white.
- MertsA 9y agoNeither one of those use cases would necessitate using the user's real email address instead of the forwarding address that Facebook provided.
- rhizome 9y agoSure, and maybe they'll put it right next to the "you're not allowed to save any data" clause.
- bobthepanda 9y agoOne is fairly trivial to prove compared to the other.
- ncallaway 9y agoOne is much easier to inspect and verify than the other. There's really no way to check if someone has made a copy of data if you've given them that data. It's not that hard to check if an application prompts a user for an email address.
- danso 9y agoThey could aggressively pursue enforcement and punitive measures. It's not about preventing everything that could possibly go awry, but making it well-known in the developer community that Facebook/Platform has no problem shutting you down if you egregiously break the rules.
- prostoalex 9y agoI think that's sorta kinda was happening with > we immediately banned Kogan's app from our platform, and demanded that Kogan and Cambridge Analytica formally certify that they had deleted all improperly acquired data. They provided these certifications. To generalize the issue, if you were in charge of APIs at some company A and some company B (not necessarily located in your jurisdiction and not necessarily subject to the same legislative framework as you) told you they used to have the data, but deleted it since then, what additional measures would you recommend company A pursue?
- danso 9y agoIn that situation, I guess there's not much power Company A has with regards with Company B, right? Unless Company B is worried that they'll have a future relationship and thus will be willing to submit some kind of audit. Zuck's announcement seems to have a decent outline -- start with investigating apps with access to large amounts of data, audit apps with strange behavior. But after a year, after the CA (and other) controversies are forgotten, what I was thinking was that FB should be doing regular, random audits/investigations, and publicize the punishment. I don't mean identifiable shaming, e.g. "Last week, we banned Jane Smith and her Flappy Farm app for misusing the data of 3,000+ users". But maybe weekly/monthly tallies of apps that were shut down or sanctioned, and a breakdown of the reasons why, and users affected, etc. Every once in awhile, an app maker might post a "We Fucked Up" article on HN, which helps even more in reminding people of TOS.
- deleted 9y ago[deleted]
- ilkan 9y ago
- hendzen 9y agoTo really fix this, Facebook will have to stop allowing 3rd party developers direct access to user data. Basically, FB should introduce an App-Engine like platform where the backend of any 3rd-party application that uses FB data has to run on FB-owned servers. Developers of these applications would then ship their code to FB (similar to Heroku) and run in a sandboxed environment where they are not allowed to take data out at all. That way FB can audit how the data is being used at anytime and kick out people who are out of compliance with their terms. If a user deletes their FB account, now all their data could be deleted from any 3rd party applications automatically. This is basically similar to the way the government handles classified data.
- prostoalex 9y ago> the backend of any 3rd-party application that uses FB data has to run on FB-owned servers Would that work for mobile apps?
- hendzen 9y agoThe backend of the mobile app would run on FB servers.
- prostoalex 9y agoMost apps that do "Login with Facebook" also support "Login with Google" and sometimes "Login with LinkedIn". The backend ownership issue becomes a bit more complicated. This is even before we get into trust issues most developers would have with Facebook having access to their user data.
- hendzen 9y agoThe portion of the app that deals with FB data would be hosted at FB, the portion of the app that deals with Google would be hosted at Google, etc. And this is only a problem for applications that pull user data from FB itself, if it was merely using FB for authorization but wasn't actually using any FB profile data, photos, friend lists, etc, than it could all be hosted on a 3rd party server.
- pishpash 9y agoHow about allowing pseudonyms for a start, like the original Internet before FB corrupted it?
- JumpCrisscross 9y ago> What kind of safeguards would you introduce? How about the ones they agreed to with the FTC in 2011 [1][2]? [1] https://www.ftc.gov/sites/default/files/documents/cases/2011/11/111129facebookagree.pdf https://www.ftc.gov/sites/default/files/documents/cases/2011... [2] https://www.ftc.gov/news-events/press-releases/2011/11/facebook-settles-ftc-charges-it-deceived-consumers-failing-keep https://www.ftc.gov/news-events/press-releases/2011/11/faceb...
- debt 9y ago"What kind of safeguards would you introduce?" I think the only sane response would be to shut down the developer program. I doubt it contributes much to the FB bottomline and it's clearly something FB doesn't care much about given the breadth of this scandal.
- bandrami 9y agoThat's true now. A decade ago, being a development platform was their main goal.