Community Corner Podcast: Agentic Commerce with Paul Conroy

PHP Podcast – November 12, 2026 Hosts: Joe Ferguson, Sara Golemon & Holly Schilling A surprise RC7, assembly-level ABI detective work, Claude landing commits in php-src, a survey on why nobody upgrades, Portuguese wiring codes, and the corporate spy saga that ate your RAM. Just an “off week.” The Surprise RC7 and the Last-Minute Regression Joe, serving as a first-time release manager alongside Matteo Beccati, walked through why PHP 8.6.0 RC7 appeared seemingly out of nowhere. RC6 was tagged on the usual Tuesday cadence, but a regression needed to land, leaving the team a choice: ship 8.6.0 GA with a known regression where working 8.5 code would break on upgrade, or throw another RC. As Joe put it, he’d rather apologize for a last-minute RC than apologize for a regression on GA. The decision was made easier by the fact that packagers like Remy need lead time to rebuild extensions. Because the team committed to an extra RC, they were also able to slip in a few nice-to-haves, including some use-after-free OpenSSL fixes that were all public knowledge and nothing security-embargoed. Sara fully endorsed the “when in doubt, add an RC” philosophy, pointing out that releases happen on Thursdays precisely so the weekend acts as a buffer. A December GA wouldn’t be the end of the world either — uptime-conscious shops wait until January anyway, giving the packages and the public beta crowd time to shake out surprises. Holly reminded everyone: this is a release candidate, not a release. Don’t run it in production. Reading Assembly to Hunt an ABI Break The RC saga tied back to an earlier mistake: the ABI version bump that was missed in RC3 because of the CVE scramble on the 21st. That meant RC3 and RC4 could have had nasty extension conflicts, and anyone seeing weird extension behavior on those builds was likely hitting the ABI break that wasn’t caught until RC5. Joe showed off Daniel Scherzer’s blog post, which drops down into the actual assembly and diffs the obj-dump output for the exception check. The trio squinted at near-identical instruction listings until the real difference surfaced: a jump target that moved from one address to another — about 32 bytes off from where the code expected to be looking. Sara reverse-engineered the cause live: roughly four word-sized fields had been added to the end of a structure (it’s in Reflection), shifting every subsequent offset. She explained the ABI lesson clearly — a header says “this field is X bytes into the structure,” and if you mix an 8.5 header with an 8.6 build, you read garbage memory. For a plain integer that’s bad data; for a pointer, the CPU politely tells you to fuck off, mate. The catch: it only bites extensions built as separate shared objects, not statically built ones. Claude as a Contributor and the “Humans.txt” Problem Joe raised a spirited discussion happening in the PHP Foundation’s internals Slack: Claude Code now shows up as a contributor in php-src, and some worry that reads like the project endorsing a commercial AI tool. Sara pushed back — commits attributed to @yahoo.com or @facebook.com addresses aren’t endorsements, they’re just people contributing while earning a living. Holly added that mailing lists and git clients have appended “Sent from my iPhone” style signatures forever and nobody cared. The real sticking point, Joe argued, is that AI-generated contributions haven’t been tested against open-source licensing in any legal system, yet those contributions are now in the project. Sara pointed to php.net/humans.txt, which still reads “built by humans, mostly” — a “mostly” she thinks may have quietly been there all along. The conversation also detoured into Claude’s new 5.2 behavior around security: it’ll audit your own code and describe exploits with suggested patches, but it won’t generate a proof-of-concept exploit to actually validate the vulnerability. Holly found that limitation a bit pointless, while the gang schemed about pointing it at localhost. Why Teams Don’t Upgrade PHP Joe dug into a recent opt-in survey about what blocks teams from upgrading. The headline findings: it’s almost never a single blocker (47–51% cite more than one), 86% cite at least one business or resource reason, and 51% say there’s no visible ROI in upgrading. Sara’s immediate rebuttal: if you’re on PHP 5, there absolutely is an ROI — you can run half as many servers. Holly aired a pet peeve that upgrading a language version shouldn’t break things, prompting a friendly “citation needed” from Sara. Joe countered that the real pain in legacy apps (pre-8) is usually unvetted, unmaintained dependencies — the one-off package that did one thing well but got abandoned, so even 5.5 to 5.6 broke it. Sara agreed that’s an ecosystem problem, not PHP’s fault, and challenged the group to name actual PHP-caused breaks: pulling mysql out of core, the ternary precedence swap, and little surprises like opcache becoming standard. That opcache change was exactly Holly’s lived example: an 8.3-to-8.5 Docker build broke because a now-unnecessary build step for opcache failed with no obvious documentation. Sara’s gentle suggestion to read the migration guides (plural, since it was a two-version jump) sparked some mock outrage, but the underlying point stood — unnecessary friction is a real cost, and the bigger the version gap, the more insurmountable the step. The survey also noted 56% cite missing tests or staging environments, and even many who run automated tests lack confidence in their coverage. Home Automation, Portuguese Wiring, and the Spouse Test A tangent about testing “wiring” turned literal when Sara revealed she’s been rewiring her new place in Portugal — where brown is live and blue is neutral (IEC color codes), which Joe immediately flagged as a nightmare for the colorblind. Sara’s home is heavy on automation: motorized metal sun shutters, IKEA smart bulbs in GU10 sockets, Shelly modules behind the light switches, internet-connected heat pumps, and a smart plug that only runs the water heater in the cheap overnight electricity window. The group compared setups and the all-important “spouse test.” Joe keeps it minimal — doorbell camera, backyard security cam, and a Google Nest thermostat that keeps re-adding a schedule he deleted — and admitted his Jellyfin server didn’t pass the spouse test at all. Sara and Joe both evangelized Home Assistant: mostly Python but happy to call out to PHP scripts that return JSON, container-friendly via docker-compose, and far from the painful early days of home automation. They swapped favorite automations — Holly’s litter-box nag texts and fridge-door-left-open light color alerts, Joe’s jealousy over people graphing solar production in the Rove Discord’s home automation channel. Add an MQTT broker and Node-RED and you’ve got message buses the whole house can listen to. Holly offered to info-dump on anyone who drops by Discord’s general channel (dark mode supported, naturally). The NVIDIA Spy Saga and a GA on the Horizon Somewhere between RAM shortages and bad TV writing, the crew riffed on the ex-NVIDIA CEO news — allegedly running GPUs on Chinese hardware he wasn’t married to, plus a third “integration” that shouldn’t have been happening, with a spy in the mix and the board already preparing to oust him. Joe shared a Mastodon favorite: a “NVIDIA CEO transitions” headline quote-tooted with “I’m so happy for her,” which Holly and Sara declared very brave in this climate. Back to business: PHP 8.6.0 is scheduled to hit general availability on November 19th, and the team floated doing some live server upgrades as a “release party” during next week’s recording. Huge shout-out to Matteo (watching live from a very late timezone) for herding php-src pull requests and pinging contributors for approvals to get RC6 and RC7 ready. And as always — there are socks that need selling, a freshly leaked phparch.com redesign to break, and a PHP Arch cowboy hat the people are now demanding. Links from the show: PHP Tek 2027 — Chicago, April 27–29, early bird tickets available Join the PHP Architect Discord production.phparch.com — the new site preview (go break it, nicely) Home Assistant — open-source home automation What stops PHP teams from upgrading What happened to PHP 8.6.0RC6? Host: Joe Ferguson Mastodon: @[email protected] PHPArch.me: @svpernova09 Sara Golemon Mastodon: @[email protected] Holly Schilling Mastodon: @[email protected] Streams: Youtube Channel Twitch Connect & Hire PHP Architect Website Twitter/X Mastodon Hire PHP Developers Looking to hire PHP developers? Email [email protected] – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review. Partner This podcast is made a little better thanks to our partners OurCVEs   Your security posture, on autopilot with OurCVEs     CodeRabbit   Cut code review time & bugs in half instantly with CodeRabbit.   PHP Architect Consulting   Your PHP codebase deserves a partner, not a contractor. PHP Architect provides long-term technical partnerships for organizations that need senior-level PHP expertise that you can depend on. https://www.phparch.com/consulting/   Music Provided by Epidemic Sound https://www.epidemicsound.com/ Join Us Live Next Week Youtube Channel Got feedback? Join us on Discord at discord.phparch.com The post The PHP Podcast 2026.11.12 appeared first on PHP Architect.

 In this episode, Scott talks with Zach Watkins about coding through osteoarthritis with Talon Voice, a split keyboard mounted to his chair, and foot pedals with macOS head tracking. Chapters: 00:00 Meet Zach Watkins 01:26 Numb hands and an osteoarthritis diagnosis 03:21 One week searching for answers 06:30 Patching Talon Voice for PHP 10:03 Writing your own voice commands 12:09 Split keyboards on camera mounts 14:01 Layers on a 42-key keyboard 17:17 Foot pedals 19:35 macOS head and face tracking Links: Our Discord – https://discord.gg/aMTxunVx Buy our shirts – https://store.phparch.com/products/community-corner-podcast-t-shirt Mentioned in this episode: Save Your Hands for Another Day (Longhorn PHP 2026 talk) – https://zacharywatkins.com/presentations/save-your-hands-for-another-day/ Coding without typing – https://zacharywatkins.com/articles/coding-without-typing/ Coding without typing (part 2) – https://zacharywatkins.com/articles/coding-without-typing-part-2/ Talon Voice – https://talonvoice.com/ Talon community commands – https://github.com/talonhub/community Zach’s Talon configuration – https://github.com/ZachWatkins/user-talon r/ErgoMechKeyboards – https://www.reddit.com/r/ErgoMechKeyboards/ Crosses keyboard – https://github.com/Good-Great-Grand-Wonderful/crosses Kinesis Savant Elite2 foot pedals – https://kinesis-ergo.com/shop/savant-elite2-triple-pedal/ Move the pointer using head pointer on Mac – https://support.apple.com/guide/mac-help/mchlb2d4782b/mac Shortcuts for Mac – https://support.apple.com/guide/shortcuts-mac/welcome/mac Longhorn PHP – https://www.longhornphp.com/ Zach’s Links: Website – https://zacharywatkins.com/ GitHub – https://github.com/zachwatkins X – https://x.com/zachwatkinsv1 Scott’s Links: Website – https://scott.keck-warren.com/ Bluesky – https://bsky.app/profile/scottkeckwarren.bsky.social LinkedIn – https://www.linkedin.com/in/scott-keck-warren-91689810/ Mastodon – https://phpc.social/@scottkeckwarren PHP Architect Social Media: X: https://x.com/phparch Mastodon: https://phparch.social/@phparch Bluesky: https://bsky.app/profile/phparch.com Discord: https://discord.phparch.com Subscribe to our magazine: https://www.phparch.com/subscribe/ Partners This podcast is made a little better thanks to our partners. OurCVEs Your security posture, on autopilot with OurCVEs   CodeRabbit   Cut code review time & bugs in half instantly with CodeRabbit.     PHP Architect Consulting   Your PHP codebase deserves a partner, not a contractor PHP Architect provides long-term technical partnerships for organizations that need senior-level PHP expertise that you can depend on https://www.phparch.com/consulting/ Music provided by Epidemic Sound https://www.epid The post Community Corner Podcast: Zachary Watkins Codes With His Voice, Feet, and Face appeared first on PHP Architect.

