<IMG SRC="https://cdn.jwz.org/images/scaled/768/2024/goatsepress.png" WIDTH=1024 HEIGHT=734 STYLE="width: 30%; height: auto; max-width: 1024px; max-height: 734px; border: 0; box-sizing: border-box; margin: 0 0.5em 1em 1em; float: right; clear: right;" SRCSET="https://cdn.jwz.org/images/2024/goatsepress.png 1024w, https://cdn.jwz.org/images/scaled/768/2024/goatsepress.png 768w, https://cdn.jwz.org/images/scaled/640/2024/goatsepress.png 640w, https://cdn.jwz.org/images/scaled/360/2024/goatsepress.png 360w" SIZES="(max-width: 660px) 30vw, 22em" LOADING="lazy" data-size="1024x734"> WP 7.0 was just released and apparently this <A HREF="https://www.linkedin.com/pulse/wp-70-cut-its-biggest-feature-shipped-ai-layer-instead-ishan-dwivedi-aqkvc/">is the "AI" release</A>. Is there a patch to excise this cancer from core, or is there a bugfix-tracking fork that I should switch to instead, or should I just never upgrade again, or what? <P><A HREF="https://www.jwz.org/blog/2025/12/what-if-the-torment-nexus-was-fundamental-to-wordpress/">Previously</A>, <A HREF="https://www.jwz.org/blog/2026/02/ai-is-a-dick-move/">previously</A>, <A HREF="https://www.jwz.org/blog/2024/07/gravatar-dunning-krugerrands/">previously</A>, <A HREF="https://www.jwz.org/blog/2024/10/lets-pick-the-right-product-for-you/">previously</A>, <A HREF="https://www.jwz.org/blog/2023/04/feedly-launches-strikebreaking-as-a-service/">previously</A>, <A HREF="https://www.jwz.org/blog/2013/06/google-reader-apocalypse-extremely-fucking-nigh/">previously</A>.

WP 7.0 was just released and apparently this is the "AI" release. Is there a patch to excise this cancer from core, or is there a bugfix-tracking fork that I should switch to instead, or should I just never upgrade again, or what? Previously, previously, previously, previously, previously, previously.

 WP 7.0 was just released and apparently this <a href="https://www.linkedin.com/pulse/wp-70-cut-its-biggest-feature-shipped-ai-layer-instead-ishan-dwivedi-aqkvc/" rel="noopener noreferrer">is the "AI" release</a>. Is there a patch to excise this cancer from core, or is there a bugfix-tracking fork that I should switch to instead, or should I just never upgrade again, or what? <p><a href="https://www.jwz.org/blog/2025/12/what-if-the-torment-nexus-was-fundamental-to-wordpress/" rel="noopener noreferrer">Previously</a>, <a href="https://www.jwz.org/blog/2026/02/ai-is-a-dick-move/" rel="noopener noreferrer">previously</a>, <a href="https://www.jwz.org/blog/2024/07/gravatar-dunning-krugerrands/" rel="noopener noreferrer">previously</a>, <a href="https://www.jwz.org/blog/2024/10/lets-pick-the-right-product-for-you/" rel="noopener noreferrer">previously</a>, <a href="https://www.jwz.org/blog/2023/04/feedly-launches-strikebreaking-as-a-service/" rel="noopener noreferrer">previously</a>, <a href="https://www.jwz.org/blog/2013/06/google-reader-apocalypse-extremely-fucking-nigh/" rel="noopener noreferrer">previously</a>.</p>

Share WordPress "AI" Apocalypse Extremely Fucking Nigh

Sign up to save your podcasts

WordPress "AI" Apocalypse Extremely Fucking Nigh

WordPress "AI" Apocalypse Extremely Fucking Nigh