5 ms·
Saying "unintentionally" here is like saying you unintentionally stole someone's TV when they gave you their key to walk their dog. It takes extra work to uplo
by smt88 8y ago
Saying "unintentionally" here is like saying you unintentionally stole someone's TV when they gave you their key to walk their dog.
It takes extra work to upload those contacts, which means several managers and developers decided to do it and then spent time implementing it.
For the FB employees reading this: what is your tipping point? Would you say no to that assignment?
- pixl97 8y ago>what is your tipping point? Would you say no to that assignment? When FB stops giving them a check. At least that has been my experience watching programmers at other companies. Unless ethically bound by regulation and law, few people seem to have ethics.
- swebs 8y ago>few people seem to have ethics Or maybe their set of ethics simply differs from yours. It is very subjective after all
- devnonymous 8y ago> It is very subjective after all Methinks that was what the OP was asking -- what is the tipping point ? Having differing ethics is fine but one can't just lean on that as a crutch when one has none.
- matz1 8y agoWhat tipping point? Maybe the engineer themselves who recommends the practice. Everyone have ethics but might be differ than you. As long as the practice meet their goal, from their perspective it works.
- dwighttk 8y agoI just tripped and a giant laser melted all the gold in Ft Knox which drained down a pipe into a storage container under my backyard.
- glitchc 8y agoGood luck selling any of it.
- jayawayjayyay 8y agoFrom the article it sounds like there was a prompt for permission that got removed: > Facebook told Gizmodo via email that in May 2016 it made a revision to the registration process, which originally asked the affected users for permission to upload contact lists. That change removed the opt-in prompt, though the company did not realize the underlying functionality was still operating in some cases. It doesn't take a conspiracy to understand how a bug like that could happen.
- sildur 8y agoWe are talking about Facebook here.
- bluntfang 8y agoFacebook is a multi-billion dollar company. This is gross negligence if they didn't spend time to QA this.
- Phobophobia 8y agoJust to be devil's advocate: Google is notorious for having separate siloed teams that do not share efficiencies or updates (eg. Hangouts and other messengers). A company like Google and Facebook don't have a good excuse, but we shouldn't be surprised.
- jayawayjayyay 8y agoDoing QA at large tech companies is never that simple. You have lots of teams that share code. Imagine a scenario where Team A uses code written by Team B which uses code written by Team C. Team C makes a change to their code that breaks Team B's code but only for the way Team A uses it.
- yardie 8y agoFor the people in the back, "Facebook is a multi-billion dollar company." They have 30,000 employees. They could spend the money to do better QA. But it's cheaper to let your end-users do it for free.
- maxxxxx 8y ago“For the FB employees reading this: what is your tipping point? Would you say no to that assignment?” There is a good chance that they didn’t know how their work would eventually be used. That’s the problem with big companies. Most people are far away from seeing the consequences of their work.
- rchaud 8y agoThe tipping point is when the utility value of their paychecks no longer exceed their personal sense of responsibility about the system they're complicit in.
- iamrobschiavone 8y agoA common practice is to keep developers unaware of the real objective of their work (like Uber, in another comment on HN, https://news.ycombinator.com/item?id=13786384 https://news.ycombinator.com/item?id=13786384): - developer A is tasked to create the prompt to ask for username and password of the email account - developer B is tasked to call some API to upload contacts from email account - developer C is tasked to bind two functionalities. Now replace developers with teams and you see how simple is for the average developer to underestimate the scope and the ethical bounds of a given task.
- codedokode 8y agoThat looks too compilcated. Will you also use several different QA engineers and several product managers for this?
- w0m 8y ago.. isn't that how larger scale projects are done?
- jtms 8y agoI’m dead serious when I say that no two large scale projects are done the same way. I have seen many and can tell you the possibilities are infinite how it gets approached
- sidlls 8y agoYes, work at large organizations with a lot of different features and products, often having complicated interactions, is not trivial.
- numbsafari 8y agoThat implies that you, as a developer, then hear new stories like this one and simply ignore any role you may or may not have had in the situation. It implies that you simply ignore that your manager or engineering leadership are asking you to do things that are unethical without informing you about how your work will be used. It implies that you continue to work for that leadership knowing that they will lie to you, hide their true intentions, and use your labor to execute profoundly unethical practices. It's not news at this point to anyone working at FB what their leadership is engaged in, and what their work is being used to accomplish. Perhaps several years ago you could claim some kind of ignorance. That's no longer the case. You know who you work for. Own it.
- johnchristopher 8y ago> It takes extra work to upload those contacts, which means several managers and developers decided to do it and then spent time implementing it. Not really. Facebook is a bunch of autonomous services (registration, access, tracking, activities, etc.) accessing shared databases (chat logs, activities, media uploads, etc.) with some kind of automatic implicit and explicit ACL in place. The suggestion/contact service got access to data provided through the email-not-working-with-oauth-so-let-us-use-automatic-token-delivery-and-confirmation-by-accessing-user-emails because it was told a new source of contacts were available for those users. So, not a straight path. Accident/Blunder > Evil. Now. GDPR ? GDPR. And because of GDPR those things aren't supposed to happen in Europe.
- codedokode 8y agoFB would probably prefer a word "lended" or "took for a repair" instead of "stole".
- saiya-jin 8y agoConsidering vast crowds of folks happily working for amoral places like investment banks (2008 crisis and its consequences) or wealth management (rich folks trying to keep as much money untaxed as possible and used for public spending), the moral bar for usual smart person is actually pretty low. Optimizing some ads seems pretty harmless when compared to. As long as you don't see the evil being literally done ie in form or row of inmates being sent to gas chambers, there are almost endless ways to persuade yourself that all is actually OK and fine.
- matt4077 8y agoThey did have the upload-your-address-book functionality before they instituted this check. I’m very much hoping to see Facebook suffer for this, but I could conceivably see a scenario where they reused code that did more than they wanted.
- tjpnz 8y ago>For the FB employees reading this: what is your tipping point? Would you say no to that assignment? I have an open ended question aimed mainly towards founders. Would you have any issues in hiring a candidate with Facebook on their resume?
- Sir_Cmpwn 8y agoDepends on the time range. Any time within the past 3-4 years: yeah, that's a problem.
- NoodleIncident 8y agoIn The Fine Article, it says that the feature was built on purpose, and previously asked for permission. The accident is that it wasn't completely removed.
- lkbm 8y ago> It takes extra work to upload those contacts It also takes extra work to ask consent. You build it. You don't notice that your confirmation screen fails to trigger. You've just unintentionally uploaded a bunch of data without consent, when your intention was to do it with consent. It's still pretty darn negligent, but it's easy to see how it could be done unintentionally.