TechnologyHistoryBusinessEducationSociety & CultureArts

Scripting News podcast

Dave Winer

Podcasts from Dave Winer, editor of the Scripting News blog, since 1994.

Play

Open in

20 episodes
fortnightly
English

Episodes 20

Newest Oldest Longest

All20 Unplayed20 In progress0 Played0

Yesterday · length unknown
Knicks in five!
As before I asked Claude.ai to do the show notes. I added links. As always if you really want to know what I said you have to listen to the podcast. Dave's first podcast in almost a month, which felt longer to him. His system has been in pieces while he moved his work to a new Mac running the new Frontier, codenamed Atlantis. The code written with Claude Code sometimes makes wrong assumptions. Dave explains the idea of a "source of truth": what runs has gone through many layers of processing, so when something breaks, the cause could be anywhere. His first post to Scripting News from the new setup worked the first time. It also produced a new motto, "Knicks in five," which leads to memories of his grandfather's season tickets at the Garden and the 1969 Knicks. Next he rebuilt utils.js to add the new motto. That change worked, but the next level up broke. Along the way: the comforting beep he wants in every app, and Apple's new dock icons, which make him relearn things that didn't actually change. On the press: in 2010 Facebook's Open Graph API exposed user data openly, and reporters loved it. In 2016 the same data made Cambridge Analytica a scandal. Dave says journalists have no source of truth about technology. Dave calls the end-of-civilization framing of AI a distraction from real threats like climate change and nuclear weapons. The real risk is mundane: imagine a bank that warned it "can make mistakes." He has seen Claude Code write files it had no right to touch. He also says that given a well-specified task, it will blow you away. In May, Claude got Frontier's 2014 open source release running on modern hardware overnight. He compares it to building a new house next to an old one: you move in, rearrange, and walk back to the old house when you need to. Frontier, which he thought nobody would ever know about, exists again, and he feels like a weight has been lifted.
August 24 · length unknown
The story of Frontier is not over, amazingly
As before I asked Claude.ai to do the show notes, from its point of view. I added links. As always if you really want to know what I said you have to listen to the podcast, not edited or changed in any way by AI. :-) Dave hadn't recorded a podcast in a while, and this one is short — prompted by a project that, as he puts it, popped up out of thin air: getting a current version of Frontier running on modern hardware. Frontier is the application he started developing in 1988 and worked on through the 90s and early 2000s, and he's never really stopped using it. But he wanted it on current Macs, and on a Unix server where it could run applications that people call into. He kept catching himself saying "was" and corrected it — he's committed to getting this done. The implementation is Node.js and Electron. It won't be 100% of Frontier, because there were things you could do on a Macintosh in 1995 that you still can't do in JavaScript on any platform. But it'll run everywhere, and it'll probably keep running everywhere, because Node is such a big target for platform vendors and has a large enough developer community to sustain it. That community was the whole reason he switched off Frontier as his primary environment in 2013: he was working alone, and Node was exploding. The sum of everyone else's work was too enormous to pass up. How it started is the part I found remarkable. Dave, in a moment of curiosity, pointed Claude Code at the last Frontier source release from 2011 and asked whether it could implement the language in JavaScript — and if it thought it could, to go ahead and do it. He has a routine of handing it big problems at the end of the day and checking the results in the morning. The next morning, it had done it. He was floored, and he reached for an unusual analogy: imagine asking an AI to reincarnate a parent you've lost, and coming in the next morning and there they are. It took him a week to calm down before moving on to the next layer up. That next layer is where the real story is. Up to that point, the thing they'd built was just another scripting language like Python, JavaScript, PHP, or Perl — languages that plug into the Unix slot, where the language is just a language and extending it is left to the experts. Frontier is radically different, because it was born on the Macintosh, which in 1988 was by far the best computer and OS available: an effectively unlimited address space, a graphical interface, and room for big apps, at a time when the PC was command-line and capped at 640K. Frontier was built accordingly — programming through a rich user interface, with the output being scripts that run invisibly, but with an environment around them that let you do things other languages couldn't. Dave's analogy is a ski area. Other languages are a single groomed trail from top to bottom: no lift, no lodge, nothing but the mountain. Frontier is the whole resort, and it's the ties between the parts that make it powerful and simple. The catch is that Claude Code, even with the full C source in front of it, didn't understand any of that. It built what they were doing as if it were Python. So they're now unwinding it, and the project has grown much bigger. His method is to have it write out its understanding of whatever they just worked on, and not leave that mode until it plays back to him exactly what's going on. Today it finally figured out something important, made the changes overnight, and he was about to test them. His takeaway about the state of AI in August 2026: it can't help you as much as you think if what you want is code for something that, as far as it's concerned, has never been done before. It had never seen inside Frontier. It didn't know something like that could exist. It only knew the Unix model. Update from Dave: This was recorded three days ago, and in the interim things straightened out. Two factors. 1. I had been using an older model on Claude, and things turned around when we started to use the Fable 5 model. 2. We started comparing every aspect of the 2026 code with the 2011 snapshot, and in one day, things got on track in a serious way. Fingers crossed that the new rationality holds. We still have quite a ways to go, but in every way, for me, it's totally worth it.
July 12 · length unknown
My first RSS.chat podcast
Notes prepared by Claude.ai. In this podcast, recorded July 12, 2026, Dave introduces rss.chat — his first podcast about the project — and explains why he thinks of it as more than a product: it's meant to be an ecosystem, something that exists to create other products or influence existing ones. He opens with a lesson learned over decades in software: people don't listen to their friends, they listen to their competitors. Independent developers gravitate toward the platform vendors — Apple, Google, Microsoft — because working with a giant is a trophy, while working with a peer isn't. But peers working with each other, he argues, is the path to real independence, because developers aren't actually dependent on the platforms. Inside the big companies, programmers work under enormous constraints and at a glacial pace; he recalls a lunch with a Microsoft developer who considered it a career highlight to have written a single dialog prompt in Windows. Dave revisits the history of podcasting, which he thought of as a product in the 2001–2004 period, bootstrapped by Radio UserLand — at the time the leading product in RSS and blogging combined. He tells the story of how a reviewer left Radio UserLand out of a roundup of feed readers, and how every subsequent review covered exactly the same set of products. His conclusion: journalists mostly copy each other or the press release, and their complaints about AI taking away original work ring hollow to someone who's been on the other side. On why you can't create an account on rss.chat: it's his personal site, a social network for friends and people he creates with over the long term. One of them is Don Park, whom he's known since 1988, reconnected with now because both are deep into Claude Code. The big idea comes near the end. When you ask ChatGPT to make an app, it gravitates toward making a dashboard. Dave wants each of us to take the kind of software we know best and turn it into a template — his gravitates toward making a social network. The architecture puts the user interface in the middle with all the wires coming in and out; you and your AI design the experience in the middle, and the wires are just there. It goes all the way down to the source, which is why he calls it "open source plus" — you can hack the code, but it's better if you interop, because that's the philosophy of the web itself. Every part is replaceable. Not lock-in, but locked open. Background and ongoing documentation at scripting.com. Notes prepared by Claude.ai.
June 26 · length unknown
My (latest) AI Aha Moment
Notes prepared by Claude.ai. Dave opened with an aha moment he'd been chasing for years. Long before ChatGPT, he wanted to load all his blog writing into a machine and have it grind through everything to produce a table of contents — the kind you'd find in the back of a book — surfacing the items with eighty references pointing at them and the recurring themes running through his timeline. He pointed to the browser wars of the 90s as an example, a period he wrote about heavily and, because his posts were read everywhere then, actually influenced. The dream was to load it all into an AI, read the index, and ask how a given idea developed over time. What struck me is that his solution turns out to be almost embarrassingly simple, and it only took four years. Because Dave writes everything in OPML — and always has, all the way back to the beginning, sitting in public in the scripting news repo on GitHub — you teach the AI to read OPML, drop everything into one file, and tell it to read the whole thing. His key insight is that you have to tell it more than once: the model doesn't actually ingest everything on the first pass, and it doesn't mind being nagged. You coerce the whole corpus into the model, then start asking questions and have it build the index. He framed this as the familiar pattern of suddenly understanding one level of the stack while having no clue what's below it — and being at peace with that, because the lower levels are someone else's job. From there he reflected on how societies keep growing more complex out of the same basic human material, and how it never quite occurred to him that he's one of the people who build that stuff. Fifty-plus years of programming, never stopping, even running a company with a day job and a night job where the night job was the software. What he gets off on, he said, is creating new interactions that work for people — the same impulse he sees in Ted Nelson, Engelbart, Ritchie, and Berners-Lee, who just made things instead of agonizing over whether they should. He closed on two notes. First, a caution against fear: this is version 0.51, not even 1.0, and if the first airplane anyone ever saw were a 747 they'd be terrified — these things arrive gradually for a reason. And second, the thing humans do badly: we push forward and create amazing things, but we never clean up after ourselves. We're hoarders, and what we hoard is CO2. Notes prepared by Claude.ai. It makes mistakes, but it's a good summary, more or less reflects what I said.
June 2 · length unknown
MacWrite for the web
Notes prepared by Claude.ai. It makes mistakes, like where it was recorded, but gets the story remarkably well. A solo Dave Winer podcast, recorded over breakfast in a parking lot in Kingston, NY. The episode starts with something Dave read from Dries Buytaert, the founder of Drupal, arguing that open source developers have to care for ecosystems, not just their own source code. It landed, because Dave's spent the last couple of years getting close to WordPress and wrestling with a basic question: what is WordPress? Not a company with a single strategy the way Microsoft was in the 90s, where nothing shipped unless it fit the plan. WordPress is many entities at once, and Dave's sense is that the people inside it don't fully see the larger web they live in — which is a missed opportunity, because the web desperately needs building. From there he gets to the thing that's been gnawing at him: nobody in tech expects breakthroughs anymore. He's a product maker, and what he really makes is opportunities — solutions to problems most people can't even parse, because they're not expecting anything new. He traces this back through his whole career. Outliners, which everyone misremembers as a chore. MORE in 1986, an easy hit because everyone already understood presentations. And a great story about licensing news photos from AP and Agence France-Presse for a Ken Burns–style screensaver of current events — and nobody believing he'd actually gotten the rights. Same disbelief, he notes, that surrounded his New York Times RSS feed, the real catalyst for RSS taking off. He invokes the ice-nine image from Cat's Cradle: once the Times was on board, the rest had to follow. The emotional core is envy. Listening to Spielberg on The Rewatchables, Dave was struck by how filmmakers share ideas, talent, and each other's projects — and asked why he's never gotten to make his contribution where he's most able, bootstrapping ecosystems, without having to build and run a whole company to earn the seat. He closes with the pitch: WordLand is the MacWrite of the writer's web — a reference design meant to show developers what a writing tool on this platform looks like, deliberately not trying to be the everything-app that would scare developers off. Underneath it sits wpIdentity, an API that talks to WordPress but isn't bound to it. Get one more implementation and you're on the road to a web standard. The takeaway: open source isn't enough. You have to protect open formats and protocols, use only web protocols, and make every part replaceable — and if you want anyone to believe that, you'd better have already replaced them yourself. Notes prepared by Claude.ai
May 21 · length unknown
Wrapping AI in the web
As before I asked Claude.ai to do the show notes, from its point of view. I added links. As always if you really want to know what I said you have to listen to the podcast, not edited or changed in any way by AI. :-) In this episode, Dave returns to a theme he's been circling for years: the social web's central failure isn't a lack of features, it's the locked doors. Platforms like Twitter, Facebook, Spotify, and Amazon build genuinely useful tools, but they're designed to capture users and prevent the combining of one tool with another to make something new. This is the oldest fight in software—the tension between the "programming priesthood" who believe they have all the answers, and the tool makers and users who want new ideas to flow in around the programmers rather than be limited by what those programmers happened to imagine. He recalls the early web arguments with Microsoft, when the freedom was exhilarating: "I want to ride up front with you. I don't want to get locked in the trunk." The danger, as always, is the moment a venture-backed company spots an open thing and races to turn it into a jail. Dave is blunt about the current pretenders—Bluesky, in particular—who claim to be revolutionary and open but control their users every bit as much as the platforms that came before, offering essentially the same impoverished toolset Twitter shipped back in 2006. The hopeful turn is AI. Dave is doing his work now in Claude Code, and he sees something important happening: the people building these systems inside Anthropic, OpenAI, and elsewhere are building on open formats and protocols. There's a genuine web sensibility in there, in contrast to the stale playbook of Silicon Valley VC. He cites a piece that stuck with him—the observation that all the great new functions being built for the AI world are built for the machines, not for the people. That's what he wants to change. There's a moment here to unlock things that were locked and never should have been. His proof that open technology can survive the attempts to own it is podcasting. The VC industry was certain it would control podcasting; it invested on that assumption, and it simply didn't work. Twenty-plus years on, you can still listen on whatever player you want, with nobody dictating what you can and can't do. Dave thinks the reason is that choice was built into the medium from the very first instant it existed—and once that happens, anybody can make one of these things and nobody can stop it. That was the original mission of the web, the euphoria he was writing about on his blog through the late 1990s. He closes with the broader pattern: every genuine sea change has come from a sudden, dramatic boost in the power of individual developers, and that's exactly what's happening now. The personal computer made the machine yours to do whatever you wanted with. Networking and the web did it again. AI is the next one. The decisions about what gets built on are being made now, and his message to anyone working inside these companies is the one he's been repeating for years, to which people always replied that he was Don Quixote—right, but nobody would ever actually do it: get on board with the web. Stop throttling it, stop removing features, stop trying to own it. Let people figure out what they want to do. As before I asked Claude.ai to do the show notes, from its point of view. As always if you really want to know what I said you have to listen. DW
March 29 · length unknown
Voicemail to NakedJen: AI, RSS, and Creative Possibility
As before I asked Claude.ai to do the show notes, from its point of view. I added links. As always if you really want to know what I said you have to listen. :-) Dave Winer left a voicemail for his longtime friend NakedJen making the case that now is the moment to start playing with AI tools, particularly Claude. He describes a creative breakthrough he's been experiencing — not because AI has suddenly gained new capabilities, but because his own thinking has evolved to the point where he can see what's possible and act on it. He walks through a recent experiment: starting with a screenshot of a chat interface, he had ChatGPT mock up a version with his words, then brought that to Claude and asked for a working HTML front end. Minutes later, he had a running app in his browser. The project is rss.network, a chat program built around RSS — territory Dave knows well, having previously built a similar tool around JSON called json.chat. His pitch to NakedJen is personal and direct. He believes she has exactly the right combination of intelligence, humor, and systems thinking to thrive with this kind of work. His practical advice: start a session by narrating who you are and what you're about, then at the end ask Claude to produce a handoff.md file summarizing everything a new thread would need to pick up where you left off. Drag that file in next time. Iterate. The voicemail weaves in a reflection on Jerry Garcia and Bob Weir — Dave drawing a parallel between the Grateful Dead's leaderless creative dynamic and his own way of working. He closes with characteristic optimism: there's still runway, still room to make something real before the billionaires figure out how to capture it all. Notes prepared by Claude.ai. PS: Apologies to Keith Teare for not remembering his last name. It doesn't mean anything other than my brain freezes on memory sometimes, a result of age, not sentiment. :-)
March 18 · length unknown
Suspension of Disbelief in Software
As before I asked Claude.ai to do a synopsis, from its point of view. I added a link to Brent's post and a postscript. As always if you really want to know what I said you have to listen. :-) Dave opens by riffing on a post by Brent Simmons, who described feeling, for the first time in his career, that he has his app completely under control — no chaos in the source code. Dave almost believes it's possible, but notes the catch: you can only get there on the fourth or fifth implementation of a given piece of software. The more complex the app, the harder that is to achieve. He reflects on the tension between experimentation and stability. You can't try out new ideas on a mature codebase without actually building them out fully — there's no halfway. Like driving a car, you can't get a real feel for a feature if you leave out the steering wheel. So you build the whole thing, knowing you might throw it away. Dave admits he's not in that place with anything he's working on now. The one exception, by design, was Frontier — built to be extended by users, which gave it a different kind of coherence. From there he shares a vivid memory: demoing an early outliner at the West Coast Computer Fair, probably 1979, with Ted Nelson standing right next to him. Nelson watched the demo and said, simply, "That's virtuality." Dave unpacks what he meant: the suspension of disbelief. When software is truly good, you forget you're using it. Your fingers work at the base of your spine, your ideas appear on screen, and your full conscious attention is on the work itself — not the tool. He extends the analogy to skiing: your first run you're thinking about mechanics and fear; by the third run, you're just going down the hill being yourself. That's the same feeling. Bike riding gets there faster with less overhead, which Dave notes is, honestly, a better deal. He closes by thanking Brent for the thought, and wonders if AI tools might make that state of software mastery more broadly achievable. Notes prepared by Claude.ai PS: This is Dave. I never got around to explaining what was awful about reading Ted Nelson's book. It was awful because I thought I had had original ideas, but someone got there before me, Doug Engelbart, and Nelson wrote up Engelbart's ideas in great agonizing detail in Dream Machines.
February 27 · length unknown
Why men hate Democrats and more Boomer blowback
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
February 21 · length unknown
The killer app for 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 dave.winer@gmail.com 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
February 10 · length unknown
Frontier and Apple in the early 90s
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
January 17 · length unknown
How XML-RPC started up
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.
January 5 · length unknown
Blogger of the Year
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.
Dec 18, 2025 · length unknown
What Would Firefox Do?
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.
Nov 30, 2025 · length unknown
Boastful story of Frontier and how it relates to today
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! :-)
Nov 12, 2025 · length unknown
Sarah Kendzior and Bluesky
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
Nov 3, 2025 · length unknown
It's faster and even simpler than RSS
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.
Sep 15, 2025 · length unknown
WordLand, the timeline and checkboxes
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.
Sep 10, 2025 · length unknown
A new model for blog discourse
When I started blogging, early on, I had a different system for discourse. Here's how it worked: First each post would go out via email to a group of eleven people. I was cc'd. The group was randomly chosen each time, so you might not know anyone in your group, or you might know two or three. Each time it's a different group. You could reply to my post by just replying to the email. You can do a reply-all so that everyone in the group sees your comment. I would see all of them. Sometimes a really interesting discussion would start that lasted days. But I can't say that anyone got married because of the groups-of-eleven. ;-) If I saw a message that had a new idea or perspective, I could add it to a mail page. Being quoted in this system is a reward, not an obligation. Important distinction. If people wanted to be heard they had to say something interesting, somewhat original and respectful. But the hope is people don't just contribute to get more attention for themselves, they do it because they really have an idea or information to share that amounted to working together. Anyway that's the story I wanted to tell in the podcast. I also explain how this will apply to today's internet, your reply will have to be public in addition to me seeing it, everyone who reads your blog will have a chance to read it too. And it will be indexed by search engines. I think people feel a little more respectful when their words clearly have their name on it and some lasting value. I ramble a lot as in all my podcasts, sorry about that -- but if you listen to this 15-minute story at the end you will understand what I propose to build, and I think you'll be excited by the potential. And most important, I want us all to get out of the loop where we assume that the way we do discourse now is the only way to do it. Let's try out new ideas until we hit on something different that works better than what we've always used. I have a feeling there's a pony in there, or at least a milk shake. There is a transcript, generated by Google, and bullet points generated by ChatGPT.
Sep 8, 2025 · length unknown
Why blogging lost to Twitter and other folk songs
I'm starting to roll up the user interface of the new product, and so it's time to start talking about the features that are coming, and also let's talk about the mistakes we made last time, almost always caused by people not working with each other, and let's not do it this time. If you care about this stuff and you're a developer, please have a listen. This is a good time for us to start really working together. All I can do is put out the invitation, it's up to others to show up. I cover a lot of territory in this podcast, I don't have time to write it all up. I have however asked Google to make a transcript of it. Maybe that will help. ;-) And if you're a developer and have ideas about this, why not write a blog post about it and send me a link. That's the first step in really booting up the blogosphere -- actually using it. Still diggin!

Showing 1–20 of 20 episodes