PHP Podcast – November 5, 2026 Hosts: Eric Van Johnson & Joe Ferguson (John Congdon) Two months, a dozen new stream buttons, and a 6 AM crypto-mining emergency. Eric falls in love with a developer-only social network, the PHP2Shell CVE tests the team, and PHP Tek season kicks off. Welcome to the Boss Level. Back After Two Months — and Everything Is On Fire (Audio-Wise) After nearly two months off the air, Eric and John opened the Boss Level episode the only way they know how: with a full-blown audio meltdown. Eric was on the wrong mic, and as usual, his connection kept cutting in and out while the crew wrestled with a fresh stack of stream widgets, pop-up reactions, and survey overlays nobody fully understood. Once they got the sound working, they reintroduced the show. This is the monthly “Boss Level” episode where the two people behind PHP Architect pull back the curtain on the magazine, the conference, and the consulting business — with a little more candor than usual, since, as Eric put it, John can’t fire him and he can’t fire John. Leaked AWS Keys and a 6 AM Bitcoin-Mining Nightmare John’s week started at 6:10 AM with pager alerts about a Lambda function failing to post to Slack. What looked like a trivial memory leak turned out to be something far worse: a leaked AWS key with permission to spin up instances. An attacker had launched 32x and 64x large machines in every single region to mine Bitcoin. The team rallied — four or five people each terminating instances region by region — and disabled the compromised key before new instances could spawn. Using AI tools to dig through the logs, they discovered the key had first been quietly tested back in September, likely by whoever was selling it to prove it was valid before putting it on the market. Identifying and rectifying took about 20 minutes, but it was not a fun morning. /Dev/Null: A Social Network Built for Developers in a Day Eric gushed about /dev/null, a brand-new developer-centric social network built on Laravel in roughly a day or two by Nuno, Brent, Matthew, and Pauline Voss. Everything about it is geared to developers: the main feed is “the log,” posting is “making a commit,” your VIM bindings work inside it, and sign-up ties directly to your GitHub account to pull in your profile. He’s begging the creators to keep the walled garden intact and not make it easier for the “normies.” He also highlighted a TUI built by Wendell (a Laravel employee and PHP Architect columnist) that mirrors the web app so closely it’s become Eric’s home for DevNull right inside his Tmux setup. That led into a tour of his terminal-centric workflow — one Tmux session per project (a trick from Jess Archer), panes for Claude, nvim, and dev servers, lazygit for commits — and why he quietly retired PHPStorm earlier this year in favor of nvim and the terminal. Pauline, a fantastic conference speaker known for Git talks, has even started livestreaming on Twitch following the build. PHP Tech 2027: Call for Speakers Closed, Evaluation Begins The call for speakers has closed, and talk evaluation is underway. John is changing the process this year so reviewers judge fewer talks at a time — one smaller track took him about three minutes. Anyone in the community, ideally planning to attend, can reach out to John on Discord to get added and help pick what gets presented. You rank three anonymized talks side by side, with the title doing most of the heavy lifting since that’s what attendees see on the website. Eric reminded listeners that submitting multiple talks improves their odds of being selected when narrowing the final list. Speakers with more than one accepted talk get priority since they’re the biggest bang for the buck. This year’s third track rotates: a JavaScript day, a Laravel day, and a DevOps day. John noted it was exactly that deployment knowledge gap that first drew him to PHP Tech back in 2010, when he had no idea how to actually deploy an application. All the details live at phptek.io. The PHP-to-Shell CVE and Why a DevOps Person Matters PHP had a rough couple of weeks due to a major “PHP2shell” CVE. Joe, a release manager for the upcoming PHP 8.6, had sensed something was brewing and started preparing rollout plans before the details dropped. When it hit, the team patched nearly everything across their clients within 24 hours, with only a couple of third-party-dependent servers trailing. Eric and John reflected that after 14 years of running their consulting arm (the DiegoDev Group, now PHP Architect Consulting), finally having a dedicated DevOps person has made the difference between night and day. The fallout rippled outward: NativePHP published a candid write-up about having to issue its first-ever security advisory, since a PHP vulnerability affects anything that compiles PHP into a mobile app. The hosts wondered how projects like NativePHP can get into the “consortium” that receives early patch access alongside the big distros. They also pushed back on the “PHP is dead” crowd — this was a memory bug that has lived in the code for 20 years and affects roughly 70% of the web, but memory bugs happen in every language, from Node to npm. The silver lining: a visible spike in PHP Foundation financial contributions, with Eric clarifying that the Foundation funds internal developers but doesn’t dictate PHP’s direction. Git Workflows, SVN War Stories, and the Specialization of Developers The conversation wandered into deployment history — FTP and rsync in the SVN/CVS days — and Eric’s war stories from a Java/WebSphere enterprise shop where developers had no idea where their apps were even hosted. His takeaway: developers today are extremely specialized, and you shouldn’t be surprised when a brilliant Java dev can’t navigate a command line. Eric defended his fork-based Git workflow: a single clean “upstream” repo that only deploys to servers, with everyone forking into their own private GitHub account and sending back only clean, deployment-ready code, essentially the open-source model. The chat gave him grief, including jabs about failing at Git worktrees, which Eric conceded he understands in principle but finds painful in a PHP workflow with its multiple Composer and npm installs and environment files. Links from the show: PHP Tech 2027 — Call for speakers closed; register now PHP Architect Consulting store.phparch.com — PHP Architect merch & elephants PHP Foundation Office Hours (streamed on our channel) Dev-Null.sh PHP 8.6.0 RC5 available for testing Linux Kernel TCP Flaw PHP 8.6’s soft feature freeze PHP Foundation Community Hour Podcast NativePHP first security advisories Host: Eric Van Johnson /dev/null: @ericvanjohsnon X: @shocm Mastodon: @[email protected] Bluesky: @ericvanjohnson.bsky.social PHPArch.me: @eric John Congdon /dev/null: @johncongdon X: @johncongdon Mastodon: @[email protected] Bluesky: @johncongdon.bsky.social PHPArch.me: @john Streams: Youtube Channel Twitch Connect & Hire PHP Architect Website Twitter/X Mastodon Hire PHP Developers Looking to hire PHP developers? Email [email protected] – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review. Partner This podcast is made a little better thanks to our partners OurCVEs Your security posture, on autopilot with OurCVEs   CodeRabbit   Cut code review time & bugs in half instantly with CodeRabbit.   PHP Architect Consulting   Your PHP codebase deserves a partner, not a contractor PHP Architect provides long-term technical partnerships for organizations that need senior-level PHP expertise that you can depend on. https://www.phparch.com/consulting/ Music Provided by Epidemic Sound https://www.epidemicsound.com/ Join Us Live Next Week Youtube Channel Got feedback? Join us on Discord at discord.phparch.com The post The PHP Podcast 2026.11.05 appeared first on PHP Architect.

 In this episode, Scott talks with Jamison Bryant about what sets CakePHP apart from Laravel and Symfony, the plugin ecosystem, and how he moved TicketSauce from CakePHP 2 to 5 with the strangler fig pattern. Links: Our Discord – https://discord.gg/aMTxunVx Buy our shirts – https://store.phparch.com/products/community-corner-podcast-t-shirt Mentioned in this episode: CakePHP – https://cakephp.org/ CakePHP on GitHub – https://github.com/cakephp/cakephp Bake console – https://book.cakephp.org/5/en/bake.html CakePHP plugins directory – https://plugins.cakephp.org/ Awesome CakePHP – https://github.com/FriendsOfCake/awesome-cakephp SwaggerBake plugin – https://github.com/cnizzardini/cakephp-swagger-bake CakePHP Preloader (OPcache) – https://github.com/cnizzardini/cakephp-preloader CakePHP Authentication – https://github.com/cakephp/authentication CakePHP Authorization – https://github.com/cakephp/authorization CakePHP app template – https://github.com/cakephp/app Strangler Fig Application by Martin Fowler – https://martinfowler.com/bliki/StranglerFigApplication.html CakePHP 5.0 migration guide – https://book.cakephp.org/5/en/appendices/5-0-migration-guide.html CakePHP upgrade tool – https://github.com/cakephp/upgrade Rector – https://getrector.org/ Cake Software Foundation – https://cakefoundation.org/ CakeDC – https://www.cakedc.com/ Passbolt – https://www.passbolt.com/ TicketSauce – https://www.ticketsauce.com/ XKCD Dependency – https://xkcd.com/2347/ Longhorn PHP – https://www.longhornphp.com/ php[tek] – https://phptek.io/ I Built a CakePHP Plugin From My iPhone While Packing for a Trip – https://www.phparch.com/article/2026-08-i-built-a-cakephp-plugin-from-my-iphone-while-packing-for-a-trip/ Jamison’s Links: Website – https://jamison.bryant.ai/ Blog (Serious Semicolons) – https://serioussemicolons.wordpress.com/ Mastodon – https://phpc.social/@ssemicolons LinkedIn – https://www.linkedin.com/in/jamisonbryant/ GitHub – https://github.com/jamisonbryant Scott’s Links: Website – https://scott.keck-warren.com/ Bluesky – https://bsky.app/profile/scottkeckwarren.bsky.social LinkedIn – https://www.linkedin.com/in/scott-keck-warren-91689810/ Mastodon – https://phpc.social/@scottkeckwarren PHP Architect Social Media: X: https://x.com/phparch Mastodon: https://phparch.social/@phparch Bluesky: https://bsky.app/profile/phparch.com Discord: https://discord.phparch.com Subscribe to our magazine: https://www.phparch.com/subscribe/ Partners This podcast is made a little better thanks to our partners. OurCVEs Your security posture, on autopilot with OurCVEs   CodeRabbit   Cut code review time & bugs in half instantly with CodeRabbit.     PHP Architect Consulting   Your PHP codebase deserves a partner, not a contractor PHP Architect provides long-term technical partnerships for organizations that need senior-level PHP expertise that you can depend on https://www.phparch.com/consulting/ Music provided by Epidemic Sound https://www.epidemicsound.com/ The post Community Corner Podcast: cakePHP with Jamison Bryant appeared first on PHP Architect.

