Behind the Manifesto: The Survivors of the Open Web 🔗 **Source:** [Behind the Manifesto: The Survivors of the Open Web](https://blog.mozilla.org/netpolicy/2025/11/12/behind-the-manifesto-the-survivors-of-the-open-web/) > [!note]+ Document Notes > tags: [Open Web, Antitrust, Browser Engines] > author: Jenn Taylor Hodges > source: Mozilla Blog > reference: [https://blog.mozilla.org/netpolicy/2025/11/12/behind-the-manifesto-the-survivors-of-the-open-web/] > date created: 2025-11-14 00:00 > > # 🏷️ Title: Behind the Manifesto: The Survivors of the Open Web > <!-- deep-read:sections start --> ## 🧭 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) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - What happened: Mozilla launched a “Behind the Manifesto” blog entry recapping a DC meetup on competition, antitrust, and AI’s impact on the open web, highlighting browser engine diversity. - Why it matters: Fewer engines (now WebKit, Blink, Gecko) risk consolidation, reducing “choice, perspectives, and ideas” and threatening an interoperable, open web. - Key stakeholders: Mozilla, independent browsers, regulators, consumers, Big Tech, policy institutes, AI researchers. - Risks and tradeoffs: Remedies in antitrust (e.g., search vs. browser competition) may create monitoring burdens or require divestitures; AI scale advantages may entrench incumbents. - Bottom line: Sustaining competition in engines and platforms is essential to protect user agency and an open, innovative web. ## 📖 Main Content - Core arguments: - The open web depends on “invisible layers” like engines, standards, and protocols that enable interoperability and permissionless innovation. - Engine consolidation from five to three raises systemic risks; maintaining Gecko alongside Blink and WebKit is about openness, not dominance. - Antitrust is “cross-partisan,” and remedies must balance search and browser competition without harming independents. - AI shifts markets but largely amplifies existing concentration due to data/compute/talent advantages. - Context and terms: - Browser engines: software that interprets web content (e.g., Gecko, Blink, WebKit). - Divestiture: structural remedy separating business units to reduce conflicts/market power. - Uncertainties: - Efficacy of antitrust remedies and data-sharing terms. - Whether AI competition will broaden or further entrench incumbents. ### 🗒️ Notes - “The internet wasn’t always… a digital commons where anyone could publish, connect, and build without asking permission.” - “In 2013, there were five major browser engines. Now, only three remain…” - “Antitrust is back… results do tend to be bipartisan.” - “Ensuring that search competition didn’t come at the expense of browser competition… the devil is going to be in the detail.” - “Divestiture… If you leave Chrome under Google, you have to build in surveillance and monitoring…” - “AI has upended the market… but… Big Tech… has been training for this… data, compute, talent… concentrated… by design.” - “There needs to be a field where new businesses can enter. Without it, we are fighting the last war.” ## 📚 References - Mozilla Manifesto (https://www.mozilla.org/en-US/about/manifesto/) - United States v. Google LLC, search case overview (https://www.justice.gov/atr/case/us-et-al-v-google-llc) - Gecko engine overview (https://developer.mozilla.org/en-US/docs/Mozilla/Gecko) - Blink engine overview (https://chromium.org/blink) - WebKit engine overview (https://webkit.org/) - Knight–Georgetown Institute (https://www.georgetown.edu/initiative/knight-georgetown-institute/) - AI Now Institute (https://ainowinstitute.org/) - Foundation for American Innovation (https://www.thefai.org/) ## 🗣️ Paraphrase - Paragraph A: The web thrived as a public, interoperable commons built on open layers like engines and standards; consolidation threatens these foundations. - Paragraph B: Policymakers and experts see bipartisan momentum in antitrust and debate search remedies, AI’s concentration dynamics, and how to keep entry paths open. ## 📰 Newsletter Mozilla’s latest “Behind the Manifesto” digs into why browser engine diversity matters for the open web. With only three engines left—Gecko, Blink, WebKit—experts at a DC meetup weighed antitrust remedies, AI’s consolidation pressures, and how to keep real choices alive for users and developers. If you build for the web, this is your reminder: interoperability isn’t automatic—it’s defended. Explore the Mozilla Manifesto, follow developments in the Google search case, and keep your apps standards-first to reduce engine lock-in. Helpful reads: the Mozilla Manifesto, MDN’s Gecko docs, and WebKit/Blink roadmaps. ## ✅ Action Items #### DevRel - Publish engine-compat demos and testbeds; track pass rates across Gecko/Blink/WebKit. - Run workshops on standards-first patterns and portability. - Improve quickstarts and repro templates for cross-engine bugs. - Campaign: “One Web, Many Engines” with attribution via UTM to docs/issues. #### OSPO - Define contribution policies for web standards work; clarify decision rights. - Institute license and provenance checks for engine-adjacent tooling. - Security: coordinated disclosure with cross-engine liaison channel. - SBOM strategy for web runtime dependencies; freshness SLOs. #### Community - Maintainer clinics on interoperable APIs and release hygiene. - First-issue rotations focused on web-compat. - Sponsor milestones tied to interop metrics; publish impact reports. #### WordPress - Core: enforce performance budgets and compatibility CI across engines. - Core Performance: dashboards for layout/JS interop regressions. - Core AI: guardrails for responsible features; eval sets for fairness/latency. - Program Team: align cross-team interop priorities; quarterly retros. - Training: lessons on standards, progressive enhancement, web-compat triage. - Accessibility: regular WCAG audits; motion/contrast preferences testing. - Meta: .org reliability SLAs; contributor tool stability across browsers. #### The WPOCC - Programs: microgrants for interop bug bounties. - Projects: documentation sprints on standards compliance. - Funding: matched grants for engine-agnostic plugins. ### FAIR - Technical independence: provenance and signature checks for build artifacts. - Policies: funding transparency; anti-capture covenants for standards bodies. - Governance artifacts: open charters and operator agreements for interop work. ## 🧪 Hypotheses - Sustained funding for non-dominant engines increases interop pass rates year-over-year. - Structural antitrust remedies (e.g., divestiture) reduce default-lock share more than conduct remedies. - Data-access remedies enable ≥2 new search entrants to reach measurable market share within 3 years. - AI inference defaults in browsers shift query distribution away from a single provider by ≥10%. ### 📊 Methodology - Longitudinal interop testing (WPT suites) across engines; difference-in-differences after policy changes. - Market-share and default-status analyses pre/post remedies. - Survey-based user choice experiments with randomized defaults and disclosures. - Audit AI integration paths (APIs, defaults, prompts) for steering effects. ### ❓ Questions - Which remedies best protect both search and browser competition simultaneously? - How can data-sharing be structured to avoid re-centralization? - What incentives most effectively attract new engine contributors? ### 🔮 Future Research - Measurement of AI-assisted browsing’s impact on open web traffic. - Governance models for standards bodies to resist capture. - Sustainable funding mechanisms for public-interest engines. ### 💡 Implications - Practice: prioritize standards and progressive enhancement to avoid lock-in. - Policy: balance structural and conduct remedies; mandate transparent defaults. - Security: shared disclosure frameworks across engines. - Education: curricula on web architecture and interop testing. ### 🧠 Learning Styles Assessment - Reading level estimate: Flesch-Kincaid ~11–12. #### 👀 Visual learners - Present: conceptual contrasts (open vs. walled gardens). - Improve: engine/standards stack diagrams; interop trend charts. #### 🔊 Aural learners - Present: quotes. - Improve: 3–5 minute audio summary. #### 🗣️ Verbal learners - Present: definitions and analogies. - Improve: glossary and side-by-side term comparisons. #### 🧩 Kinesthetic learners - Present: n/a. - Improve: hands-on interop labs and checklists. #### 🧠 Logical learners - Present: causal reasoning on consolidation. - Improve: decision trees and KPI dashboards. #### 🧑‍🤝‍🧑 Social learners - Present: panel perspectives. - Improve: moderated Q&A and peer review prompts. #### 🧘‍♀️ Solitary learners - Present: structured narrative. - Improve: reflection prompts and self-check quizzes. #### 🌿 Naturalistic learners - Present: ecosystem framing. - Improve: lifecycle and sustainability analogies. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: headings. - Improve: consistent landmarks and descriptive alt text. #### Keyboard navigation - Present: logical order. - Improve: explicit skip links and visible focus. #### Contrast and readability - Present: likely OK text contrast. - Improve: verify 4.5:1; adjust line-height. #### Text resizing and reflow - Present: responsive content. - Improve: test at 200%+ and reduced motion. #### Media and captions - Present: text quotes. - Improve: audio descriptions/transcripts for any embeds. #### Forms and interactions - Present: n/a. - Improve: accessible toasts and forgiving inputs if forms exist. #### Standards reference - Map gaps to WCAG 2.2 AA. ### 🌍 DEIB Assessment #### Cultural breadth - Present: US policy focus. - Improve: global case studies and translations. #### Inclusive language - Present: neutral tone. - Improve: plain-language summaries and expanded glossary. #### Neurodiversity support - Present: consistent structure. - Improve: chunking and icon+text labels. #### Representation - Present: varied orgs/voices. - Improve: broader regional/disciplinary representation. #### Psychological safety - Present: respectful framing. - Improve: community guidelines and moderated discussion. ### ✅ Logical Validity #### Strong reasoning - Inductive: engine consolidation → reduced choice; supported by count drop from five to three. - Causal: AI scale → concentration; ties to data/compute/talent control. #### Fallacies - Potential survivorship bias: focusing on remaining engines; could add data on failed engines and reasons. - Remedy efficacy uncertainty: clarify with comparative case studies. #### Tone of voice - Constructive, mission-driven, cautious about concentration. ### 🛡️ DARVO Analysis - Deny: none; acknowledges consolidation. - Attack: none; no undermining of critics. - Reverse victim/offender: none; emphasizes systemic risks, not victimhood. ## 🎯 Conclusion - Bottom line: Keeping multiple strong browser engines and fair platform rules is essential to preserve an open, interoperable web; antitrust and AI policy choices now will shape that future. - Next steps: Track interop metrics, advocate balanced remedies, fund open engine work, and design user experiences that foreground choice. ## 🧱 Refactor Appendix (append after 🎯 Conclusion) ### 📚 Literature Split Pad - Purpose: Stage Konik CEE units that become per-source Literature notes. - Split level: H3. - Include verbatim quotes under 25 words and a [view highlight] link. ### [H1] Engine diversity sustains the open web > [!quote] Behind the Manifesto: The Survivors of the Open Web by [[Jenn Taylor Hodges]] via [[Mozilla Blog]]. Published 2025-11-12. Accessed 2025-11-14. > “Layers such as browser engines, open standards, and shared protocols are the scaffolding…” Two lines: Motivation to preserve interoperability; use in policy advocacy. [view highlight](https://blog.mozilla.org/netpolicy/2025/11/12/behind-the-manifesto-the-survivors-of-the-open-web/#H1) #xref #articleseed ID:rw_[MISSING] ### [H2] Antitrust is cross-partisan in the US > [!quote] Behind the Manifesto: The Survivors of the Open Web > “Antitrust is back… results do tend to be bipartisan.” Two lines: Signals durable policy window; use in coalition-building. [view highlight](https://blog.mozilla.org/netpolicy/2025/11/12/behind-the-manifesto-the-survivors-of-the-open-web/#H2) #xref ID:rw_[MISSING] --- ### 🔖 Atomic Split Pad (Zettel Candidates) - Purpose: Promote reusable claims into Atomic notes. - Split level: H4. - Each item: one idea, present tense, specific, testable. #### [Z1] Diverse browser engines improve user choice - Scope: consumer browser markets, 2013–present. - Pointer: engine count from five to three. - Links: [[Interoperability]] [[Competition-Policy]] #### [Z2] AI scale advantages entrench incumbents - Scope: platforms with data/compute/talent concentration. - Pointer: expert panel quotes on AI consolidation. - Links: [[AI-Governance]] [[Market-Structure]] --- ### ✏️ Fleeting Queue (Extract by Selection) - [F1] Draft interop KPI dashboard for engine parity — context/https://blog.mozilla.org/netpolicy/2025/11/12/behind-the-manifesto-the-survivors-of-the-open-web/ #fleeting #inbox - [F2] Compile antitrust remedy case notes (divestiture vs. conduct) — context/https://www.justice.gov/atr/case/us-et-al-v-google-llc #fleeting #inbox - [F3] Outline “One Web, Many Engines” DevRel campaign — context/https://developer.mozilla.org/ #fleeting #inbox --- <!-- deep-read:sections end -->