Analyzing WP Engine’s second amended complaint, part 1

Analyzing WP Engine’s second amended complaint, part 1 🔗 **Source:** [Analyzing WP Engine’s second amended complaint, part 1](https://www.delta.blog/analyzing-wp-engines-second-amended-complaint-part-1/) > [!note]+ Document Notes > tags: [WordPress, Litigation, CFAA] > author: The Delta > source: The Delta > reference: [https://www.delta.blog/analyzing-wp-engines-second-amended-complaint-part-1/] > date created: 2025-10-09 00:00 > > # 🏷️ Title: Analyzing WP Engine’s second amended complaint, part 1 >  ## 🧭 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: WP Engine filed a Second Amended Complaint (SAC), reasserting claims not dismissed with prejudice; this part focuses on reviving the CFAA §1030(a)(7) claim and notes extensive new redactions and clarifications. - Why it matters: The SAC adds facts (some sealed) tying alleged “extortionate” threats and the ACF “hijacking” to “damage” against protected computers—key to the CFAA theory. - Key stakeholders: WP Engine, Automattic, Matt Mullenweg, WordPress community, WordPress.org infrastructure/users. - Risks and tradeoffs: Interpreting GPL “freedoms” vs. access to WordPress.org services; reputational and security implications; appeal posture on dismissed claims. - Bottom line: The CFAA claim is materially bolstered—especially via ACF overwrite, WordPress.org access blocks, and alleged internal admissions—but its success turns on preexisting rights and “damage” elements. ## 📖 Main Content - Core arguments: - The SAC is longer (175 vs. 144 pages) but much is unchanged where claims already survived; new material concentrates on reassertions and discovery-backed details. - WP Engine reframes ACF as a “hijacking,” emphasizes “damage” to protected computers: “forcibly overwriting millions of instances of the ACF plugin with the SCF plugin.” - Reasserted CFAA §1030(a)(7) hinges on extortionate threats plus damage; WP Engine ties this to the WordPress.org ban and ACF overwrite, and to an 8% royalty demand. - WP Engine argues preexisting rights via GPL freedoms and community assurances about open access to WordPress.org; acknowledges this is a legal gray area given closed services. - Context/definitions: - CFAA §1030(a)(7) requires threats with intent to extort involving damage/access to protected computers. - “Protected computer” broadly includes internet-connected systems. - GPL grants freedoms to run, modify, and distribute software; it does not directly grant access to third-party services. - Uncertainties: - Redacted discovery may be decisive (e.g., “nuclear war” references, internal views on trademark licensing and ACF actions). - Court’s view on whether WordPress.org access is a preexisting right tied to GPL/community assurances. ### 🗒️ Notes - “This is not a complete rewrite... effectively every one of those thirteen claims... remains unchanged.” - WP Engine filed to unseal redactions; sealed SAC and redline submitted. - WordPress Foundation line strengthened (“properly governed charitable foundation”). - “Nuclear war” dispute: WP Engine cites discovery suggesting fuller phrasing existed. - Woo/Stripe: discovery hints at October 2024 internal actions affecting WP Engine users. - Premeditation: March/July 2024 internal plans; “nuclear war... intentional and premeditated.” - Appeal posture preserved for attempted extortion and standalone trademark misuse. - Pineapple checkbox: framed as defying/mocking PI order; reputational court optics. - CFAA focus: - Switch to “hijacking” for ACF. - “Blocking and interfering with access to wordpress.org’s systems... forcibly overwriting millions of instances...” - Timeline: Sept threats → Oct 5 threats re ACF → Oct 12 takeover. - 8% royalty demand alleged untethered to trademark value. - GPL/community promises cited to ground “preexisting rights”; noted as contestable. - Redactions imply internal admissions on harm, intent, lack of consent, and risk to users. - Harm: lost ACF Pro upgrades, reputational damage, inability to patch, SCF took installs/reviews. ## 📚 References - 18 U.S.C. § 1030 (Computer Fraud and Abuse Act) https://www.law.cornell.edu/uscode/text/18/1030 - GNU General Public License overview https://www.gnu.org/licenses/gpl-3.0.en.html - WordPress.org (project site) https://wordpress.org/ ## 🗣️ Paraphrase - Paragraph A: The SAC adds length and targeted changes, preserving cleared claims while intensifying the CFAA argument with new discovery-backed details and terminology shifts like “hijacking.” - Paragraph B: WP Engine links alleged threats, WordPress.org blocking, and ACF overwrite to CFAA “damage,” arguing preexisting rights via GPL and community assurances, while acknowledging legal ambiguity. ## 📰 Newsletter - This week’s big read: a deep dive into WP Engine’s SAC. The post unpacks why the “hijacking” of ACF and blocking access to WordPress.org may be central to a revived CFAA claim, plus how redacted discovery could sway the court. - Learn: Brush up on CFAA basics (see 18 U.S.C. §1030) and GPL freedoms to understand the rights vs. services debate. - Watchlist: ACF/SCF update paths, plugin directory policies, and any unsealing of redactions. - Community pulse: The “pineapple on pizza” checkbox still stings—optics matter when courts are watching. - Useful links: CFAA statute; GPL overview; WordPress.org handbook for plugin policy context. ## ✅ Action Items #### DevRel - Publish a neutral explainer on CFAA implications for plugin devs and hosts. - Host office hours on WordPress.org dependency risks (updates, APIs). - Create examples showing resilient update channels and rollback strategies. #### OSPO - Clarify policies distinguishing GPL code freedoms vs. third-party service dependencies. - Train on trademark nominative fair use and license negotiation guardrails. - Establish incident intake for platform-access disruptions. #### Community - Run contributor clinics on directory governance and dispute escalation. - Pair sessions for plugin release hygiene and emergency comms. #### WordPress - Core: document guarantees vs. best-effort for .org services exposure. - Core Performance: assess impact of forced plugin overwrite patterns. - Core Program Team: define crisis comms playbook for directory actions. - Security/Plugins/Meta: simulate directory incident drills; improve provenance checks. - Hosting: standardize fallbacks for .org API outages (caching/mirrors). #### The WPOCC - Fund governance clinics and documentation sprints on platform dependencies. - Pilot microgrants for “offline-first” update mechanisms. ### FAIR - Publish covenants separating code freedoms from service control. - Ship signed release artifacts and local mirrors to reduce central points of failure. ## 🧪 Hypotheses - H1: Framing ACF as “hijacking” increases judicial receptivity to CFAA “damage.” - H2: Evidence of premeditation strengthens the extortion element under §1030(a)(7). - H3: Courts will distinguish GPL freedoms from access to WordPress.org services. - H4: Demonstrated harm to update paths and security elevates the “protected computer” damage claim. ### 📊 Methodology - Legal text analysis of §1030(a)(7) elements vs. alleged facts. - Comparative case review on CFAA extortion and platform access disputes. - Expert surveys (IP/infosec) on whether forced plugin overwrites constitute “damage.” ### ❓ Questions - Will the court treat WordPress.org access as a preexisting right? - Do redacted admissions directly tie intent to harm and user risk? - How will nominative fair use weigh against the proposed license demand? ### 🔮 Future Research - Case studies where platform policy actions intersected with CFAA claims. - Empirical analysis of plugin overwrite incidents and downstream security impact. ### 💡 Implications - Practice: Build redundant update channels and rollback tooling. - Policy: Clarify governance over directory controls and emergency changes. - Security: Treat mass overwrite risks as a first-class supply-chain vector. ### 🧠 Learning Styles Assessment - Reading level: Flesch-Kincaid Grade ~12–13. #### 👀 Visual learners - Present: Screenshots referenced (ACF/SCF examples). - Improve: Timelines of events and claim-element mapping. #### 🔊 Aural learners - Present: None. - Improve: 3–5 minute audio summary. #### 🗣️ Verbal learners - Present: Definitions of CFAA elements and GPL freedoms. - Improve: More analogies for “service vs. software” distinction. #### 🧩 Kinesthetic learners - Present: None. - Improve: Hands-on guide to simulate update path fallbacks. #### 🧠 Logical learners - Present: Statute-to-fact tracing. - Improve: Decision trees for claim viability. #### 🧑‍🤝‍🧑 Social learners - Present: Community reactions noted. - Improve: Moderated Q&A and peer roundtables. #### 🧘‍♀️ Solitary learners - Present: Dense notes. - Improve: Reflection prompts and self-check quiz. #### 🌿 Naturalistic learners - Present: None. - Improve: Ecosystem resilience analogies. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear headings. - Improve: Alt text for figures/screenshots. #### Keyboard navigation - Present: Standard article layout. - Improve: Add skip links in site template. #### Contrast and readability - Present: Appears standard. - Improve: Verify 4.5:1; adjust line-height. #### Text resizing and reflow - Present: Responsive site likely. - Improve: Test 200% zoom and reduce motion options. #### Media and captions - Present: Static images. - Improve: Captions and descriptive text. #### Forms and interactions - Present: N/A. - Improve: N/A. #### Standards reference - Map to WCAG 2.2 AA for images, structure, and contrast. ### 🌍 DEIB Assessment #### Cultural breadth - Present: Global community context implied. - Improve: Explicit multi-locale impacts. #### Inclusive language - Present: Generally neutral. - Improve: More plain-language summaries for legal terms. #### Neurodiversity support - Present: Consistent structure. - Improve: More chunking and icon+text labels. #### Representation - Present: N/A for imagery. - Improve: Inclusive examples if adding visuals. #### Psychological safety - Present: Respectful framing. - Improve: Clear community guidelines in linked resources. ### ✅ Logical Validity #### Strong reasoning - Statute-to-fact mapping: quotes CFAA text then aligns alleged actions (overwrite, access block) to “damage.” - Chronology: threats → ban → overwrite sequence supports causality. #### Fallacies - Potential overreach: equating GPL freedoms with service access. Fix by narrowing to documented promises/policies. #### Tone of voice - Analytical, cautious: “I am not a lawyer,” “speculation” labels, balanced on uncertainties. ### 🛡️ DARVO Analysis - Deny: Defense counsel disputes “nuclear war” phrasing. - Attack: Not prominently featured here. - Reverse victim/offender: Alleged framing of license demand as standard negotiation vs. plaintiff’s “extortion” narrative. ## 🎯 Conclusion - Bottom line: The SAC meaningfully strengthens the CFAA §1030(a)(7) claim via discovery-backed details, ACF “hijacking,” and WordPress.org access issues. Outcome likely turns on whether the court recognizes preexisting rights and accepts overwrite/access blocks as “damage.” - Next steps: Watch unsealing motions, the court’s reaction to GPL/service arguments, and part 2 on antitrust claims. ## 🧱 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] CFAA claim hinges on “damage” > [!quote] Analyzing WP Engine’s second amended complaint, part 1 by [[The Delta]] via [[The Delta]]. Published 2025-10-08. Accessed 2025-10-09. > “forcibly overwriting millions of instances of the ACF plugin with the SCF plugin.” Context: Element of “damage” under §1030(a)(7). Use: map alleged overwrite to CFAA. [view highlight](https://www.delta.blog/analyzing-wp-engines-second-amended-complaint-part-1/#H1) #xref #articleseed ID:rw_[MISSING] ### [H2] Preexisting rights are contested > [!quote] Analyzing WP Engine’s second amended complaint, part 1 > “The GPL… grants freedoms… [but] expecting those freedoms apply to closed source services is a stretch.” Context: GPL vs. WordPress.org access. Use: scope of rights. [view highlight](https://www.delta.blog/analyzing-wp-engines-second-amended-complaint-part-1/#H2) #xref ID:rw_[MISSING] --- ### 🔖 Atomic Split Pad (Zettel Candidates) #### [Z1] Forced plugin overwrites qualify as damage - When a platform overwrites installed code en masse. - Pointer: ACF→SCF overwrite episode. - Links: [[CFAA]] [[Software Supply Chain]] #### [Z2] GPL freedoms don’t guarantee service access - Applies where third-party services front GPL software. - Pointer: Court’s treatment of WordPress.org access. - Links: [[GPL]] [[Platform Governance]] --- ### ✏️ Fleeting Queue (Extract by Selection) - [F1] Draft visual timeline: threats → ban → overwrite — https://www.delta.blog/analyzing-wp-engines-second-amended-complaint-part-1/ #fleeting #inbox - [F2] Compile CFAA §1030(a)(7) case comps — https://www.law.cornell.edu/uscode/text/18/1030 #fleeting #inbox - [F3] Outline “service vs. software rights” explainer — https://www.gnu.org/licenses/gpl-3.0.en.html #fleeting #inbox --- # 🏷️ Title: Analyzing WP Engine’s second amended complaint, part 1 ## 🧭 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: WP Engine filed a Second Amended Complaint (SAC), reasserting claims not dismissed with prejudice; this part focuses on reviving the CFAA §1030(a)(7) claim and notes extensive new redactions and clarifications. - Why it matters: The SAC adds facts (some sealed) tying alleged “extortionate” threats and the ACF “hijacking” to “damage” against protected computers—key to the CFAA theory. - Key stakeholders: WP Engine, Automattic, Matt Mullenweg, WordPress community, WordPress.org infrastructure/users. - Risks and tradeoffs: Interpreting GPL “freedoms” vs. access to WordPress.org services; reputational and security implications; appeal posture on dismissed claims. - Bottom line: The CFAA claim is materially bolstered—especially via ACF overwrite, WordPress.org access blocks, and alleged internal admissions—but its success turns on preexisting rights and “damage” elements. ## 📖 Main Content - Core arguments: - The SAC is longer (175 vs. 144 pages) but much is unchanged where claims already survived; new material concentrates on reassertions and discovery-backed details. - WP Engine reframes ACF as a “hijacking,” emphasizes “damage” to protected computers: “forcibly overwriting millions of instances of the ACF plugin with the SCF plugin.” - Reasserted CFAA §1030(a)(7) hinges on extortionate threats plus damage; WP Engine ties this to the WordPress.org ban and ACF overwrite, and to an 8% royalty demand. - WP Engine argues preexisting rights via GPL freedoms and community assurances about open access to WordPress.org; acknowledges this is a legal gray area given closed services. - Context/definitions: - CFAA §1030(a)(7) requires threats with intent to extort involving damage/access to protected computers. - “Protected computer” broadly includes internet-connected systems. - GPL grants freedoms to run, modify, and distribute software; it does not directly grant access to third-party services. - Uncertainties: - Redacted discovery may be decisive (e.g., “nuclear war” references, internal views on trademark licensing and ACF actions). - Court’s view on whether WordPress.org access is a preexisting right tied to GPL/community assurances. ### 🗒️ Notes - “This is not a complete rewrite... effectively every one of those thirteen claims... remains unchanged.” - WP Engine filed to unseal redactions; sealed SAC and redline submitted. - WordPress Foundation line strengthened (“properly governed charitable foundation”). - “Nuclear war” dispute: WP Engine cites discovery suggesting fuller phrasing existed. - Woo/Stripe: discovery hints at October 2024 internal actions affecting WP Engine users. - Premeditation: March/July 2024 internal plans; “nuclear war... intentional and premeditated.” - Appeal posture preserved for attempted extortion and standalone trademark misuse. - Pineapple checkbox: framed as defying/mocking PI order; reputational court optics. - CFAA focus: - Switch to “hijacking” for ACF. - “Blocking and interfering with access to wordpress.org’s systems... forcibly overwriting millions of instances...” - Timeline: Sept threats → Oct 5 threats re ACF → Oct 12 takeover. - 8% royalty demand alleged untethered to trademark value. - GPL/community promises cited to ground “preexisting rights”; noted as contestable. - Redactions imply internal admissions on harm, intent, lack of consent, and risk to users. - Harm: lost ACF Pro upgrades, reputational damage, inability to patch, SCF took installs/reviews. ## 📚 References - 18 U.S.C. § 1030 (Computer Fraud and Abuse Act) https://www.law.cornell.edu/uscode/text/18/1030 - GNU General Public License overview https://www.gnu.org/licenses/gpl-3.0.en.html - WordPress.org (project site) https://wordpress.org/ ## 🗣️ Paraphrase - Paragraph A: The SAC adds length and targeted changes, preserving cleared claims while intensifying the CFAA argument with new discovery-backed details and terminology shifts like “hijacking.” - Paragraph B: WP Engine links alleged threats, WordPress.org blocking, and ACF overwrite to CFAA “damage,” arguing preexisting rights via GPL and community assurances, while acknowledging legal ambiguity. ## 📰 Newsletter - This week’s big read: a deep dive into WP Engine’s SAC. The post unpacks why the “hijacking” of ACF and blocking access to WordPress.org may be central to a revived CFAA claim, plus how redacted discovery could sway the court. - Learn: Brush up on CFAA basics (see 18 U.S.C. §1030) and GPL freedoms to understand the rights vs. services debate. - Watchlist: ACF/SCF update paths, plugin directory policies, and any unsealing of redactions. - Community pulse: The “pineapple on pizza” checkbox still stings—optics matter when courts are watching. - Useful links: CFAA statute; GPL overview; WordPress.org handbook for plugin policy context. ## ✅ Action Items #### DevRel - Publish a neutral explainer on CFAA implications for plugin devs and hosts. - Host office hours on WordPress.org dependency risks (updates, APIs). - Create examples showing resilient update channels and rollback strategies. #### OSPO - Clarify policies distinguishing GPL code freedoms vs. third-party service dependencies. - Train on trademark nominative fair use and license negotiation guardrails. - Establish incident intake for platform-access disruptions. #### Community - Run contributor clinics on directory governance and dispute escalation. - Pair sessions for plugin release hygiene and emergency comms. #### WordPress - Core: document guarantees vs. best-effort for .org services exposure. - Core Performance: assess impact of forced plugin overwrite patterns. - Core Program Team: define crisis comms playbook for directory actions. - Security/Plugins/Meta: simulate directory incident drills; improve provenance checks. - Hosting: standardize fallbacks for .org API outages (caching/mirrors). #### The WPOCC - Fund governance clinics and documentation sprints on platform dependencies. - Pilot microgrants for “offline-first” update mechanisms. ### FAIR - Publish covenants separating code freedoms from service control. - Ship signed release artifacts and local mirrors to reduce central points of failure. ## 🧪 Hypotheses - H1: Framing ACF as “hijacking” increases judicial receptivity to CFAA “damage.” - H2: Evidence of premeditation strengthens the extortion element under §1030(a)(7). - H3: Courts will distinguish GPL freedoms from access to WordPress.org services. - H4: Demonstrated harm to update paths and security elevates the “protected computer” damage claim. ### 📊 Methodology - Legal text analysis of §1030(a)(7) elements vs. alleged facts. - Comparative case review on CFAA extortion and platform access disputes. - Expert surveys (IP/infosec) on whether forced plugin overwrites constitute “damage.” ### ❓ Questions - Will the court treat WordPress.org access as a preexisting right? - Do redacted admissions directly tie intent to harm and user risk? - How will nominative fair use weigh against the proposed license demand? ### 🔮 Future Research - Case studies where platform policy actions intersected with CFAA claims. - Empirical analysis of plugin overwrite incidents and downstream security impact. ### 💡 Implications - Practice: Build redundant update channels and rollback tooling. - Policy: Clarify governance over directory controls and emergency changes. - Security: Treat mass overwrite risks as a first-class supply-chain vector. ### 🧠 Learning Styles Assessment - Reading level: Flesch-Kincaid Grade ~12–13. #### 👀 Visual learners - Present: Screenshots referenced (ACF/SCF examples). - Improve: Timelines of events and claim-element mapping. #### 🔊 Aural learners - Present: None. - Improve: 3–5 minute audio summary. #### 🗣️ Verbal learners - Present: Definitions of CFAA elements and GPL freedoms. - Improve: More analogies for “service vs. software” distinction. #### 🧩 Kinesthetic learners - Present: None. - Improve: Hands-on guide to simulate update path fallbacks. #### 🧠 Logical learners - Present: Statute-to-fact tracing. - Improve: Decision trees for claim viability. #### 🧑‍🤝‍🧑 Social learners - Present: Community reactions noted. - Improve: Moderated Q&A and peer roundtables. #### 🧘‍♀️ Solitary learners - Present: Dense notes. - Improve: Reflection prompts and self-check quiz. #### 🌿 Naturalistic learners - Present: None. - Improve: Ecosystem resilience analogies. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear headings. - Improve: Alt text for figures/screenshots. #### Keyboard navigation - Present: Standard article layout. - Improve: Add skip links in site template. #### Contrast and readability - Present: Appears standard. - Improve: Verify 4.5:1; adjust line-height. #### Text resizing and reflow - Present: Responsive site likely. - Improve: Test 200% zoom and reduce motion options. #### Media and captions - Present: Static images. - Improve: Captions and descriptive text. #### Forms and interactions - Present: N/A. - Improve: N/A. #### Standards reference - Map to WCAG 2.2 AA for images, structure, and contrast. ### 🌍 DEIB Assessment #### Cultural breadth - Present: Global community context implied. - Improve: Explicit multi-locale impacts. #### Inclusive language - Present: Generally neutral. - Improve: More plain-language summaries for legal terms. #### Neurodiversity support - Present: Consistent structure. - Improve: More chunking and icon+text labels. #### Representation - Present: N/A for imagery. - Improve: Inclusive examples if adding visuals. #### Psychological safety - Present: Respectful framing. - Improve: Clear community guidelines in linked resources. ### ✅ Logical Validity #### Strong reasoning - Statute-to-fact mapping: quotes CFAA text then aligns alleged actions (overwrite, access block) to “damage.” - Chronology: threats → ban → overwrite sequence supports causality. #### Fallacies - Potential overreach: equating GPL freedoms with service access. Fix by narrowing to documented promises/policies. #### Tone of voice - Analytical, cautious: “I am not a lawyer,” “speculation” labels, balanced on uncertainties. ### 🛡️ DARVO Analysis - Deny: Defense counsel disputes “nuclear war” phrasing. - Attack: Not prominently featured here. - Reverse victim/offender: Alleged framing of license demand as standard negotiation vs. plaintiff’s “extortion” narrative. ## 🎯 Conclusion - Bottom line: The SAC meaningfully strengthens the CFAA §1030(a)(7) claim via discovery-backed details, ACF “hijacking,” and WordPress.org access issues. Outcome likely turns on whether the court recognizes preexisting rights and accepts overwrite/access blocks as “damage.” - Next steps: Watch unsealing motions, the court’s reaction to GPL/service arguments, and part 2 on antitrust claims. ## 🧱 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] CFAA claim hinges on “damage” > [!quote] Analyzing WP Engine’s second amended complaint, part 1 by [[The Delta]] via [[The Delta]]. Published 2025-10-08. Accessed 2025-10-09. > “forcibly overwriting millions of instances of the ACF plugin with the SCF plugin.” Context: Element of “damage” under §1030(a)(7). Use: map alleged overwrite to CFAA. [view highlight](https://www.delta.blog/analyzing-wp-engines-second-amended-complaint-part-1/#H1) #xref #articleseed ID:rw_[MISSING] ### [H2] Preexisting rights are contested > [!quote] Analyzing WP Engine’s second amended complaint, part 1 > “The GPL… grants freedoms… [but] expecting those freedoms apply to closed source services is a stretch.” Context: GPL vs. WordPress.org access. Use: scope of rights. [view highlight](https://www.delta.blog/analyzing-wp-engines-second-amended-complaint-part-1/#H2) #xref ID:rw_[MISSING] --- ### 🔖 Atomic Split Pad (Zettel Candidates) #### [Z1] Forced plugin overwrites qualify as damage - When a platform overwrites installed code en masse. - Pointer: ACF→SCF overwrite episode. - Links: [[CFAA]] [[Software Supply Chain]] #### [Z2] GPL freedoms don’t guarantee service access - Applies where third-party services front GPL software. - Pointer: Court’s treatment of WordPress.org access. - Links: [[GPL]] [[Platform Governance]] --- ### ✏️ Fleeting Queue (Extract by Selection) - [F1] Draft visual timeline: threats → ban → overwrite — https://www.delta.blog/analyzing-wp-engines-second-amended-complaint-part-1/ #fleeting #inbox - [F2] Compile CFAA §1030(a)(7) case comps — https://www.law.cornell.edu/uscode/text/18/1030 #fleeting #inbox - [F3] Outline “service vs. software rights” explainer — https://www.gnu.org/licenses/gpl-3.0.en.html #fleeting #inbox ---