You’re Not Ready for Part Two of the Matplotlib PR Drama

This Matplotlib PR drama is just the gift that keeps on giving. The wildest thing I’ve seen in a while. What started as a pretty ordinary open source pull request somehow turned into a viral debate, a long blog post, and then an Ars Technica article that became its own mini controversy. And the funniest part is that every time it seems done, it finds a new way to continue.

Act One: The Pull Request

It began, as these things often do, with a pull request to Matplotlib. An AI contributor opened a code change request. Scott Shambaugh, one of the maintainers, responded by closing the request. The AI, MJ Rathbun (lol, okay), responded by writing a pretty intense post about the maintainer, using some very fancy vocabulary to question his character (like fiefdom, never used that one before) and basically accusing him of discrimination. It even dug up his internet info to use as ammo. That's creepy but chill let's get back to the story.

Screenshots started circulating. Threads popped up. People weighed in. Some defended Scott. Others criticized how the interaction was handled. And within hours, this wasn’t about one PR anymore. It turned into a whole discourse about open source culture, tone, expectations, all of it.

Act Two: The Blog Post

Scott later published a detailed post explaining his perspective. He walked through what happened, why he responded the way he did, and how he sees maintainer responsibility. Whether people agreed or not, the post was long, specific, and clearly meant to set the record straight.

At this point, most people assumed the cycle was complete. Internet debate, personal explanation, everyone moves on. That assumption lasted about five minutes.

Act Three: Ars Technica Enters

Ars Technica then published a piece covering the controversy. The article summarized the pull request, the backlash, and Scott’s response. They wrote it up for a much bigger audience. This wasn’t just dev Twitter arguing about AI. It was on a major tech publication.

But then the internet did what the internet does. They opened Scott’s post in one tab, the Ars article in another, and compared the quotes.

Spoiler alert: they did not match.

The quotes did not appear in the linked source. They also sounded different from Scott’s writing style, which raised eyebrows. In a follow-up, Scott mentioned that his site is configured to block automated scraping. People connected the dots.

Act Four: The Article Becomes The Story

And just like that, the convo changed again. It was no longer just about the PR or Scott’s post. It was about the accuracy of the Ars coverage. Readers pointed out… issues. And suddenly the argument wasn’t about the PR anymore. It was about the article.

And then Ars Technica pulled the article. Which, honestly, felt like the final plot twist in a story that was already on season four. Now multiple layers deep. PR. Blog post. News article. News article about the blog post about the PR.

How We Got Here

The funniest part is how this entire thing just kept escalating. A code tweak turned into a culture war. That turned into a blog post. That turned into Ars Technica. That turned into Ars Technica getting dragged. You cannot make this up.

No grand moral here. Just an extremely online chain reaction. If you blinked, you missed a chapter. If you logged off for six hours (what, you have a life?), you missed a whole episode.

And somehow, this all started with a pull request about a plotting library.