As before I asked Claude.ai to do a synopsis. I corrected one factual error (informing it, waiting for a new version, not correcting the writing). And I think it may have missed the big points of both, but I will respect its opinion. As always if you really want to know what I said you have to listen. :-)

Dave Winer responds to a recent episode of the David Frum podcast, in which Frum's guest was Tim Miller of The Bulwark. The topic that caught his attention: why young men are turning to Trump. He has thoughts, but first he has a detour to make.

The detour is MeToo. Winer remembers it vividly as a social media-enabled phenomenon that did real damage — to people's careers, to trust, to the basic norms of adult interaction. He watched friends lose everything to accusations he found implausible, and he remembers modifying his own behavior in ways he describes as "horrific." The fear was pervasive and real. He credits the movement with catching genuine predators like Harvey Weinstein, but he also remembers the stampede quality of it — the way platform dynamics allowed something that couldn't have happened before social media. He got a small, personal taste of unwanted physical contact — a forced hug from someone who'd knocked him off his bike in Manhattan — and it clarified something for him about how violation feels.

On the young men question, Winer offers no clean answer — just honest acknowledgment that their complaints about housing costs and economic lockout have merit. What frustrates him is the solution they chose. Trump, he argues, is dismantling the very things young people will need: healthcare, environmental protection, institutional stability. He closes with a characteristic mix of irritation and optimism, pointing to Minnesota as evidence that something better is still possible.

Notes prepared by Claude.ai

As with previous podcasts I asked Claude.ai to write the show notes based on a machine-generated transcript. It makes mistakes, so you have to listen to the podcast if you want to know what I really think. But it's pretty good, and will help search engines find this.

Dave Winer's Twitter account was hijacked, and the experience crystallized something he's been thinking about: AI's first killer app in tech should be customer service.

The incident unfolded quickly and confusingly. Dave received an email from Twitter claiming copyright infringement on content he himself had created, threatening to take down his account within 24 hours unless he could explain why — something that seemed to require a lawyer. While he was on his Peloton, his phone rang three times in 30 minutes with no voicemail, no caller ID, just a mysterious urgency that made him fear someone had died. Then he was locked out of the account entirely. A friend on Bluesky mentioned the same copyright notice had hit them simultaneously, confirming this was some kind of mass attack. Dave still has no idea what happened or how to fix it, and he has 63,000 followers on an account he's maintained since 2006.

The deeper frustration isn't just the hack — it's the complete absence of recourse. He pays $8 a month for Twitter Blue, yet there's no way to reach an actual human being for help. This is where his proposal gets pointed: tech companies should deploy AI not for generating content slop or automating essays, but for solving the customer service crisis they've created by refusing to hire support staff. If X really has Grok as a serious AI system, Dave argues, it could read the transcript of this podcast, cross-reference it with server logs, understand what happened, and simply restore his account by reverting the email address to [email protected] and requiring a fresh password reset.

This would be the economic benefit of AI that actually matters — fixing the broken relationship between platforms and their paying users. Dave frames it as both an immediate solution to his problem and a broader challenge to the industry: stop looking for frivolous AI applications and address the fundamental flaw in how these systems treat people.

Notes prepared by Claude.ai

As with previous podcasts I asked Claude.ai to write the show notes based on a machine-generated transcript. It makes mistakes, so you have to listen to the podcast if you want to know what I really think. But it's pretty good, and will help search engines find this. Additionally, I refer to the Think Different piece as revealing the big missing piece in web apps, the problem I hope to solve with WordLand and the competitive products that I want to encourage.

Dave Winer reaches back nearly four decades to tell the story of Frontier, his scripting system for the Macintosh, and draws a direct line from that experience to what he's working on today.

The backstory begins with Winer's company riding the Mac wave in the mid-1980s. While most developers abandoned the platform during its lean early years, his team stuck it out, kept their revenue flowing through a PC product, and were perfectly positioned when Apple removed the hardware limitations in January 1986. That loyalty paid off in relationships — Winer had contacts throughout Apple, including Jean-Louis Gassée, the top product executive just below the CEO level.