PHP Podcast – October 29, 2026 Hosts: Joe Ferguson, Sara Golemon & Holly Schilling Patrick Stewart has passed. Tailscale handed out root. The PHP RCE patch landed. And MediaWiki contributer Brooke Vibber tells us how Wikipedia survives celebrity deaths, 500 languages, and Apple’s file system. Patrick Stewart, Cache Stampedes, and the Michael Jackson Outage The crew opened on the sad news of Patrick Stewart’s passing. That segued directly into special guest Brooke Vibber recounting a very real MediaWiki war story from the early days. Back in 2009, when Michael Jackson died, so many people tried to edit the Wikipedia article simultaneously that the entire system fell over. Each save triggered a full re-render, link table updates, and layers of other work — and with a thousand of those happening at once, it destroyed everything. The emergency fix was a hack that served stale cached data to anyone viewing the Michael Jackson page, which instantly brought the site back online. The proper fix came later: a pressure valve for high-concurrency situations, a textbook cache-stampede problem they should have anticipated but didn’t catch until real planetary-scale load exposed it. Since fixing it correctly, they’ve never had a repeat — even for later celebrity deaths. Tailscale SSH Root and the PHP RCE Patch The team covered Tailscale’s security adventure where the built-in SSH functionality let someone already on a node in your tailnet get root on any server running it. Because it requires network access first, it wasn’t catastrophic, and Tailscale patched it quickly — though Holly cheerfully admitted to not updating her family game servers. Talk turned to the big PHP RCE vulnerability. Joe, as a release manager, actually got early access to the patch and noted it was massive — lots of files touched. The Foundation blog explained the bug was found in the 2024 security audit, but the security team struggled not with *how* to fix it but how to fix it *best*, producing competing implementations with different tradeoffs while it remained only a theoretical exploit. Sara underlined that memory-corruption RCEs like this — where a bailout leaves data somewhere it shouldn’t be, eventually turning into bytecode or binary — are extremely hard to pull off, depending on architecture and memory layout. Despite claims of in-the-wild exploitation, most were retracted, and performance impact of the fix turned out to be negligible. Wikimedia’s own response was to simply shut down all user-generated cloud services code until the patch was installed — sometimes the biggest circuit breaker is the best security. HHVM, PHP 7, and the Phantom PHP 6 Brooke walked through Wikimedia’s journey with HHVM, which gave a solid 2x improvement over PHP 5 when Sara’s team at Facebook was pitching it. But once PHP 7 arrived — borrowing many of HHVM’s performance ideas — the gap closed, performance got more consistent and less spiky, and the extra complexity of running HHVM plus the pressure to adopt Hack stopped being worthwhile. Sara took partial credit for grabbing the clever bits out of HHVM and getting them into PHP 7, all without a JIT (that didn’t arrive until PHP 8). Wikimedia stuck with mainline PHP for broader compatibility and because they’d written their entire codebase in PHP and had no desire to switch to Hack. Naturally, the conversation detoured into the legend of PHP 6. Sara confirmed the last version of PHP 6 lives on in a Git tag — something like an experimental first Unicode attempt — and it will generally compile, just don’t expect performance, since it runs about a third the speed of PHP 7. Holly floated secretly shipping PHP 8.6 as the PHP 6 branch, and Sara noted that re-adding Register Globals would be trivially easy and really ought to be an April Fool’s joke someday. 500 Languages, Unicode, and the Localization Cache Brooke revealed MediaWiki is quite possibly the most localized software in the world, supporting roughly 500 human languages — real languages with assigned ISO codes, not Klingon (though that might exist too). The system uses fallback chains, so a reader in a former Soviet country might fall back to Russian before English, and it can even dynamically convert between scripts like Serbian Cyrillic and Latin, or Chinese traditional and simplified. The infrastructure runs across roughly 2,200–2,500 Kubernetes-hosted application servers in data centers in Virginia and Texas (with a smaller caching center in San Francisco). Every MediaWiki update is packaged into an image with the pre-compiled localization cache and atomically rolled out across all nodes. Brooke worked on a patch to move the localization cache from a disk-backed database to an in-memory one built from PHP array literals, letting OPcache deduplicate all the strings automatically. In isolated testing it should yield several percent throughput improvement — which, at Wikipedia’s traffic volume, translates to tens or hundreds of thousands of dollars of equipment saved. The Esperanto Unicode Origin Story In one of the nerdiest stories the show has ever aired, Brooke explained how they first got involved in Wikipedia development back in 2001 — through localization support, while learning Esperanto for fun. (Bonus trivia: there’s a 1966 horror film, *Incubus*, starring William Shatner entirely in Esperanto, with pronunciation so notorious that Esperanto conventions turn it into a drinking game.) Because the early wikis ran 8-bit Latin-1, Esperanto’s accented characters didn’t work. So Brooke patched the open-source code to use UTF-8 for the Esperanto edition — doing Unicode before UTF-8 was the universal standard. As MediaWiki (built by Magnus Manske) took over, every new language wiki went straight to Unicode, and eventually English Wikipedia was converted too, using on-demand dynamic conversion of old Latin-1 revisions to minimize downtime. That led into a gleeful MySQL gripe session: early MySQL 3 had no transactions and no Unicode, so Wikimedia stored UTF-8 in binary fields and managed their own collations. When MySQL 4 “added Unicode,” the fine print revealed it only supported the Basic Multilingual Plane — useless for the rare CJK characters an encyclopedia must store. Normalization Forms and Cursing Apple Brooke saved the best horror story for the end: Unicode normalization. An “é” can be stored as a single precomposed character or as “e” plus a combining accent — and macOS on HFS stored file names the second way while everyone else used the first. The result was Mac users uploading images whose filenames wouldn’t match when others tried to link them. Since a compatible ICU library couldn’t be guaranteed, Brooke wrote a pure-PHP fallback that validated UTF-8 *and* normalized it to the precomposed form, so every way you type a name links the same way. Brooke cursed the Unicode Foundation many times — but cursed Apple a lot more, since everything else did the right thing by default. The group agreed the Intl extension (which provides exactly this normalization) is one of the few things that really should be installed by default — Wikipedia requires it outright now. They closed with a quick nod to Holly’s pet project on scalar extension functions for strings and a final push for the PHP Tech CFP, open through October 31. Links from the show: PHP Tech 2027 — Chicago, April 27–29; CFP & early bird tickets at phptek.io (CFP closes Oct 31) Brooke Vibber — brooke.vibber.net MediaWiki — the engine that runs Wikipedia Join us live in Discord Hosts: Joe Ferguson Mastodon: @[email protected] PHPArch.me: @svpernova09 Sara Golemon Mastodon: @[email protected] Holly Schilling Mastodon: @[email protected] Brooke Vibber Mastodon: @[email protected] Web: brooke.vibber.net Streams: Youtube Channel Twitch Esperanto Unicode Connect & Hire PHP Architect Website Twitter/X Mastodon Hire PHP Developers Looking to hire PHP developers? Email [email protected] – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review. Partner This podcast is made a little better thanks to our partners OurCVEs   Your security posture, on autopilot with OurCVEs     CodeRabbit   Cut code review time & bugs in half instantly with CodeRabbit.   PHP Architect Consulting   Your PHP codebase deserves a partner, not a contractor. PHP Architect provides long-term technical partnerships for organizations that need senior-level PHP expertise that you can depend on. Learn more.   Music Provided by Epidemic Sound https://www.epidemicsound.com/ Join Us Live Next Week Youtube Channel Got feedback? Join us on Discord at discord.phparch.com The post The PHP Podcast 2026.10.29 appeared first on PHP Architect.

