Whistle-Blower Says Facebook ‘Chooses Profits Over Safety’
Frances Haugen, a Facebook product manager who left the company in May, revealed that she had provided internal documents to journalists and others. Some of Ms. Haugen’s documents have also been distributed to the state attorneys general for California, Vermont, Tennessee, Massachusetts and Nebraska, Mr. Tye said. But he said the documents were not shared with the Federal Trade Commission, which has filed an antitrust suit against Facebook. In a video posted by Whistleblower Aid on Sunday, Ms. Haugen said she did not believe breaking up Facebook would solve the problems inherent at the company. “The path forward is about transparency and governance,” she said in the video. “It’s not about breaking up Facebook.” Ms. Haugen has also spoken to lawmakers in France and Britain, as well as a member of European Parliament. This month, she is scheduled to appear before a British parliamentary committee. That will be followed by stops at Web Summit, a technology conference in Lisbon, and in Brussels to meet with European policymakers in November, Mr. Tye said. On Sunday, a GoFundMe page that Whistleblower Aid created for Ms. Haugen also went live. Noting that Facebook had “limitless resources and an army of lawyers,” the group set a goal of raising $10,000. Within 30 minutes, 18 donors had given $1,195. Shortly afterward, the fund-raising goal was increased to $50,000.
Facebook and all of its apps go down simultaneously.
Facebook’s internal communications platform, Workplace, was also taken out, leaving most employees unable to do their jobs. SAN FRANCISCO — Facebook and its family of apps, including Instagram and WhatsApp, went down at the same time on Monday, taking out a vital communications platform used by more than three billion people around the world and adding heat to a company already under intense scrutiny. Facebook’s apps — which include Facebook, Instagram, WhatsApp, Facebook Messenger and Oculus — began displaying error messages around 11:40 a.m. Eastern time, users reported. Within five minutes, Facebook had disappeared from the internet. Hours later, the sites were still not functioning, Facebook’s last significant outage was in 2019, when a technical error affected its sites for 24 hours, in a reminder that even the most powerful internet companies can still be crippled by a snafu. This time, the cause of the outage remained unclear. Several hours into the incident, Facebook’s security experts were still trying to identify the root issue, according to an internal memo and employees briefed on the matter. Two members of its security team, who spoke on the condition of anonymity because they were not authorized to speak publicly, said it was unlikely that a cyberattack had taken place because one hack was unlikely to affect so many apps at once. Inside Facebook, workers scrambled because their internal systems also stopped functioning. The company’s global security team “was notified of a system outage affecting all Facebook internal systems and tools,” according to an internal memo sent to employees. Those tools included security systems, an internal calendar and scheduling tools, the memo said. Employees said they had trouble making calls from work-issued cellphones and receiving emails from people outside the company. Facebook’s internal communications platform, Workplace, was also taken out, leaving many unable to do their jobs. Some turned to other platforms to communicate, including LinkedIn and Zoom as well as Discord chat rooms. Some Facebook employees who had returned to working in the office were also unable to enter buildings and conference rooms because their digital badges stopped working. Security engineers said they were hampered from assessing the outage because they could not get to server areas. Several Facebook workers called the outage the equivalent of a “snow day,” a sentiment that was publicly echoed by Adam Mosseri, the head of Instagram. Facebook has already been dealing with plenty of scrutiny. The company has been under fire from a whistle-blower, Frances Haugen, a former Facebook product manager who amassed thousands of pages of internal research and has since distributed them to the news media, lawmakers and regulators. The documents revealed that Facebook knew of many harms that its services were causing. Ms. Haugen, who revealed her identity (yesterdy) on Sunday online and on “60 Minutes,” is scheduled to testify on Tuesday in Congress about Facebook’s impact on young users. John Graham-Cumming, the chief technology officer of Cloudflare, a web infrastructure company, said in an interview that Monday’s problem was most likely a misconfiguration of Facebook’s servers.
The Fakest "Whistleblower" Ever
In a lesser-noticed but revealing portion of Frances Haugen’s stage-managed PR tour last week, the vaunted “Facebook Whistleblower” took a moment to show off her “national security” credentials for Republican Senator Dan Sullivan of Alaska. After the two had finished rehearsing all the reasons why American children are at such grave risk from a dangerously unregulated internet, they pivoted to another topic — that being Haugen’s previous experience at Facebook working in what she describes as “counter-espionage” operations. Yes, you read that right: Haugen was apparently a “project manager” at something called the “threat intelligence org,” located deep in the bowels of Facebook, at which she claims to have presided over a team carrying out “counter-espionage” ops on behalf of Mark Zuckerberg.
The internet is the last remaining instrument for dissent and free discourse to thrive outside state and oligarchical control. This campaign aims to put an end to that. Glenn Greenwald - Oct 25
sexton@vrx Mon Oct 04 13:24:29 ~ % dig ns facebook.com @b.gtld-servers.net ; <<>> DiG 9.11.1 <<>> ns facebook.com @b.gtld-servers.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27004 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 9 ;; WARNING: recursion requested but not available ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;facebook.com. IN NS ;; AUTHORITY SECTION: facebook.com. 172800 IN NS a.ns.facebook.com. facebook.com. 172800 IN NS b.ns.facebook.com. facebook.com. 172800 IN NS c.ns.facebook.com. facebook.com. 172800 IN NS d.ns.facebook.com. ;; ADDITIONAL SECTION: a.ns.facebook.com. 172800 IN A 129.134.30.12 a.ns.facebook.com. 172800 IN AAAA 2a03:2880:f0fc:c:face:b00c:0:35 b.ns.facebook.com. 172800 IN A 129.134.31.12 b.ns.facebook.com. 172800 IN AAAA 2a03:2880:f0fd:c:face:b00c:0:35 c.ns.facebook.com. 172800 IN A 185.89.218.12 c.ns.facebook.com. 172800 IN AAAA 2a03:2880:f1fc:c:face:b00c:0:35 d.ns.facebook.com. 172800 IN A 185.89.219.12 d.ns.facebook.com. 172800 IN AAAA 2a03:2880:f1fd:c:face:b00c:0:35 sexton@vrx Mon Oct 04 13:26:41 ~ % ping a.ns.facebook.com. PING a.ns.facebook.com. (129.134.30.12): 56 data bytes ^C --- 129.134.30.12 ping statistics --- 3 packets transmitted, 0 packets received, 100.0% packet loss sexton@vrx Mon Oct 04 13:27:47 ~ % traceroute a.ns.facebook.com. traceroute to a.ns.facebook.com. (129.134.30.12), 64 hops max, 40 byte packets 1 vrx (xxx.xxx.xxx.1) 0.158 ms 0.123 ms 0.093 ms 2 xxx 0.330 ms 0.562 ms 0.212 ms 3 xxx 0.743 ms 0.674 ms 0.779 ms 4 xxx 109.149 ms 107.849 ms 107.844 ms 5 xxx 108.475 ms 108.476 ms 108.465 ms 6 HundredGE0-3-0-0.br03.hkg12.pccwbtn.net (63.218.174.189) 152.769 ms TenGE0-1-0-1.br03.hkg12.pccwbtn.net (63.218.174.37) 155.060 ms HundredGE0-7-0-2.br03.hkg12.pccwbtn.net (63.218.174.113) 156.170 ms 7 TenGE0-1-0-1.br03.hkg12.pccwbtn.net (63.218.174.37) 156.238 ms TenGE0-0-0-10.br03.hkg12.pccwbtn.net (63.218.174.78) 154.896 ms TenGE0-1-0-1.br03.hkg12.pccwbtn.net (63.218.174.37) 156.156 ms 8 * * sexton@vrx Mon Oct 04 13:28:51 ~ % traceroute c.ns.facebook.com. traceroute to c.ns.facebook.com. (185.89.218.12), 64 hops max, 40 byte packets 1 vrx (xxx.xxx.xxx.1) 0.139 ms 0.109 ms 0.095 ms 2 * * * 3 * * * 4 * *