After selling his company and taking a well-deserved winter off skiing, Winer set to work on something he'd always wanted to build: a scripting system for the Mac. It was an elegant product — it added a menu to the Finder, provided a proper script editor, and made apps scriptable. He developed it with the knowledge and informal blessing of his friend at the top of Apple's product organization, who met with him regularly and gave feedback. When the demo landed in front of Apple's executives, it went well — they asked for a proposal. Winer went back with what he considered a fair deal: a per-machine license capped at $14 million, after which Apple would owe nothing. He thought it addressed their concerns directly, particularly their frustration over the ongoing royalty payments to Adobe on every LaserPrinter sold.

What came back instead was rejection — and then the revelation that Apple had an internal project all along, something called "Family Farm," a scripting system that would let users "script in English." That project eventually shipped as AppleScript, which Winer regards as technically inferior to what he'd built. The internal reaction to his proposal, he suspects, had less to do with the merits and more to do with the psychology of salaried employees who saw him as someone who shouldn't be profiting at their level. He kept developing Frontier for years afterward, building it into a much larger product than originally planned — but the moment had passed.

Now, Winer says, he finds himself in a structurally similar position. There's something missing from the web that has been missing for over 30 years: a real developer platform. Mobile has a rich app ecosystem; the web doesn't, and he thinks there's a specific, answerable reason why. The solution, as he sees it, involves an API for storage — and that's where WordPress comes in. He frames WordPress not just as a publishing tool but as a storage platform, the foundation piece that a proper web developer ecosystem has been lacking.

Notes prepared by Claude.ai

As with the previous podcast I asked Claude.ai to write the show notes. It makes mistakes, so you have to listen to the podcast if you want to know what I really think. This time it wrote it in the first person, not third person which I would have preferred. At the end I have some of my own notes. DW

This story about XML-RPC's creation in 1998 feels relevant because we're on the verge of something similar today, but this time it might go much further.

Frontier was a comprehensive scripting environment with object database, editor, debugger, and extensive verb set that provided one unified way to do things instead of JavaScript's fifty million ways. It had excellent networking capabilities and was deeply integrated for desktop publishing and magazine pre-production.

Apple felt threatened and didn't appreciate what we were doing - there was a lot of bad stuff happening at Apple, and we were part of one of the bad things that happened there. We couldn't depend on the Mac anymore and had to convert to Windows.

The core problem was communication between Mac and Windows systems with their completely incompatible networking. The solution hit me and I wrote a blog post called 'HTTP plus XML equals RPC' - a way to make everything work the same way.

Bob Atkinson from Microsoft called after reading my blog. Bill Gates was a regular reader and would forward posts around the company, asking people what they thought. This meant everyone at Microsoft was up to date on what I was doing.

We set up a meeting at Microsoft in Redmond with Bob and another programmer whose name he changed later. These were experienced Microsoft programmers who had done important projects but didn't want to become managers - they wanted to keep programming.

The spoiler: it's much easier for an independent guy like me to do something like this than for guys inside a big company. Even well-compensated programmers with big titles can't get something like this to happen inside their company.

I'd seen this before at Apple with the number two guy who wanted me to do a scripting environment because he couldn't get the Apple engineers to do it. Once Apple engineers got wind of it, they put roadblocks in our way - developers shouldn't hold back progress.

Don Box, another independent guy, joined our one or two day meeting at Microsoft. We had discussions, sketched ideas, then went back and worked. The Microsoft team sent me an example, and I questioned every detail over the phone.

Their idea of networking was radically different from mine. My idea was RPC - remote procedure calls - because every programmer understands function calls at the most basic level. Everything is a function call if you go deep enough to machine language.

They wanted objects, classes, and extensibility. I said let's go for it and documented everything immediately. I sent the document to the other three guys and never heard back from any of them - complete silence despite my follow-ups.

I published XML-RPC without their names, feeling conflicted since it wasn't entirely my creation. But we built the reference implementation in Frontier, put up a test server, and evangelized it like crazy through my widely-read blog.