PHP Podcast – October 22, 2026 Hosts: Holly, Sara, Joe – Special Guest Daniel Scherzer PHP ships an emergency security release a day early, Daniel Scherzer pushes the commits at 6:30am on four hours of sleep, and governments across Europe start pulling servers offline. Oh, and a 12-pound dog nearly killed Holly. The PHP2Shell Security Release Special guest Daniel Scherzer — release manager for PHP 8.5 and 8.6 and a recent addition to the PHP ecosystem security team — walked the crew through the week’s big story: two critical CVEs that could lead to remote code execution. The team coordinated a synchronized release across PHP 8.2.35, 8.3.36, 8.4.27, and 8.5.12, with additional source backports provided for 7.4, 8.0, and 8.1 given how severe the vulnerabilities were. Daniel described the stress of it all, including waking up at 1am with a headache before a 5am alarm and a release process planned for 1300 UTC. In the end he volunteered to push every change himself, running three commands to push a whole bunch of commits across three repositories in a single atomic operation — four tags and seven branches at 1335 UTC, just before public disclosure. He also drew a clear line around the hats he wears. As a release manager he had early access to the fix, but he deliberately did not patch his own PHP-powered website ahead of time, explaining that the community trusted him to help release PHP, not because he was important enough to get early access for personal use. Governments in Europe were turning off public-facing sites and the NSA published guidance, leaving Daniel marveling at how he ended up with a front-row seat to something heads of government were paying attention to. A Two-Year-Old Bug and the AI Angle The vulnerability wasn’t new — it was originally discovered back in 2024 during the security audit funded through the PHP Foundation via the German government’s Sovereign Tech grant. The bug reportedly traces back through the PHP 5 series and possibly even PHP 4. What changed in 2026 was that someone (with AI tooling assistance) figured out how to turn a theoretical vulnerability into a workable exploit. Daniel pushed back on the framing that AI simply “found” the bug, emphasizing the two years in between where it was known but there weren’t enough maintainer hours or infrastructure to address it. At the time it was essentially a theoretical bug with no consistently provable exploit path. He cautioned that AI-discovered vulnerabilities shouldn’t be assumed correct without a human reviewing them, noting he hadn’t yet seen a clean proof-of-concept that didn’t also rely on some other underlying server vulnerability. The group discussed the rate of security reports skyrocketing as LLMs become common, with Sara describing the bandwidth problem the volunteer security team faces: triaging what’s likely to be exploited, confirming fixes are actually complete, and avoiding publishing an incomplete fix that tips off bad actors. Amazon claimed to have seen exploitation attempts beforehand, but the release manager chat showed no indication the bug was ever exploited in the wild before the release. Fund the Volunteers Who Hold Up the Internet A recurring theme was that PHP is fundamentally a volunteer-driven effort. The packagers for Ubuntu, Debian, and Red Hat — Remy and Andres — were both on vacation and stopped their plans to package PHP a day early. The Docker library maintainers are volunteers too, as are many members of the Foundation security team who are still not paid contractors. The crew highlighted a Mastodon post from Nils Alderman arguing that if the governments shutting down servers, the hosting companies, and the enterprises terrified by this vulnerability each gave even $50,000 a year to the PHP Foundation, things could look very different. Daniel echoed this: had there been infinite money and maintainer hours, every theoretical vulnerability might get fixed as a hardening measure. Joe shared how PHP Architect Consulting had its first client patched roughly 30 minutes after the fix went live — thanks to a tip from Marco Pavetta about forking the Docker PHP library repo and building your own base image before the mirrors saturated. He also recounted his own role helping Derick Rethans keep php.net patched before the announcement so the site wouldn’t fall over under load, including one odd bug where the patched version broke Apache directory listing on downloads.php.net. Life as a Release Manager With three release managers now on the team — Daniel, Joe, and Matteo Beccati — the conversation turned to what the role actually involves. Joe explained he wanted to learn more about the process, especially how to make judgment calls on backwards-compatibility breaks, and that lots of discussion happens behind the scenes before and during a release. Daniel noted he’d volunteered to be 8.5’s release manager for this exact week over a year ago, and that the Zoom coordination call was his idea. They dug into an ABI change in the security release that added new fields to the executor globals. The group debated whether that counts as an ABI break — the consensus being it technically is one, but a safe one as long as you’re not mixing newer extensions depending on those fields with older versions in the same branch. Sara and Holly stressed that extensions should never be wholesale copying global blocks in the first place, especially given how differently that memory behaves in threaded versus non-threaded builds. Daniel shared his origin story: just over two years contributing to PHP, starting with a typo fix to a test name after creating a professional GitHub account under Daniel E. Scherzer. Holly and Sara warned him there’s no escaping — Sara sent her first patch 24 years ago and is still here. The bit about “settling for Joe” ran throughout the whole episode. Rust, C, and the Rewrite Temptation Daniel raised the question of rewriting PHP in Rust, pointing out the vulnerability was fundamentally tied to C’s longjmp, which doesn’t exist in Rust. Sara countered that you don’t need a longjmp approach at all — the same behavior could be achieved with C++ exceptions or a Rust mechanism, but it would be a fundamentally different runtime approach. Holly, half-joking, said she’s one sponsor away from pulling a “bun” and throwing hundreds of thousands of AI agents at a hard rewrite of the PHP engine, predicting this is the first of many memory-safety bugs AI agents will surface in the C codebase. Daniel tempered the hype, noting AIs hallucinate and that this being the first of 100,000 reports doesn’t mean there are 100,000 real memory issues. The segment wrapped with Daniel’s recent work building PHP extensions in Rust (he gave a workshop on it at Longhorn), digging into the C macros for globals and how ZTS thread-support mode changes everything. The repeated advice: learn it, experiment on your own fork, but don’t mess with it until you actually understand it — and never hit git push to the public source. Links from the show: PHP Tek 2027 — April 27–29 in Chicago, early bird tickets available PHP Tek CFP — closes end of October 2026 Scherzer.dev — Daniel’s site, blog, timeline write-up, and hire info PHP Foundation — donate to support PHP security work https://phpc.social/@naderman/117485091076355564 Today’s PHP Security Release, and How We’re Strengthening PHP Security Host: Joe Ferguson Mastodon: @[email protected] PHPArch.me: @svpernova09 Sara Golemon Mastodon: @[email protected] Holly Schilling Mastodon: @[email protected] Streams: Youtube Channel Twitch Connect & Hire PHP Architect Website Twitter/X Mastodon Hire PHP Developers Looking to hire PHP developers? Email [email protected] – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review. Partner This podcast is made a little better thanks to our partners OurCVEs   Your security posture, on autopilot with OurCVEs     CodeRabbit   Cut code review time & bugs in half instantly with CodeRabbit.   PHP Architect Consulting   PHP Architect provides long-term technical partnerships for organizations that need senior-level PHP expertise that you can depend on. Your PHP codebase deserves a partner, not a contractor. Learn more.   Music Provided by Epidemic Sound https://www.epidemicsound.com/ Join Us Live Next Week Youtube Channel Got feedback? Join us on Discord at discord.php.com The post The PHP Podcast 2026.10.22 appeared first on PHP Architect.

   In this episode, Scott talks with Damien Seguy about the history of the elePHPant, from Vincent Pontier’s logo doodle to 6,054 plush toys in Damien’s home, how the community trades them through the Community Postal Service, and what it takes to create your own. Chapters: 00:00 Intro 01:52 How the PHP logo became an elephant 03:53 Turning the logo into a plush toy 05:29 elePHPants for user groups, companies and conferences 07:56 Trading and the Community Postal Service 10:25 The chocolate factory handoff 15:55 How to create your own elePHPant 19:17 Colors, nails and accessories 24:33 Scratchy: elePHPants for small user groups 27:39 Exakat and the PHP onboarding book Links: Our Discord – https://discord.gg/aMTxunVx Buy our shirts – https://store.phparch.com/products/community-corner-podcast-t-shirt Mentioned in this episode: Exakat static analysis engine – https://www.exakat.io/ PHP onboarding book (feedback welcome) – https://thephpbook.readthedocs.io/en/latest Damien’s Links: Bluesky – https://bsky.app/profile/dseguy.bsky.social Mastodon – https://phpc.social/@dseguy GitHub – https://github.com/dseguy Scott’s Links: Website – https://scott.keck-warren.com/ Bluesky – https://bsky.app/profile/scottkeckwarren.bsky.social LinkedIn – https://www.linkedin.com/in/scott-keck-warren-91689810/ Mastodon – https://phpc.social/@scottkeckwarren PHP Architect Social Media: X: https://x.com/phparch Mastodon: https://phparch.social/@phparch Bluesky: https://bsky.app/profile/phparch.com Discord: https://discord.phparch.com Subscribe to our magazine: https://www.phparch.com/subscribe/ Partners This podcast is made a little better thanks to our partners. OurCVEs Your security posture, on autopilot with OurCVEs   CodeRabbit   Cut code review time & bugs in half instantly with CodeRabbit.     PHP Architect Consulting   Your PHP codebase deserves a partner, not a contractor PHP Architect provides long-term technical partnerships for organizations that need senior-level PHP expertise that you can depend on https://www.phparch.com/consulting/ Music provided by Epidemic Sound https://www.epidemicsound.com/ The post Community Corner Podcast: elePHPants with Damien Seguy appeared first on PHP Architect.

