Interoperable Facebook  ## Metadata - Author: [[Electronic Frontier Foundation]] - Full Title: Interoperable Facebook - Category: #articles - Document Note: --- tags: - #interoperability - #antitrust - #decentralization Author: Electronic Frontier Foundation Source: EFF article/video Reference: https://www.eff.org/interoperablefacebook date created: 2025-08-21 00:00 --- # Title: Interoperable Facebook ## Table of Contents: - [🎯 Overview](#-overview) - [🧩 Context: Why we stay on platforms we don’t enjoy](#-context-why-we-stay-on-platforms-we-dont-enjoy) - [🔗 What interoperability means](#-what-interoperability-means) - [⚖️ Policy landscape (DMA, ACCESS Act)](#️-policy-landscape-dma-access-act) - [🖥️ Design fiction: Life on an interoperable Facebook](#️-design-fiction-life-on-an-interoperable-facebook) - [🧭 Impacts: Choice, competition, and safety](#-impacts-choice-competition-and-safety) - [🗒️ Notes](#-notes) - [📖 References](#-references) - [🗣️ Paraphrase](#-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items (DevRel/OSPO alignment)](#-action-items-devrelospo-alignment) - [🧪 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) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) ### References: - EU Digital Markets Act overview: https://digital-strategy.ec.europa.eu/en/policies/digital-markets-act - ACCESS Act (US interoperability proposal – backgrounder): https://www.congress.gov/bill/117th-congress/senate-bill/2992 - EFF’s shorter examples video (as referenced by the article) - Downloadable PDF (as referenced by the article) ## 📝 Summary: EFF presents a video and design fiction showing how legally mandated interoperability could transform Facebook from a walled garden into a hub that can exchange posts and messages with many smaller, community-run, and nonprofit services. Rather than framing social media stickiness as “addiction,” Cory Doctorow explains that lock-in, switching costs, and network effects keep users on platforms they no longer enjoy. Interoperability—backed by policies such as the EU’s Digital Markets Act and the proposed US ACCESS Act—would let users choose alternative interfaces and providers while still communicating with friends on incumbent platforms. The piece argues that this would reduce Big Tech dominance, restore user agency, and stimulate a healthier ecosystem. ## 📖 Main Content: - The lock-in problem - EFF argues the core reason users stay isn’t mere “addiction,” but lack of viable exits that preserve social graphs, history, and reach. - Network effects concentrate value; switching means losing contacts and context. - Interoperability defined - Technical and legal ability for different services to exchange private messages and public posts. - Users pick the client or community server they prefer without severing ties to friends on Facebook. - Policy drivers - EU DMA compels gatekeepers to enable certain forms of interoperability and prohibits self-preferencing that thwarts it. - US ACCESS Act proposals would require dominant platforms to maintain interoperable interfaces under oversight. - Design fiction: What it could feel like - You log into your favorite community-run app but can still DM friends on Facebook, join groups, and post across networks. - Safety controls, filters, and moderation can be provided by your chosen app, not only by the incumbent. - Anticipated benefits - Increased user choice and mobility; competitive pressure on incumbents. - Diverse moderation models; specialized communities; innovation from small players. - Implementation considerations - Secure APIs/protocols; consented data portability; anti-spam/abuse safeguards. - Standards governance; interoperability testing; enforcement to prevent sabotage by incumbents. ### 🗒️ Notes - Stickiness isn’t just “addiction” - Lock-in: contacts, identity, history. - High switching costs; loss aversion. - Network effects amplify incumbency. - Interop mechanics - Federated or bridged messaging and posting. - Consistent identity and consent across services. - Transport encryption; rate limiting; abuse reporting. - Regulatory context - DMA: mandates gatekeeper obligations, including interop for messaging. - ACCESS Act: US approach to interoperability and portability oversight. - Design fiction scenarios - Cross-posting from a community client to Facebook friends. - Receiving Facebook DMs in a third-party app with your own filters. - Moderation chosen by you rather than imposed by a single platform. - Risks and mitigations - Abuse vectors: spam, brigading across networks → shared blocklists, trust frameworks. - Privacy leaks via poorly designed bridges → scoped tokens, data minimization. - Incumbent non-compliance → audits, penalties, independent testing. - Outcomes - More competition and innovation. - Greater user agency and healthier social experiences. - Reduced centralization without requiring everyone to move at once. ## 📖 References: - Interoperable Facebook (EFF): https://www.eff.org/interoperablefacebook - Digital Markets Act: https://digital-strategy.ec.europa.eu/en/policies/digital-markets-act - ACCESS Act background: https://www.congress.gov/bill/117th-congress/senate-bill/2992 ## 🗣️ Paraphrase: - Original idea: “It’s not because social media is ‘addictive’…” - Paraphrase: The main reason people remain on platforms like Facebook isn’t a chemical hook; it’s the structural barriers—network effects and lock-in—that make leaving costly while isolating you from your social circles. - Original idea: “Small companies, nonprofits, and community-run services will be able to connect…” - Paraphrase: If interoperability is mandated, independent and community-controlled apps could directly communicate with Facebook, allowing everyone to exchange posts and messages regardless of the service they prefer to use. ## 📰 Newsletter: This week in the WordPress-verse: leveling up your dev chops and your freedom to choose. On the learning front, we’ve got fresh resources for modern PHP patterns, JS bundles you’ll actually enjoy shipping, and CSS container queries that feel like cheating (but aren’t). Community-wise, we’re celebrating new contributors tackling first issues in Core and applauding maintainers experimenting with interoperable, federated social features for WordPress sites—because talking across platforms shouldn’t feel like long-distance in the ’90s. Plugin radar: a lightweight ActivityPub bridge helps your site speak fluent fediverse, and a GitHub Actions starter speeds up plugin CI with tidy test matrices. For a bigger-picture read, EFF’s “Interoperable Facebook” explores why we stick with platforms we don’t love and how policy-backed interoperability could finally let users choose their tools without losing their friends. If that resonates with your open web heart, consider piloting cross-network comments or experimenting with message bridges. Links: Interoperable Facebook by EFF (policy + design fiction): https://www.eff.org/interoperablefacebook; Digital Markets Act basics: https://digital-strategy.ec.europa.eu/en/policies/digital-markets-act. Friendly reminder: hydrate your docs, not just your plants. ## ✅ Action Items: Prompt for aligning this article with your DevRel/OSPO goals: - Purpose: Explain how mandated interoperability in social platforms models best practices for open ecosystems in WordPress and open source. - Alignment dimensions: - Open-source advocacy: Map interop principles (open protocols, portable data, user agency) to WordPress’s plugin/theme ecosystem and to federated social standards (e.g., ActivityPub). - Contributor engagement: Propose contributor pathways to build/maintain bridges (WordPress plugins, REST/GraphQL adapters) and moderation tools for cross-network interactions. - Education: Design curricula on interoperability architectures, standards governance, responsible API design, and trust/safety in federated systems. - Sustainable funding: Outline funding for maintenance of interop plugins, security reviews, and moderation infrastructure via sponsorships, foundations, or OSPO-backed budgets. - OSPO trajectory: Define policies for dependency governance, protocol selection criteria, compliance with privacy and accessibility, and a playbook for interop incident response. - Transparency and inclusivity: Recommend community norms for consentful data flows, algorithmic transparency, and multilingual documentation. - Deliverables: - Workshop: “From Walled Gardens to Bridges: Interop Patterns for WordPress.” - Reference plugin: ActivityPub + Facebook/Threads bridge prototype with consent-first UX. - Policy brief: WordPress ecosystem recommendations aligned with DMA-like obligations. - Maintainer guide: Abuse mitigation across federated networks (blocklists, rate limits, reports). - Metrics: Adoption of interop plugins, cross-network engagement quality, incident rates. - Speaking abstract: - “Interoperable Social: How WordPress Can Operationalize User Agency through Open Protocols” — tie EFF’s vision to practical tools, governance, and education. ## 🧪 Hypotheses: - H1: Enforcing interoperability decreases user churn anxiety and increases multi-home usage without reducing total social engagement. - H2: Third-party moderation layers chosen by users improve perceived safety versus single-platform moderation. - H3: Availability of federated bridges stimulates SME and nonprofit entry into social tooling markets. - H4: Data minimization and consent-based interop reduces privacy harm relative to screen-scraping or gray-market APIs. ### 📊 Methodology: - Mixed-methods evaluations: - A/B field trials with interoperable bridges vs. control on community sites; measure engagement, safety incidents, and satisfaction. - Surveys/interviews on switching costs and perceived agency. - Instrumentation: privacy-preserving analytics; incident taxonomies; rate-limit telemetry. - Data sources: - WordPress plugin telemetry (opt-in), moderation logs, support tickets. - Public policy datasets on DMA compliance outcomes. - Analysis: - Difference-in-differences for pre/post interop adoption. - Causal inference with propensity matching for communities that adopt bridges. - Thematic coding of qualitative feedback. ### ❓ Questions: - How can interoperability preserve end-to-end encryption across heterogeneous services? - What governance prevents incumbents from “embrace-extend-extinguish” of open protocols? - Which moderation responsibilities belong to origin vs. destination services? - How do we design consent UX for cross-posting without dark patterns? - What performance SLAs are realistic for federated bridges at scale? ### 🔮 Future Research: - Protocol-agnostic trust frameworks for spam/abuse that respect privacy. - Interop-specific threat modeling for identity spoofing and metadata leakage. - Economic impacts of interop on SME entrants and nonprofit hosts. - Accessibility standards for cross-network content transformation. - Legal safe harbors for third-party clients and bridges. ### 💡 Implications: - Advances competition policy with practical technical scaffolding. - Informs platform governance and OSPO policies on protocol selection and maintenance. - Guides open-source communities toward safer, user-controlled federation. - Shapes educational programs for responsible interop engineering. ### 🧠 Learning Styles Assessment: - Readability: General audience, upper high-school to early college level. - Visual (Present): Video with graphics. Improve: Add system diagrams and flowcharts of interop data paths and moderation flows. - Aural (Present): Narrated video. Improve: Provide an audio-only podcast feed and short audio summaries. - Verbal (Present): Clear conceptual framing. Improve: Add more examples, glossaries, and links to standards. - Kinesthetic (Present): Limited. Improve: Provide hands-on labs, code samples, and sandbox bridges. - Logical (Present): Policy-to-technical reasoning. Improve: Include explicit architectures, decision trees, and metrics. - Social (Present): Community-run services highlighted. Improve: Link to forums, working groups, and contributor calls. - Solitary (Present): Downloadable PDF. Improve: Reflection prompts and self-paced exercises. - Naturalistic (Present): Not emphasized. Improve: Note sustainability impacts of decentralization (e.g., hosting choices, energy use). ### 📊 Accessibility Assessment: - Screen readers: Ensure semantic headings, transcripts, and alt text for all visuals. - Keyboard navigation: Confirm tabbable controls and visible focus states on the video page. - Contrast/readability: Use high-contrast palette and scalable, legible fonts. - Text resizing: Ensure responsive layouts support 200% zoom without loss of content; provide downloadable, accessible PDF with tagged structure and captions. ### 🌍 DEIB (Diversity, Equity, Inclusion, Belonging) Assessment: - Cultural relevance: Expand case studies to include global-majority communities and low-bandwidth contexts. - Inclusive language: Generally neutral; define technical/policy terms for non-experts. - Neurodiversity support: Break content into shorter segments; include bullet points and summaries per section. - Representation: Highlight diverse maintainers, nonprofits, and community servers. - Psychological safety: Add content warnings where discussing harassment; link to resources for targeted communities. ### ✅ Logical validity: - Strong reasoning: - Causal reasoning: Lock-in and network effects explain user stickiness; this grounds the need for interop. - Balanced view: Acknowledges multiple providers (small companies, nonprofits, community-run) and user choice. - Ethical reasoning: Emphasizes user agency and competition as public-interest goals. - Areas to strengthen: - Provide empirical evidence on outcomes where interop exists (e.g., messaging interop in DMA pilots, ActivityPub ecosystems). - Detail safeguards against abuse and privacy risks with concrete frameworks. - Potential fallacies to avoid: - False dilemma: Avoid implying interop is the only remedy; mention complementary measures (data portability, enforcement against unfair conduct). - Hasty generalization: Don’t assume all interop improves welfare; specify conditions for success (security, consent, governance). - Tone: Persuasive, advocacy-oriented, informative. 🔍 DARVO Analysis: - Deny: The piece reframes “addiction” narratives rather than denying harms; no denial of problems—acknowledges structural causes. - Attack: No attacks on individuals; critiques structures and policies. - Reverse Victim/Offender: Does not cast incumbents as victims; centers users’ lack of agency. Minimal DARVO indicators; rhetoric is policy- and solution-focused. ### 🔍 SEO Evaluation: - Keywords: “interoperability,” “Facebook,” “walled gardens,” “Digital Markets Act,” “ACCESS Act,” “open social networks.” - Placement: Ensure keywords appear in title, first paragraph, subheads, and meta description. - Meta description (example): “What if Facebook had to interoperate? EFF and Cory Doctorow explore laws like the DMA that could let you choose your app and still talk to everyone.” - Title tag: “Interoperable Facebook: How Laws Could Open Walled Gardens” (≤60 chars if needed). - Headers: Use H2/H3 with key terms: “What is interoperability,” “DMA and ACCESS Act,” “Design fiction examples.” - Content length: Expand beyond video transcript with a 1,200–1,800-word explainer. - Links: Add authoritative external links to DMA texts, ACCESS Act, and standards like ActivityPub. - URL: Already concise and descriptive. - Images: Include descriptive alt text; optimized sizes and filenames (e.g., interoperable-facebook-diagram.png). - Mobile: Ensure responsive video embeds and compressed assets. - Engagement: Add CTAs to watch the shorter examples video, download PDF, and join discussions. - Schema: Use Article schema; include VideoObject for the embedded video; add FAQ schema for common interop questions. - Social sharing: Configure Open Graph/Twitter Cards with a compelling image and summary. ## 🎯 Conclusion: EFF’s Interoperable Facebook argues that user dissatisfaction with big platforms stems less from “addiction” and more from structural lock-in. Mandated interoperability—via policies like the DMA and proposals like the ACCESS Act—would let users choose the tools and communities they prefer while staying connected to friends who remain on large platforms. The design fiction makes this concrete: cross-network posts and messages, user-chosen moderation, and a more competitive, innovative ecosystem. For WordPress and open-source advocates, this vision aligns directly with building bridges, championing open protocols, and teaching responsible, inclusive federation at scale. - Summary: In this video, we discuss the forces that keep us using services like Facebook long after we stop enjoying them (hint, it's not because social media is "addictive") and we present a short "design fiction" explaining what it might be like to use social media in the near future, after big companies... - URL: https://www.eff.org/interoperablefacebook  In this video, we discuss the forces that keep us using services like Facebook long after we stop enjoying them (hint, it's not because social media is "addictive") and we present a short "design fiction" explaining what it might be like to use social media in the near future, after big companies like Facebook were legally required to open up their walled gardens and let their users talk to anyone online, not just other Facebook users. What if Facebook - and the other tech giants - were simply less important to your life? What if you had lots of choices about how you and the people you care about could communicate with each other? Several proposed laws—like the EU Digital Markets Act and the US ACCESS Act—aim to make Big Tech platforms interoperable. That means that small companies, nonprofits, and community-run services will be able to connect to platforms like Facebook and everyone will be able to exchange private messages and public posts, no matter which service they choose. But how would that work? What would life be like on an "interoperable Facebook? In this video, EFF’s Cory Doctorow describes how we got here, and why interoperability is a great solution to our social media woes. Then we demonstrate what interoperability might look like on Facebook—allowing you to chat and post through a variety of other platforms—so you have the choice of how social media should work for you. Want to skip straight to the examples of interoperability on Facebook? This shorter video is for you: [Download the PDF](https://eff.org/files/2022/09/12/interoperablefacebook-2022_0.pdf) of the article the video is based on here. [](https://eff.org/files/2022/09/12/interoperablefacebook-2022_0.pdf) Credits: * Produced by the Electronic Frontier Foundation * Written and narrated by Cory Doctorow * Graphics and production by Shirin Mori * Sound design, mastering and music by John Taylor Williams, Wryneck Studios, Interoperable Facebook, Electronic Frontier Foundation, 01jw4jh9fb022z0h8vz73cwfv3.