Years later, it surfaced inside Microsoft as SOAP, which went to the W3C. I attended the first meeting with 100 people in the room - full-time standards people and representatives from major tech companies ensuring they were represented.

The W3C process didn't yield anything useful, whereas XML-RPC did. The problem was that within large, complicated companies, ideas couldn't stay simple - they had to accommodate everything. This was what was wrong with the tech industry being brought to the web.

The warning for today: be careful when you think 'what can go wrong?' Just because you haven't thought of a problem doesn't mean it's not there.

Notes (written by DW)

I got the name of the blog post totally wrong. It was RPC over HTTP via XML.

I sound really tense in this podcast, I needed to do it quickly, but my memory of what happens was imperfect. Didn't have the time to do all the research that's pretty much all in my blog posts in 1998.

And I did make one big mistake, but corrected it quickly. I knew what happened inside Microsoft very soon after XML-RPC was released, it was SOAP, a process I explain here. Collectively, they were just trying to recreate the networking world they all were familiar with, and trying to come up a way to bridge all the different approaches. I think we all would have done much better to skip all the W3C meetings and start to build apps on XML-RPC, and convene a meeting a year later with the developers only and figure out what we want to do next, based on actual experience using the earlier work.

XML-RPC was a seed, but even thought Microsoft internally fully understood the potential, they never built on it.

2026 to me feels similar to 1998, but as with the last time, the potential is in the web, and getting away from corporate strategies, instead following the grain of the web, and leaving it up to the companies to adapt. That can work, btw -- it happened with podcasting. But you have to be scrupulous, working for all developers, not just ones at big corporations, and empowering users, or you don't do it. ;-)

Current links

In 2019, I did an overhaul of XML-RPC website, and created a reference implementation in JavaScript, both client and server (Node.js).

XML-RPC website.

XML-RPC GitHub repo.

JSON encoding.

The original website was preserved.

As with the previous podcast I asked Claude.ai to write the show notes. It chose to write it in the third person, which is great with me. It even filled in the first name of Jack Smith, when I couldn't remember it in the podcast, so in some ways the show notes are more informative than my almost 40 minute ramble. And it misunderstands some of what I'm saying, but I left it in as-is.

The situation with Venezuela feels like a replay of Iraq - emotional, cowboy-style decision making reminiscent of George W. Bush's revenge mission for his father. This isn't how a 21st century nuclear-armed nation with a powerful economy should operate.

Trump's real estate buddies went to meet with Putin to make deals for the Trump brand, while Putin and Xi have professional teams in constant contact. The naïve plan to split the world into three pieces reflects the same 'move fast and break things' mentality that tech leaders have now abandoned.

Facebook and Zuckerberg no longer move fast and break things - their system is reliable and steady. They're efficient at achieving goals while deliberately misleading people about what they're doing. They established Threads as an alternative to Twitter, though we know who owns it unlike Blue Sky.

The naivety extends to journalists proudly publishing on Substack without checking who owns it or understanding the old saying: if you can't figure out what the product is, you're the product.

A powerful personal story about jury duty reveals how you realize 'the jury is in me' - it's an education process that never leaves you, where judge and attorneys develop you as a juror to make crucial decisions about someone's fate.

Biden is criticized as an idiot who should have disqualified Trump from running. He let the Justice Department handle it while trying to get things back to normal for four years, but Trump should have been constitutionally ineligible for insurrection.

Hakeem Jeffries is making the same mistakes as Biden - just saying Trump's actions were illegal and hoping Republicans will see the importance of legality. The Democrats aren't up to this moment, and we're running out of time.

Jack Smith's investigation and case against Trump never got heard because the Supreme Court ruled on immunity. The transcript and video were released on Christmas Day as a news dump, and mainstream media completely failed to cover it - no one at MSNBC or CNN broke their holiday to report this historic information.

David Frum gets recognition as 'blogger of the year' for his podcast where he talks about what he doesn't know - exactly what bloggers should do. The advice: keep doing what you're doing, be drawn to topics that interest you even if you don't know about them, and bring on experts to teach you.

