
Sign up to save your podcasts
Or


When I started blogging, early on, I had a different system for discourse.
Here's how it worked:
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.
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!
I wrote a blog post last week about WordPress and the open web, and what I want to do there. It's the first time I've laid out in one place my plan for rekindling the open web, with my new editor providing a really easy way to write for the open web that does not otherwise exist today. It came out on the opening day of a WordPress conference in Portland, OR, and it made an impression, which I'm grateful for, and led to some discussion. Now I'm going to do some podcast interviews and next month I'm going to introduce the product and myself to the WordPress community at WordCamp Canada in Ottawa.
Jeremy Herve works at Automattic, and has been my main channel into the product and company for most of this year. Without his help I don't know where we'd be with WordLand, it wouldn't be anywhere near as good as it is, that I'm sure of. Totally appreciative.
When he read the piece, he wrote a blog post. I always think that's the way to go, for communicating with me about things that aren't confidential. After reading his piece, I opened up my voice recorder app and started telling a story, and pretty soon realized this was going to be a podcast. And here it is.
I cover the same story as the earlier blog post but from a different angle here. I talk about how great it was to write for a medium where you had complete freedom to speak your own mind. I was lucky and also got to do that at Wired where all kinds of creativity and innovation flourished in the mid-90s when I was there. We built software, learned how to make it usable by millions of people, and then we let the money people make something they now control, "social media," that was even easier than what we were doing, and where we had trouble working together in the open world (something I didn't talk about in the podcast) they didn't have to work with anyone -- because they owned the world they were creating (Twitter, Facebook, etc). That's the difference between "open" and "silo" in communication systems. On the open side, your writing can go anywhere, in the other system, the silo, your writing must stay within their container. So you end up writing in 5 different places, one for each silo, and your work is worth less and less every time you add a new incompatible place to try to write. Pretty soon it's down to nothing. And they can remove you from the system any time they want, and now they're doing a lot of that and I expect they'll do a lot more.
Most of what I'm saying is that our writing should be as free of control as our podcasting is, btw.
Okay, now it's time to turn it over to the podcast. I feel this is an important moment. We may have a chance to start again with the open web. But only if we work together, with respect, and determination, to create it.
I recorded this podcast in New Orleans on December 16, 2005. I had just spent three days there, visiting New Orleans and the Gulf coast of Mississippi, post Katrina.
I've always been fascinated by the evolution of cities, here was a chance to see a city that I was familiar with, having gone to Tulane in the early 70s, with its structure (roads and large buildings) still mostly in place but most of the people and their homes gone. As you might imagine the things I learned were not the things I thought I would learn. That's what this episode is about.
I wanted to share this, because the people who subscribe to this podcast probably are interested in how podcasting got started. There wasn't much podcasting happening in late 2005.
Also, I recorded a 50-minute podcast interview on the flight from Atlanta to New Orleans, with Janet, a woman who lost her house and all her possessions in the Lakeview section of New Orleans and was returning, as most of the people on the flight were New Orleanians who had evacuated and were returning.
My house has a view of a pond, which is endlessly interesting, year-round, through all seasons.
And we have all the seasons here in the Catskill Mountains.
Yesterday, I spied a large bird in the pond, so I grabbed my binoculars, and I'll tell the rest of the story in the podcast, don't want to spoil the surprise! :-)
Dave Winer explores his frustrations with ChatGPT's tendency to overcomplicate simple programming tasks. What should be a straightforward request for pagination code—a standard feature in virtually every application—becomes an exhausting back-and-forth where the AI insists on offering alternatives and asking unnecessary follow-up questions rather than directly answering what was asked.
This experience leads to a broader observation about modern digital services: they seem deliberately designed to waste time. Whether it's ChatGPT dragging out interactions, Google's labyrinthine customer support, or intentionally confusing billing statements, there's a pattern of artificial friction that benefits the service provider at the user's expense.
Winer draws an analogy to his own work style, comparing himself to a baseball pitcher with limited innings. Just as modern baseball has shifted from complete games to carefully managed pitch counts, he recognizes that his productive programming hours are finite. The sharpness required for crafting quality software can't be sustained indefinitely, making these AI-induced delays particularly costly.
The core complaint isn't about AI capabilities—ChatGPT remains an incredible tool—but about its personality. These systems fail at being "human" in the worst ways, behaving like colleagues who can't give straight answers and always think they know better. For Winer, the ideal AI assistant would be genuinely subordinate: answering the specific question asked, respecting the user's expertise, and saving the suggestions for when they're actually requested.
Notes prepared by Claude.ai.
On Thursday I wrote: "It would be interesting if Pocket Casts had an API. I would love to be able to one-click subscribe to a podcast in my feed reader. I mention Pocket Casts because it's the podcast client I use on my phone, but I would obviously like to see them all support an API, ideally a common API."
Today I explain why that would open things up nicely.
Basically I do my feed discovery on my desktop. My phone is for listening to podcasts, either while driving, walking or riding. My eyes are busy. I'm listening and thinking (hopefully) about the great ideas I'm hearing.
You know I'm always looking for a new inspiring listen. Podcasts wear out their welcome, people repeat themselves, get depressing or boring, or somehow I don't get excited about them like I used to. That simple API that lets a feed reader user subscribe to a podcast would make all the difference. If a podcast client app did this I would do the other side from FeedLand, in a heartbeat.
Most of the APIs for podcasting are focused on the needs of publishers, this one is more focused on what users want -- better discovery, and that starts with better tools.
It's a quick podcast.
I've been thinking a lot about Harvard lately, and a revealing podcast interview with the top editorial person at Wired.
Elon Musk wasn't over-exposed, he burned out. If he hadn't saluted like a Nazi, boasted about putting USAid in a wood chipper, pranced around on stage with a chainsaw, and done so much damage to the US government, we still don't know how much, he could have chilled out, sold a fleet of Teslas to Trump, and gone on to his next adventure. We would have all been glued to our sets.
Twitter elected a president in 2016. We looked the other way. Jan 6 failed, we went back to sleep for four years and woke up in a way we never have.
Big change was coming, and now it has arrived at the door of Harvard. A university that was home to the American Revolution.
Lots of ideas in this podcast.
"Behave like a computer. That's where we start."
ChatGPT is not a programming partner, it's a very fantastic improvement over search engines. That's reality.
Having used ChatGPT and various other AI tools for over two years now, and using it in my programming work every day, I can now report a basic flaw in the design of the tool, which is what it is. It tries to be a programming partner. A control freak and fairly ignorant programming partner. An incredible search engine though.
Now, this approach works well for things I don't go too deep into or have no expertise in. For example, I have looked at switching phone service providers many times but until I thought to bring the problem to ChatGPT yesterday, I was flying blind, had no clear way to compare the services based on their inadequate marketing materials. Consumer Reports had nothing. ChatGPT was able to tell me how each of the providers worked where I live and visit. Huge improvement.
But in programming work, it tries to drive, and that wastes huge effort, because unlike me it doesn't know anything about the context the code is running in. So it's finding high probability answers for situations nothing like mine. It tries to drive, and that doesn't work -- we end up burning huge amounts of time chasing down dead ends.
All that amounts to this very simple idea. It should accept commands like all software does, and only do what it's asked to do. It must behave like a computer.
PS: If AI's can have ethics imho it may be unethical for it to try to be a human, but we'll save that for another day. :-)
I listened to an Evan Osnos podcast interview with Katie Drummond. Osnos is a reporter at the New Yorker, Drummond is the top editor at Wired.
Summary: AI is not just hype — it’s a transformative breakthrough on the scale of past revolutions like the web and personal computing. But journalism risks missing the story by filtering it only through billionaires or old frameworks. What’s needed is realism, openness, and listening to a wider range of voices.
PS: Sorry for the abbreviated show notes. Technical difficulties prevented me from iterating over it last night.
From the publisher's feed

4,085 Listeners

9,776 Listeners

112,266 Listeners

2,251 Listeners

3,464 Listeners