The Facebook Fake-Out  🔗 **Source:** [The Facebook Fake-Out](https://www.anildash.com/2026/09/29/facebook-fake-out/) > [!note]+ Document Notes > --- > tags: [meta-platforms, platform-accountability, privacy-and-consent, big-tech-regulation, open-web] > author: Anil Dash > source: anildash.com > reference: https://www.anildash.com/2026/09/29/facebook-fake-out/ > date created: 2026-09-30 10:13 > --- > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > # 🏷️ Title: The Facebook Fake-out > ## 🧭 Table of contents > - [📝 Summary](#-summary) > - [📖 Main content](#-main-content) > - [🗒️ Notes](#️-notes) > - [📚 References](#-references) > - [🗣️ Paraphrase](#️-paraphrase) > - [📰 Newsletter](#-newsletter) > - [✅ Action items](#-action-items) > - [🧪 Hypotheses](#-hypotheses) > - [📊 Methodology](#-methodology) > - [❓ Questions](#-questions) > - [🔮 Future research](#-future-research) > - [💡 Implications](#-implications) > - [🧠 Learning styles assessment](#-learning-styles-assessment) > - [📊 Accessibility assessment](#-accessibility-assessment) > - [🌍 DEIB assessment](#-deib-assessment) > - [✅ Logical validity](#-logical-validity) > - [🛡️ DARVO analysis](#️-darvo-analysis) > - [🎯 Conclusion](#-conclusion) > - [🔄 Refactor appendix](#-refactor-appendix--the-facebook-fake-out) > ## 📝 Summary > - **What happened.** anildash.com published "The Facebook Fake-out" on 2026-09-29. It is a short opinion essay, about 510 words in the captured text (¶0 to ¶13). The captured text carries no byline. The author is recorded as Anil Dash because the site is a personal blog under that name and ¶12 says "My Wired column" while linking to a Wired piece on Dash's own site. Treat the byline as inferred from the site, not stated in the text. > - **The claim.** The author says Meta (Facebook's parent company) has run one five-step cycle for decades (¶1 to ¶5): launch something that violates privacy or consent, get caught, announce a pause while calling the practice not that bad, wait for attention to move, then relaunch. The author adds that the company reads the eventual success as proof the idea was fine (¶6), and that the cycle depends on short attention spans, weak institutional accountability, and platform coercion (¶7). > - **Why it matters.** The essay names a repeatable pattern that regulators and journalists can check against a company's record. It also ties the pattern to platform dependence: ¶7 says people can't opt out of large platforms without "dire social consequences," which is the lock-in argument that open-web work answers. > - **Key stakeholders.** Meta (the accused party, with Instagram and WhatsApp named in ¶0), legislators and journalists (the addressed audience in ¶0), users of large platforms (¶7), former Facebook product managers now at OpenAI (¶8), and readers asked to find more examples (¶9). > - **Risks and tradeoffs.** This is opinion and advocacy. Every claim about Meta is the author's characterization. The five-step cycle is asserted as a general pattern, and the captured text names no specific product, date, or press release that went through all five steps. The only dated items are three "Throwbacks" from 2010 and 2012 (¶11 to ¶13), which are links to earlier commentary by the author and Wired, not listed instances of the cycle. Strong language ("nefarious," "toxic behaviors," "genocide") shapes the reader before any evidence appears. > - **Bottom line.** The essay is a useful frame and a weak record. It gives a testable model (five steps, one predicted outcome) but supplies none of the case data that would test it in the text. Verify the specific incidents yourself before repeating the pattern claim in a policy or press setting. > ## 📖 Main content > **Framing and audience.** ¶0 opens by describing Meta as the company "behind Instagram and WhatsApp and the direct enabling of the Rohingya genocide." It says the pattern is something policy, regulation, and journalism people are "constitutionally incapable of understanding," and offers the essay as a reference to send to a legislator or journalist. That sets the purpose: a shareable explainer, not a reported investigation. > **The five-step cycle (¶1 to ¶5).** The steps are: (1) launch a product or feature that plainly violates privacy or consent, (2) get caught by users, tech experts, or researchers, (3) issue a press release announcing a pause while arguing the practice "wasn't really that bad," (4) wait until attention moves elsewhere, (5) relaunch and collect data or surveil behavior without consent. ¶1 says the first step is one "you're probably familiar with" and that it "sometimes even makes headlines." No instance is named. > **The outcome and the internal reading (¶6).** The author says that by the time the feature returns, people have moved on and the company keeps the practice. The author then writes what happens "within the company": the outcome is "taken as proof" the idea was fine, in a quoted line, "See? They were complaining about nothing!" The captured text gives no source for that line. It reads as the author's paraphrase of an attitude, not a quotation from Meta. ¶6 also ties the cycle to the "inevitability" strategy, where technologies are treated as parts of nature. The anchor text "inexorable parts of nature" links to a June 2026 post by the same author. > **Why it works (¶7).** Three conditions: short attention spans, institutions that don't hold companies accountable, and the coercive power of big platforms, described as making it "effectively impossible" for most people to opt out without dire social consequences. These are stated as facts. No study or example supports them in the text. > **Alumni effect (¶8).** The author says former employees carry behaviors to later jobs and gives one example: many former Facebook product managers work at OpenAI, and ChatGPT "has run the same playbook" on privacy and trust. Both claims link to earlier posts by the author (see References). "So many" is not quantified. > **Response (¶9).** No immediate solution is offered "for the foreseeable future." The proposed action is to identify and name the pattern, call it out on repeat, and find examples, past and present. This asks readers to supply the missing case data. > **Throwbacks (¶10 to ¶13).** Three links: "Facebook makes it official: You have no say (2012)," a Wired column on the moment Terms of Service "became abusive" (2012), and "The Facebook Reckoning (2010)." The captured text shows only the anchor titles and years. The linked pages weren't opened. > **Uncertain or contested in this source.** > - "For decades" (¶0): Facebook launched in 2004 by public record, which is under two decades before this essay's date. The text doesn't define the start. Verify what timespan the author means. > - "Direct enabling of the Rohingya genocide" (¶0): the link goes to an Amnesty International page whose URL slug reads as a report finding that Facebook's systems promoted violence against Rohingya and that Meta owes reparations. The slug is not the report text, and the essay's wording ("direct enabling," "genocide") may be stronger than the report's. Check the report's own language. > - The five steps (¶1 to ¶5) are a model, not a dataset. Whether any feature followed all five steps in order, and how many, isn't shown. > - The quoted internal reaction (¶6) is unsourced. > - Former-PM count at OpenAI (¶8) is unquantified and the two supporting links are the author's own posts. > ## 🗒️ Notes > #### 📄 ¶0 Purpose and framing > - Introduces a decades-long Meta pattern that policy, regulation, and journalism audiences "seem" unable to grasp, and offers a clear explanation so people can spot the next repeat (¶0). > - Names Instagram and WhatsApp as Meta properties and links "direct enabling of the Rohingya genocide" to an Amnesty International page (see References). > - Invites readers to send the essay to legislators and journalists. This is advocacy framing from the first paragraph. > #### 📄 ¶1-¶3 Launch, get caught, announce a pause > - Step 1: launch something that violates privacy or consent, described as constant and sometimes headline news (¶1). > - Step 2: users, experts, or researchers find and expose it (¶2). > - Step 3: a press releas  There’s a pattern that Facebook (well, Meta — you know, those folks behind Instagram and WhatsApp and the [direct enabling of the Rohingya genocide](https://www.amnesty.org/en/latest/news/2022/09/myanmar-facebooks-systems-promoted-violence-against-rohingya-meta-owes-reparations-new-report/)) has been following for decades now that everyone in the worlds of policy and regulation and journalism seems to be constitutionally incapable of understanding. So I wanted to take a moment to explain it, clearly and simply, in hopes that this will at least make it obvious when everyone is being tricked again. Feel free to use this as a reference to send to your favorite legislator or journalist the next time they’re getting fooled by Mark Zuckerberg. 1. Launch a new product or feature that very obviously violates people’s privacy or consent. (This one, you’re probably familiar with; they do this constantly, and sometimes it even makes headlines.) 2. Get caught, either by users or by tech experts or researchers who find out Meta has been doing this nefarious thing. 3. Put out a press release announcing that Meta will be pausing this practice, while explaining how it wasn’t *really* that bad. 4. Wait a little while until everybody is paying attention to something else, or the next scandal has popped up. 5. Launch the product or feature again, and steal everybody’s data or surveil everybody’s behavior without their consent or respect for their privacy. Of course, by the time the transgressive technology comes back around, everyone has moved on to the next terrible thing, and the company gets away with the thing that had everyone up in arms in the first place. Within the company, this is taken as proof that it wasn’t a bad idea to begin with: “See? They were complaining about nothing!” It’s a part of the “inevitability” strategy that so much of Silicon Valley has been using for years, where treating new technologies as if they were [inexorable parts of nature](https://www.anildash.com/2026/06/23/fight-ai-platform-war/) is a tactic for getting every part of society to go along with their most extreme plans. Much of this relies on people having short attention spans, on institutions that don’t hold these big companies accountable, and on the coercive power that big platforms like Meta’s have over people’s lives (they effectively make it impossible for most people to opt out without facing dire social consequences). It’s especially important to identify these patterns because the alumni of these companies bring these toxic behaviors with them when they go on to their subsequent roles. It’s no coincidence, for example, that [so many former Facebook product managers work at OpenAI](https://www.anildash.com/2026/02/18/threatening-kids-with-ai/) and that ChatGPT has run the same playbook in terms of [abusing people’s privacy and trust](https://www.anildash.com/2025/10/22/atlas-anti-web-browser/). While we don’t have an immediate solution for this broken behavior, at least for the foreseeable future, what we *can* do is identify these patterns and name them, and call them out when we see them repeat. See if you can’t identify some examples yourself, both from the past and perhaps some that are happening right now. Throwbacks: * [Facebook makes it official: You have no say](https://www.anildash.com/2012/11/28/facebook_makes_it_official_you_have_no_say/) (2012) * [My Wired column capturing the moment their Terms of Service became abusive](https://www.wired.com/2012/08/ts-column/) (2012) * [The Facebook Reckoning](https://www.anildash.com/2010/09/13/the_facebook_reckoning-2010/) (2010), The Facebook Fake-Out, Anil Dash, 01m3saj5460ebmbdwn7dx98m70.