Brian Lehrer is cited as a model - he brings on experts in areas where he's prepared but lets them teach from their full-time experience. The key is finding experts and reading lots of blogs without caring about qualifications.

Podcasting was created by the speaker and Adam Curry to be a medium open to everybody with no gatekeepers. The success means it's hard to find good stuff, so we need better discovery tools - let people be the algorithms, not opaque AI systems.

Examples of programming your own algorithm: asking ChatGPT to build RSS feed lists for NBA news without paywalls, or student newspapers at US universities. The speaker's blog at scripting.com features an innovative blog roll that's actually a feed reader.

Final advice to David Frum and others: get out of your bubble, discover people with intelligent expertise who interest you, but only do it if it feels good - learning is supposed to be enjoyable.

Dave Winer

PS: I wrote up the Blogger of the Year award on Scripting on January 6.

I asked Claude.ai to do the show notes -- something I really don't enjoy or have time for. So if this doesn't adequately describe the podcast, blame the AI. ;-)

There's tired frustration among web developers who remember Firefox's heyday. This podcast is for those who experienced Firefox's rise and understand its impact on the web.

The browser wars started with Mosaic and Netscape in the early days of the web. The Netscape IPO changed everything in tech - shifting company valuations from profit-based to potential-based metrics, marking the beginning of the tech boom.

Microsoft dominated the PC market when the web emerged as an existential threat. Bill Gates had promised years earlier to learn from minicomputer companies' mistakes - to be scrappy when disruption came for Microsoft. This led to their aggressive entry into the browser market with Internet Explorer.

Microsoft's browser strategy was smart. They created a quality browser, especially for Mac, understood the value of developer community, built developer tools and platforms like Visual Basic and ActiveX, and ultimately won the browser war against Netscape through platform integration.

Firefox emerged as a lightweight alternative to the bloated Internet Explorer, built by a small team focused on core browser functionality. It succeeded where Netscape had failed, much like Chrome would later challenge Firefox itself.

My personal history with Firefox and Mozilla involves my work on RSS development. When invited to give an RSS seminar at Mozilla, I was met with hostility. The Mozilla developers were dismissive of independent developers, asking who I was and why I was involved. This personal animus eventually led me to switch to Chrome.

Firefox faces a current crisis - dependent on Google payments for default search, with a shrinking user base leading to layoffs. The silver lining is that employees who resisted developer community engagement are gone, creating an opportunity to refocus without internal resistance.

Firefox's AI strategy is failing. They're trying to compete with AI features, but browsers should remain pure web platforms. AI doesn't belong in browsers, and Firefox can't compete with larger companies on AI integration anyway.

The solution is for Firefox to become a developer platform. Forget AI features and focus on being a fantastic platform for web app developers. Let developers grow the platform.

Firefox should create a storage service - sell accounts directly to users for $5/month, provide APIs for developers to access user files with permission, use standard file formats, and stay in the distribution and banking business rather than trying to be product visionaries.

This approach works because it solves developers' storage reselling problem, enables independent developers to focus on development, creates an ecosystem where developers convince users to buy services, and aligns with Firefox's original mission.

The only way to save Firefox is to ask 'What would Firefox do?' and then do exactly that. Return to roots as a lightweight, developer-friendly platform. Stop trying to compete where bigger companies have advantages. Focus on the unique position as an independent browser with developer focus.

I recorded this 23 minute podcast on October 31.

I didn't publish it then, but I figured at some point I would.

It's the story of how a product like Frontier comes into existence.

I had done this before, in 2020, in an oral history I did for a book a friend was writing. This podcast is how I remember it in 2025. :-)

If you want to hear how a complicated project comes together when you're developing as you're designing, which I always do -- this is for you. It takes a while to get started, and then I talk fast, and use technical terms without explaining them. Sorry for all that.