PHP Podcast – October 15, 2026 Hosts: Joe Ferguson & Holly Schilling Longhorn PHP kicks off, agentic commerce gets scary, bots keep scanning, and a Cold War satellite schematic proves software is harder than hardware. Swag, Longhorn PHP, and “Am I Even a PHP Developer?” Joe opened by confessing he found a JavaScript bug in the swag store cart while ordering socks and a hoodie — the curse of being a developer who can only ever see the bugs. Holly joked that Sara got bumped from the show for refusing to wear swag, while Eric apparently bought one of everything in the store, including a Peanuts-style team picture card from PHP Tech. The conversation turned to Longhorn PHP 2026, which kicked off with a tutorial day and runs through the main talk day on Friday. Holly is presenting remotely after travel plans fell through, giving a talk on her pet peeve: websites that get “packaged up” and shipped as apps instead of being built as real native applications. That led into a heartfelt riff on imposter syndrome. Holly admitted she’s spent years insisting she’s “not really a PHP developer” despite submitting RFCs, speaking at conferences, and having an elephpant named after her. Joe shared his own years at a Python startup where he felt like a fraud for only writing PHP nights and weekends. The takeaway: showing up in community spaces — Discord, social media, GitHub, conferences — is all it takes to belong. Agentic Commerce and Single-Use Card Security Joe highlighted a Community Corner episode with Scott Keck-Warren and Paul Conroy on agentic commerce — the slightly terrifying idea of your Claude agent going out shopping on your behalf. Holly was especially wary of trusting Gemini for shopping advice given Google’s long history of steering how people search and buy. Much of the underlying tech, they noted, lives in Stripe and resembles Apple Pay-style single-use card numbers: time-limited, amount-limited tokens that protect the real source card. Holly drew on her experience at a buy-now-pay-later company (now branded FlexPay) doing one-time code generation, where even 15-minute-lived card numbers required full PCI compliance, certificate pinning, HMAC, encryption at rest, and constant audits across every layer from mobile SDK to backend. Bots, Scrapers, and Cloudflare to the Rescue A Discord listener (ducknizzle) asked what everyone uses to kill bot and scanner traffic on public sites. Joe’s pessimistic answer: block ranges, sometimes entire countries, and ultimately just put it behind Cloudflare and let specialists deal with it — the same way you’d pay someone to host email rather than running it yourself. Holly praised Cloudflare Pages for static content, calling it free and “it just works” with zero bandwidth worries, though WordPress makes things more complicated. Joe talked about his work-in-progress effort to standardize robots.txt across php.net properties, while acknowledging it only helps the well-behaved crawlers — malicious scrapers and AI training bots will simply ignore it. Holly estimated AI scrapers now outnumber legitimate bots roughly 10 to 1, and both lamented how the internet has lost some of its earlier friendliness. How the PHP Security Team Handles Your Reports Joe showcased a PHP Foundation blog post describing how the security team triages reports, sharing insight from his new role as a release manager. Release managers get advance heads-up on security releases, which follow extra processes to handle disclosures responsibly. He explained that every report is read, triaged, and prioritized — someone in Discord recently got confirmation their advisory was “in the backlog.” The sobering reality is that the greater PHP security team is only one or two humans, reflecting the open-source nature of the project. The team can now issue its own CVEs rather than waiting on GitHub, so fixes and packager updates can ship as fast as possible. Joe noted serious, wild remote-code-execution-level vulnerabilities remain rare, especially this early in the 8.6 cycle, which just branched from master. New PHP News Site, Design, and php.net’s Redesign Joe demoed a new PHP ecosystem news site from Eric Barnes (Laravel News) and Matt Stauffer (Titan) in collaboration with the PHP Foundation — a modern aggregator reminiscent of the old Planet PHP days, complete with RFC coverage, a newsletter, topic sections, and a slick automatic dark mode toggle. Holly, admitting she has no eye for design herself, loved how well it was executed. That sparked a running theme of developer respect for design as a discipline neither host feels competent in. Joe mentioned a php.net redesign in progress — mock-ups are available in the PHPC Discord’s PHP Foundation Ambassador Marketing subgroup, though it’s still a work in progress and not yet mobile friendly. Both admitted feeling like outsiders in design meetings the way non-developers feel in dev meetings. Joe shared Anthropic’s guidance to tell Claude what you *don’t* want for front-end work, to which he replied that as a developer, he often doesn’t even know what he doesn’t want. A Satellite Schematic vs. a Million Lines of Code Holly launched into a favorite tangent, inspired by Apple releasing its home hub device years after the hardware was ready and pundits asking why the software took so long. Working on her own project with 16 encryption keys across five servers, she had to draw diagrams just to keep the key exchanges straight. She then described a treasured artifact: a 3-by-9-foot schematic of an entire FSC-78 Bravo-mod satellite terminal from her Army SATCOM days at Fort Detrich — the whole Cold War-grade, anti-jamming system fitting on roughly 65 letter-sized pages. Contrast that with Margaret Hamilton’s famous photo beside the Apollo code printouts: around a million lines, a scale that’s routine in modern projects. Her point: software complexity dwarfs even elaborate hardware, and developers rarely give themselves credit for it — leaky abstractions, uncaught exceptions, and endless edge cases don’t plague hardware the way they plague code. The discussion wrapped with fault tolerance stories: Joe discovered a three-node Elasticsearch staging cluster where failover had never been enabled (and only one node was taking all the traffic), and Holly recalled a satellite timing setup with redundant cesium sources where the only part that kept failing monthly was the single non-redundant box joining them together. Fault tolerance, they agreed, is important. Links from the show: PHP Tech 2027 — Chicago, April 27–29, tickets & CFP open Join us in Discord PHP Arch Swag Store PHP Foundation — How the Security Team Handles Your Reports Community Corner Podcast: Agentic Commerce with Paul Conroy 2027 State of Open Source Survey (Perforce / OpenLogic / Zend) PHP Architect Consulting Host: Joe Ferguson Mastodon: @[email protected] PHPArch.me: @svpernova09 Sara Golemon Mastodon: @[email protected] Holly Schilling Mastodon: @[email protected] Streams: Youtube Channel Twitch Connect & Hire PHP Architect Website Twitter/X Mastodon Hire PHP Developers Looking to hire PHP developers? Email [email protected] – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review. Partner This podcast is made a little better thanks to our partners OurCVEs   Your security posture, on autopilot with OurCVEs     CodeRabbit   Cut code review time & bugs in half instantly with CodeRabbit.   PHP Architect Consulting   Your PHP codebase deserves a partner, not a contractor. PHP Architect provides long-term technical partnerships for organizations that need senior-level PHP expertise that you can depend on. Learn more.   Music Provided by Epidemic Sound https://www.epidemicsound.com/ Join Us Live Next Week Youtube Channel Got feedback? Join us on Discord at discord.phparch.com The post The PHP Podcast 2026.10.15 appeared first on PHP Architect.

   In this episode, Scott talks with Paul Conroy about agentic commerce: how AI agents buy things on our behalf, how Stripe’s shared payment tokens keep them on a budget, and how the Machine Payments Protocol finally puts HTTP 402 Payment Required to work in your API middleware. Links: Our Discord – https://discord.gg/aMTxunVx Buy our shirts – https://store.phparch.com/products/community-corner-podcast-t-shirt Mentioned in this episode: Charging AI Agents Per Request: A Practical Guide to the Machine Payments Protocol – https://conroyp.com/articles/practical-guide-machine-payments-protocol Agentic Commerce Beyond The Checkout: Building with Machine Payments (Paul’s talk) – https://conroyp.com/speaking/agentic-commerce-beyond-the-checkout-building-with-machine-payments PayForGoals.com, the MPP demo – https://payforgoals.com PayForGoals.com source code – https://github.com/square1-io/www.payforgoals.com laravel-mpp package – https://github.com/square1-io/laravel-mpp Stripe Machine Payments Protocol quickstart – https://docs.stripe.com/payments/machine/mpp/quickstart Paul’s Links: Website – https://conroyp.com Company: Square1 – https://square1.io X / Twitter – https://x.com/conroyp Bluesky – https://bsky.app/profile/conroyp.bsky.social LinkedIn – https://www.linkedin.com/in/paulconroy2/ GitHub – https://github.com/conroyp Scott’s Links: Website – https://scott.keck-warren.com/ Bluesky – https://bsky.app/profile/scottkeckwarren.bsky.social LinkedIn – https://www.linkedin.com/in/scott-keck-warren-91689810/ Mastodon – https://phpc.social/@scottkeckwarren PHP Architect Social Media: X: https://x.com/phparch Mastodon: https://phparch.social/@phparch Bluesky: https://bsky.app/profile/phparch.com Discord: https://discord.phparch.com Subscribe to our magazine: https://www.phparch.com/subscribe/ Partners This podcast is made a little better thanks to our partners. OurCVEs Your security posture, on autopilot with OurCVEs   CodeRabbit   Cut code review time & bugs in half instantly with CodeRabbit.     PHP Architect Consulting   Your PHP codebase deserves a partner, not a contractor PHP Architect provides long-term technical partnerships for organizations that need senior-level PHP expertise that you can depend on https://www.phparch.com/consulting/ Music provided by Epidemic Sound https://www.epidemicsound.com/ The post Community Corner Podcast: Agentic Commerce with Paul Conroy appeared first on PHP Architect.