I want this kind of story told, because the folklore about how software is built or even that software is built at all, by humans, is usually wrong. It's not about invention, it's about building a new machine out of mostly pre-existing parts. Note that in the story there are zero components in the mix that we had not already perfected and commercialized. Some of them came from other developers, but most of them were remixes of themes that had appeared in earlier stories, or maybe ones that had been considered for inclusion but ended up on the cutting room floor, as in a movie editing process.

The thing about Frontier is that it made it easy for us to iterate over blogging tools when the time came to work on those. Frontier was the ideal platform for that kind of work, it's why were able to move so quickly and try out lots of approaches. But our runtime was no competition for PHP or Python with SQL. Our database wasn't written to work at that scale, unfortunately -- or a lot more of the world we use today would still be running in our environment. But the ideas persist.

Interesting sidebar not mentioned in the podcast, when we did MORE which was a really popular product on the Mac platform of the mid-late 80s, we took everything we had and put it into the product. We didn't leave a single thing out. This was because we had a devteam that could do it, and we were fairly desperate as an ongoing business just before we shipped it (1986). Apple had to loan us $400K to get to shipping! Anyway -- it worked. And that's why we called it MORE, we had no idea which if any of the features would pull people in. Turned out it was the presentations.

Anyway -- glad to finally get this out there.

Happy Thanksgiving! :-)

A short podcast about Sarah Kendzior being banned from Bluesky, and why this shouldn't be like any other such event.

We should learn, that systems like Bluesky depend on moderation, and they don't have a clear business model, and they've grown very large, and they can't afford to hire moderators who understand the difference between a line from a powerful song, and a threat.

If we want a literate web, and I desperately want that myself, it has to be made in a different way.

That's what this short podcast is about.

And to Sarah, if you hear this, I love your work. You've done here what you usually do so well, you've shown us the truth. Keep on truckin! Dave Winer

If I could grab you by the shoulders I would urge you to pay attention.

Here's a way to push news around the net that's as fast as you can imagine it being, and even simpler than RSS.

It's all about WebSockets, rssCloud and WordPress.

Would you spend a few minutes thinking about that?

Then here's a podcast for you.

Here's the blog post I wrote this morning with all the links you need to explore the sockets tech in FeedLand.

I'm in the homestretch on the next release of WordLand. This version has approximately twice as many features as the last one. Because, like Radio UserLand from long ago, it does both reading and writing. But the UI is different. It's patterned after all the twitter-like products. It answers the question -- could you do a nice social network with nothing more than RSS and WordPress. And the answer is an emphatic yes.

And of course there is no center to the RSS universe, it might have benefited from one (ask me about it) but it didn't have one. Maybe for a while it looked like Google Reader would become that, but we know what happened there.

Anyway, I explain that WordLand solves a big problem for bloggers in the 2020's. We scatter our words all over creation. And we feel bad because we feel like everything should be on our blog. But forget it, that is never going to happen. Our billionaire overlords would never allow it. But if you flip the problem around and ask -- how about if I can see all the stuff I've written on all the blogs in a timeline, where all the different sources are mixed in, most-recent first. I tried a lot of approaches out, but this is the one I kept. It works, but -- it has one flaw, my linkblog.

I explain in the podcast that sometimes the linkblog overwhelms the other stuff, linkblog items are very quick so I can do a lot of them. So in the first three days I had it I lived with this, until I had to do something about it. Here's the big idea: I made it so you can temporarily turn off any of the feeds with a simple checkbox. One click and the linkblog items are gone, another click, they're back.

Anyway I want to start talking about this, I'm warming up for October. If you have questions, let me know and maybe I can answer them. I really appreciate interest in this work, this kind of stuff is a performing art. I want to empower creative people. That's why I do this. And I need to hear how that's working from smart users who care.

A couple of notes. I was thinking about putting a screen shot in here, but on more thought, it's not ready to show yet, even as a work in progress. And sorry for the rough editing job at the end. I rambled off on another topic that I want to try again.

Links from this podcast.

Great Art on Bluesky.

Daveverse blog traditional view, and the Mastodon view. It's an amazing world of interop coming online. Lovin it.

Checkbox News. A design I've been wanting to use since 2007.

Links panel on Scripting News. A place to read the linkblog items.