PHP Foundation Community Hour – October 8, 2026 Hosts: Elizabeth Barron & James Titcumb James tells the story of how he fell into open source, breaks down what Pie actually does, celebrates the 1.5 release, and shares real advice for anyone nervous about making their first contribution. How James Got Into Open Source James traced his open source journey back many years to a set of Zend Framework 1 helper classes he found useful enough to publish, back when he wasn’t even sure GitHub existed yet. From there he built a little tool to deploy code from Git over SSH at a previous employer, replacing a hand-upload process that he knew had to be modernized. Things really took off when he joined Roave, where contributing was actively encouraged and he was surrounded by prolific maintainers like Marco working on Doctrine, alongside in-house libraries such as Security Advisories and Better Reflection. Having a supportive employer early on made all the difference, letting him do the work during the day instead of squeezing it into nights and weekends. Elizabeth reflected that this is a common on-ramp into open source: scratch your own itch, put it out there, and hope it helps someone with the same problem. She emphasized how much employer support, team mentorship, and a genuine culture of open source help newcomers find their footing. What Pie Is and Why It Exists James explained that Pie came about because the infrastructure around PECL and PEAR is simply aging, with very few people who know the code base well enough to maintain it. The PHP Foundation approached him to overhaul that tooling, applying the hard-won lessons of Composer — which he agrees is arguably the best package manager for any language. Under the hood, Pie is really a very fancy wrapper around four commands — phpize, configure, make, and make install — plus a lot of dependency management and making sure you get the right package for your specific PHP install, something PECL never really did. Thanks to the Packagist team setting up an extensions area, Pie plugs into Composer’s source code to get that dependency resolution for free. A key distinction is that you aren’t installing extensions for a project the way you do with Composer packages — you’re installing them for a particular PHP install. Pie manages this in a dedicated Pie home directory, keeping each of your many PHP versions and their extensions sorted out. James’s bigger goal has evolved from simply replacing PECL to making installing an extension as frictionless as installing a PHP package. Democratizing Extensions and the Windows Challenge Moving off PECL’s centralized repository and onto Packagist means literally anyone can now submit an extension, the same way they publish PHP packages. James noted that when problems come up there are usually three kinds of fixes: improving something in Pi, writing better documentation, or working with an extension author who hasn’t configured their composer.json correctly. Because extensions have unique needs, the Composer team added new Pi-specific options to specify configure flags, supported platforms, and architectures — concepts Composer never had since it only ever dealt with pure PHP code. A Windows-only library extension is useless on macOS or Linux, and a systemd-dependent one is useless on Windows, so that categorization matters. The most common friction point James sees is Windows extensions. Unlike PECL, which auto-compiled DLLs from uploaded source, the Pie ecosystem requires authors to build the DLL themselves — handled through a GitHub Action called PHP Windows Builder, which Shivam worked on. For security reasons Pie deliberately can’t just download and run arbitrary binaries on people’s systems. The 1.5 Release Elizabeth congratulated James on shipping 1.5, a significant release that pulled together several large, closely-related requests. A lot of it grew from working with the author of the mlocati Docker PHP extension installer, mapping out everything Pie does on a whiteboard to see where changes could unlock multiple features at once. The big internal change was fixing how Pie handles locking, bringing it much closer to how Composer manages its own lock file. That one improvement enabled installing multiple extensions at once, making a reinstall of an already-installed extension a no-op, installing reproducibly from a lock file, and the long-requested Pie upgrade command that bumps all your Pie extensions in one go. The other massive chunk of work was the attestation library. It started as a bare-bones OpenSSL-based verification of GitHub attestation certificates — written with help from Tim Düsterhus so people could verify Pi’s authenticity without needing the gh CLI. For 1.5, James ran it against the Sigstore conformance test suite and filled in a huge number of gaps, bringing it close to full conformance on the verification side. That opens the door to the Composer team’s stated interest in authenticating PHP packages down the line. Advice for New Contributors Asked what he’d tell his past self, James kept it simple: just get involved, and always assume good intent. If a maintainer doesn’t respond within a day they’re probably just busy — not ignoring you — and lengthy back-and-forth on a pull request usually reflects a maintainer trying to keep the project maintainable, not nitpicking. He encouraged everyone to open a discussion before sending a PR so effort doesn’t get duplicated — a lesson learned after early contributions collided with work he already had in progress. To help with that, he adds a “maintainer investigating” label to issues he’s actively working on, and leans on issue and PR templates to steer people in the right direction. Elizabeth added that newer coders can find it intimidating to put their work out publicly on GitHub forever, and that both sides benefit from a little grace and a shared social contract. James closed by stressing that the single most helpful contribution is feedback — report even the small things you worked around, because eliminating that friction saves the next developer the same headache, as happened with a recent PCRE2 compile fix on macOS. Links from the show: Pie(php/pie) — GitHub repository, issues & discussions PHP Windows Builder GitHub Action Packagist Extensions Composer attestation library Introduction to PIE Host: Elizabeth Barron Mastodon: @[email protected] LinkedIn: elizabethn James Titcumb Mastodon: @[email protected] Streams: Youtube Channel Twitch Connect & Hire PHP Architect Website Twitter/X Mastodon Hire PHP Developers Looking to hire PHP developers? Email [email protected] – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review.   Music Provided by Epidemic Sound https://www.epidemicsound.com/ Join Us Live Next Week Youtube Channel Got feedback? Join us on Discord at discord.phparch.com The post PHP Foundation Community Hour Podcast 2026.10.08 appeared first on PHP Architect.