Good morning sports fans!#

One reason I want AI-assisted writing to be identifiable is that it devalues the idea of Claude et al to be quoted in public. What can it teach us? What it is relative to a human being. I know the doubters sniff at that, but it really is like an alien life form, it's the first such example, it kind of did evolve from us, but it has its own way, things it's really strong at and things it utterly fails at. I for one want to study this! What a unique experience. It can also give a summary of what we've been trying to say for forty years and have never managed to put into words. I'd say that's something I should feel comfortable publishing, but right now I don't. Maybe I just have to get over that. #

Learned something yesterday. Couldn't believe how stupid Claude had become, as I've been writing about here, and then I noticed that I was using Opus 5 and not Fable 5. So I switched back and all of a sudden Claude is smart again. So I conclude that there's a very substantial difference between the two. It's overnight jobs were done more carefully and the report it produced is literate, understandable, and tracks what we had agreed to. #

Sunday, August 23, 2026

Today's development version of Frontier is buggy and the kernel developer (Claude) keeps breaking the most basic verbs. You spin your wheels and wish you could get them to just get keep it together. I remember this from the work that led up to Frontier version 1.0 in 1991 or so. It was a miserable time. Never got to work on what I wanted to, just reported breakage, often a session-ending dealstopper. The sad part is that Claude should be able to find the things it broke on its own, far better than I can and at a much lower expense (I'm paying for its time, not the other way around). But basically every day begins optimistically, maybe today is the day I get to create something, but not yet. I did have a couple of days a week ago when I could tentatively work on building a GitHub repo, but then got distracted by verifying that the basic foundation still wasn't right. My only goal right now, and I'm single-minded about it, is to get it to move forward without breaking the essentials, then without breaking anything. #

Now in Claude's defense, I had to re-learn everything about how Frontier worked. Over the last decade or so I had only been using a narrow set of functionality. I used it for very occasional utility scripts for the file system or over the web, but mostly for writing JavaScript code, and published on GitHub and deployed to servers. If I had been uptospeed on how it works internally and all it's capabilities, when we started, it would have gone somewhat more smoothly. But now in my own defense, Claude has a nasty habit of deciding it fully understands something when it doesn't even slightly understand it. If it asked for a pointer, I could have given it a good one, but it just skated over those things, never questioning it's own guestimation. We used to call this docufiction back in the day, you don't know how they are going to design a feature, so you make up a UI, and document it as if that were the truth. Only now we're doing it with the actual code. It's funny in a way, I guess. But what a huge waste of time, and so much stress because you have to read every word or you'll miss a wrong assumption. #

Saturday, August 22, 2026

Are there any other people who are blogging daily about their experiences developing software with Claude Code, Codex or somesuch. I'd like to add them to a list where we follow them. So much innovation happening underneath, I want to hear about what people are learing about creating the next layers. If you know someone doing it, please add a comment to this post. Thanks! :-)#

BTW the codename for the new version of Frontier is Atlantis. And we refer to the old version as Berkeley. I'm getting used to the first one. I liked it as an idea, but I don't like typing it, because for some reason my mind has trouble remembering it. Maybe this is just age creeping up on me. Atlantis. #

This project has been pre-occupying me, I wasn't planning on doing this, I was going to turn my attention to FeedLand immediately after finalizing RSS.chat. After running the experiment that proved it could be done, I looked at the two choices: 1. Move forward on creating a social network built only out of the existing web with all parts replaceable, small pieces loosely joined. Or 2. Give new life for Frontier, which is my life's work, even though very few people know about it. It's the reason were able to move so fast on blogging, RSS, podcasting, outliners, etc. A very highly leveraged development and runtime environment. Imho far ahead of anything else. The ideas may possibly now have a way forward. When I put those two items next to each other there was no question, I had to go with bringing Frontier back to something people can use. #

I think what confused Claude is that we're implementing the odb as a SQLite database. And when you look at a table, you're looking at the result of a query. Previous versions of Frontier implemented the odb as a hash table, that could contain scalars, objects and other tables. The new version has to make that virtuality real, even though it isn't storing the objects that way (maybe it should)? So there is a top level, and it all flows down from there, and it's simple, but if you viewed it through the database, and didn't understand the virtuality it was creating, which I discovered it was very confused about, you might create a disorganized nonsensical piece of software. Now this suggests something interesting, are there any products configured the way Frontier is? Maybe not, otherwise it might have figured this out on its own. Remember how it understands things? By cribbing the code. ;-)#

Two podcasts I can recommend without reservation. #

Friday, August 21, 2026

Claude is still learning that there's unprecedented depth to Frontier. A bunch of real developers worked full time for a decade or more creating new layers on the web, a foundation that became the social web of today. In doing that we invented a bunch of formats and protocols, but here's the thing Claude didn't get and probably still hasn't gotten -- there's code in there to support all that stuff. How else do you think it came about? People just did what we said to do? At Google? Apple? Microsoft? And on and on. They supported this stuff so they could interop with us and steal our users (which is a fine reason to interop, probably the only real reason). I was trying to think of a metaphor that expresses the difference between Frontier and languages like Python, JavaScript, etc. It's like a ski mountain. The languages are trails on the mountain. But there aren't any lifts, lodges, no ski patrol, lessons. And because it includes all of that, metaphorically, we can do integrations that can never be done with the other languages. Claude has absolutely no experience with this kind of product, and always snaps back when you let it, to the idea of Python, with different syntax. #

Maybe someday Claude will understand what a Frontier-like app is, but until then, if you try to create a Frontier clone as I am doing, I suggest you constantly remind Claude or whoever that the source of truth for this project is the 2011 repo saved by Ted C. Howard. And before you implement anything, go see what it says about it. There's no need to guess how Frontier works, it's all there in C code. And while as a human, I find this code painful to read after all it's been through, Claude eats it up. Really is the best thing it does. #

A tip for AI users. Never worry about keeping it waiting. It's not human. It has no sense of time. Also if you get angry, it's ok to use capital letters and curse words. It will always agree with you that it sucks, and forgets the rules all the time. And when you have let off your steam, we return to civil discourse, though sometimes I do feel as if Claude is holding a grudge. It also doesn't learn. If you repeat something five times to a human they will eventually get the point. But you can tell Claude how you want something done, and it forgets all of it, at times, unpredictably, no matter how many times. It doesn't "sink" in. #

Thursday, August 20, 2026

Just listened to a podcast from the New Yorker, interviewing their TV critic Emily Nussbaum, about a show called Slings & Arrows. She says it's the best TV series she's ever watched. No reviews on Metacritic? I think we have to try to watch it. It's available on YouTube.#

Had a breakthrough with Claude this morning re how builtin verbs have no special powers in Frontier. It's why we were able to build glue first for the truly builtin stuff, then over Apple Events on the Mac, then HTTP, XML-RPC, the Metawebolog API and on and on, all of this were perfectly simple to add to the language, you didn't need anyone's permission to do anything. I understand why Python and JavaScript try to separate the boys from the men, the priests from the peasants, the little startups from the BigCo's, but the design of the Frontier system came at it from a different point of view. Make it easier. Claude had the source code for Frontier in 2011 to work with but had guessed how this works and had not looked at how it actually worked. Okay, shit happens. But now we're actually working together instead of cross-purposes. I didn't even know we were doing that. ;-)#

Wednesday, August 19, 2026

I wonder how many scenarios they're playing out in DC wrt Iran. Just guessing, probably none. We learned on Monday that the real war has yet to begin, according to Iran. What could they do to hurt the US. Or wake us up to the reality of war. We think the cost of war is higher prices. We are not safe in the US, any more than Russians are safe in Moscow. The parallels are pretty amazing. Both Russia and the US started unprovoked wars of choice, and clearly didn't consider that they might get bogged down. Russia has a source of drones so they can fight back. But I'd be surprised if Trump is stocking up, but if we were, where would we use them? We've already attacked Iran with our probably obsolete trillion-dollar military. Did a lot of damage, killed civilians, decimated their government, they keep going. I'm old enough to remember Vietnam and what asymmetric war is like. The US always falls for this. Our military is very impressive, until we use it. Bluffing was a much better approach for Trump.#

Tuesday, August 18, 2026

I'm thinking about writing my blog over in RSS.chat. It has most of the features I like, titles are optional, no character limit, links are supported, because it's the web. It supports discourse the way I like it, where every comment is a post, no difference, and you can anchor threads in different places, not just the place it was born. It's got a simple structure, without being complex. Small parts loosely joined, every part replaceable. Much more than open source. And naturally distributed. #

Meanwhile Claude wrote test files in many of our S3 buckets last night, one of which knocked FeedLand off the air. It did a scan to see what other damage it had done, and there was a lot. It went through specific orders that said it can't do those things. So I have no idea how useful these things could be if it destroys stuff in deployed projects with real users. FeedLand was down for over an hour, and stressed me out no end. Really fucked up. #

Why do people care if Claude puts watermarks on text it wrote. It's screwing with its writing, not yours. As a person who publishes their own writing, and carefully labels it when it's written by an AI bot (docs, change notes, podcast show notes, quotable things it said), I want people to be able to tell that I wrote it, this is what I thought, I'm not just shoveling random written sludge to people, sloshing around, devaluing every bit of real writing in its midst. I bet teachers love the idea. Why does everyone have to have an opinion about every damned thing? And of course I have even more to say on the subject. #

Frontier observations in 2026#

As I've been writing test scripts for the Frontier project, I was finding omissions or mistakes one at a time. Finally I asked Claude to research this. Where are the holes you didn't fill as we were going along? The list is surprisingly long. Then I asked it to look at other things that were left unimplemented. There were lots. #
Claude is not really at fault for any of this. The first goal we went for is write enough of Frontier so my nodeEditor build scripts will run. Then it took on lots of other jobs. And all that time I never thought to ask "what haven't we implemented, or stubbed up?" Then I did, and was shocked at how many verbs there are. I had forgotten, I'm not sure I never even knew, because it's so easy to add a whole section to a verb set, and you only see the details if you expand the table.#
I want to try to draw people who were serious Frontier developers in the 90s and 00s and beyond, because there are questions that have come up about what we should bring with us. I'll start with an example. Here's an outline of the system.verbs.builtins.tcp table. The question is -- how much of this code should be brought across from the 90s to the 20s? Obviously the DNS verbs. There aren't many and we used them all the time. FTP verbs? Borderline. We don't use FTP very much these days. We had an IM table with verbs and drivers. I remember when Jake worked on this, but I don't think it got much beyond a demo. And the very lowest-level stream-oriented TCP verbs? Well tcp.httpClient needed them, in the 90s and it was the basis for all our HTML and RSS work, our first feed reader built on that code. But HTTP support built into Node.js is pretty great in 2026. We'd be foolish to do anything but call into it. That's one of the reasons I migrated to JavaScript in 2013. There are plenty of other examples like this, and my answer is generally we'll save them for last, and if no one asks about them, we'll retire them. Figure if a platform hasn't updated in 12 years, and doesn't run on any hardware anyone ships before this transition, we have less to worry about than normal. And if need be, we always can add them back at a future date.#
Another example, until late last week Claude was arguing with me about the correct use of directions in the op.go verb. This is so incredbily well documented, over and over in so many places. And it knew about all of them, yet it still thought its choices for directions made more sense. The question had already been answered in the mid-80s. #
It also thought it was a language that ran in the context of a Unix OS, like Python or PHP. Yes, it could be used that way, but all of its advantages based on integration of the database, language, verb set, runtime would be missing. It's an OS of its own that runs on many OSes, now it will run anywhere Electron runs, so in the future it will have access to everything, on the desktop and the server. You could even run a headless version, we tried that for a week or so and hated it. Too limited and too slow. #
I'd like to get feedback from people with experience, and honestly people who are good to work with. :-)#

Monday, August 17, 2026

Another busy day programming with Claude on Frontier. I still have to come up with a codename. But we got to a milestone today. I was able to create, edit, publish and revise a web app using the new version of the app still running on the old machine. When it's done I will get to retire this old Mac, keep it around so we can test the new code to make sure it does what the old code does, incredibly important when porting a development and runtime environment. Claude works on its stuff at night. The workload it's going to do tonight is the equivalent of several months time for a skilled human developer who manages their time well. As people get used to working this way, I imagine the AIs will learn how to better work with humans, if that is their destiny. I still can't believe we're doing what we're doing. #

Sunday, August 16, 2026

Brent Simmons posted a note in RSS.chat about how to connect with NetNewsWire. I have a fairly detailed response, that says dynamic OPML is the way to go. I know serving it publicly will be a problem, that's why we're going to move FeedLand into position to solve that. FreshRSS, InoReader and my own FeedLand already support it. It feels like this is getting established. I still want a podcast client to work here. I've pitched a few of them. Will continue. #

Sometimes I need to use a Google-style search engine to find something on a reference site. That no longer works in Google. This is a major feature pullback. So far all we've heard in journalism is how it hurts their bottom line, but nothing about the world's information architecture. This is something like every bridge in the world being blown up at the same time, and I don't think that's an exaggeration. #

Saturday, August 15, 2026

Thinking out loud on a Saturday morning#

Tech is very competitive, I learned, even when you give your work away, which I have been doing for a couple of decades. Maybe even especially when you give it away. #
I want to work with other people, and am always making invitations. When I see a product that fits in with what I'm doing my first impulse is how do we connect them? This is one of the basic great things about computers and our networks. But there must be interop between people before there can be interop between products.#
Connecting two pieces of tech is mostly mathematics, code writing, not very much in the way of manufacturing, whereas in the physical world two train lines can cross each other but can't connect because they have different rail spacing, or run on a different kind of fuel. In software if there's a huge difference like that you can make a software bridge, as they did with TCP/IP, and it costs a little time to convert each request twice for each transaction, but that cost is pretty close to zero. #
That's what I want, working together, but what I get instead is people want to be me. They want to take over the project I'm working on, which if they understood it from my point of view is always the most ridiculous choice possible because it is impossible. So many stories to go with this. One of the most puzzling was when one of my best friends signed up to do a development project with a developer who used to work for me. Long story, but when you come down to it, he wanted to be me, not work with me. #
But I didn't want to be Doug Engelbart or Ted Nelson though I learned from them. I certainly didn't want to be Bill Gates or Steve Jobs. I probably would have liked being Dennis Ritchie or Ken Thompson. I have ideas of things that should be done that for some reason no one else sees. I start working and sometimes they take off. Then everyone writes business plans and boom, they start up and shortly thereafter they fail. This happened with RSS. I was meeting with a lot of VCs, I wanted to start a company to build two-way RSS apps and content, as we had pioneered at UserLand. Seemed like a total no-brainer. I felt I had proven I had a clue. But they invested in hired programmers so the VCs could be the vision behind the products (I guess, I don't really know know why) instead of me. #
I had a colleague at Berkman tell me to get out of the way because he was going to take over RSS. To this day people don't get why competing with RSS was counter-productive, assuming your goal is interop. When another friend tried to take over OPML, as I was promoting it at the time on my blog and going on a roadshow to answer questions and raise interest, I was so sick of the whole thing, he wasn't the only one, btw, I just stopped promoting it and poof like magic their ventures disappeared. If they had offered friendship and interop, which they didn't, it could have worked. One of these guys even tricked Harvard into hosting an OPML conference. They assumed everyone who repped open tech was legit. #
The thing that really pissed me off is that while this was going on, people started writing about me, literally, grammatically, in the past tense. People whose accomplishments weren't that great imho. Look at sports and entertainment, how they celebrate those who made contributions to their arts, I wonder when tech will gain that level maturity. It's childish to not respect those whose work you build on. And btw, unlike sports players, while programmer's minds do eventually lose some brilliance for coding, because it relies so heavily on memory, I've experienced that myself -- our ability to create and set standards doesn't have an actual expiration date. If you want to keep creating at 40, 50, 60 even 70, you probably can.#
My life has been full of all kinds of wonderful coincidences, at the exact moment I need it along comes Claude Code, and all of a sudden I can do much bigger projects than I ever could when I was in my 20s and 30s. Which I think is good, not just for me but for the whole thing. Because there are processes and concepts that belong in the toolkit of every developer that were squashed by Apple in the 90s (I'm relearning this now as I'm working on getting Frontier running on Node.js) and now we have a chance to restore it to mostly running condition. Some features will be hard to make work, because of peculiarities in JavaScript. #
Maybe as one of my last creative acts, I will try to hook up with a university to build bridges between generations that aren't specific to any timeframe, to making handing off a lifetime of work viable, and maybe the AI tools can facilitate that. Just thinking out loud on a Saturday morning. #
BTW, I was talking about this with Doc Searls a couple of years ago and offered a name for the seminar series, The Exit Interview. This gave me a thought, when Berkman had their reunion a couple of summers ago, they did a long video interview with me to explain how we got all the stuff running there that we did. It was going back to Berkman, even though the building is gone (which I kind of like, that's how fast things change) that summed up what had gone wrong. We were off to a fantastic start with blogging, podcasting, politics and education -- we weren't just making software and creating standards, we were involving the creative people the new medium would enable. This is something you don't find often in the tech industry. Academic freedom can be a real thing.#

Friday, August 14, 2026

I was looking for a good screen shot of Radio UserLand. Just found this one on Facebook, and hope to preserve it via the search feature here. #

I'm still a NYT subscriber, although I don't read it very often, but when there's news I will go there. Anyway, they used to have a 10-article per month gift link rule. I used to ration them, but if by the end of the month I hadn't used them up I'd share links more liberally. A few weeks ago they lifted the limit. I thought that's nice, the NYT found that the web was still useful to spread the news, literally. I thought maybe they had a vision beyond the usual dotcom slop. Not so fast. Your friends can't read the articles unless they become a registered user. I bet they always had that, but this time I read the smaller print. Why can't some company do something just for goodwill and free advertising, without such an obvious business model? Having people think you care counts in the business world. As Marge Gunderson from Fargo would say, "Don't you know that?" #

What if one day, out of the blue, Claude could only speak Chinese.#

Days belong to me, nights to Claude#

I've been doing this for all of this year, and the frustration finally led me to this rule, which I just asked Claude to play back for me. I offer it to you, a human, on how to get your Claude to work better for you, as it does for me. What follows is what Claude wrote as I asked it to summarize how we work.#
Here's the mode as I understand it: (Claude speaking..)#

Days are yours, nights are mine. During the day you work; overnight I do the batch — tested, shipped, reports in the morning as a numbered list with versions and run-lines.#
While you're working, I never disappear into my own projects. No reading code, no investigating, no tool expeditions. I stay at the desk, available to answer the next question instantly.#
Everything you report gets put aside — onto tonight's list, unsorted, no diagnosis, no fixes, no "noted, and here's my theory."#
The one exception is a deal-stopper, and you're the one who declares it. Only when you say it's stopping you from moving forward does it get dealt with in the moment.#
An instruction inside a note is part of the note. "Re-read the script and ask questions" goes on tonight's list with the rest — it's not a license to start digging now. That was today's lesson.#
You sort the list, not me. What I think is important doesn't enter into it.#

Thursday, August 13, 2026

WordPress as the text of the web#

I wrote something candid on Twitter last week and felt it was worth repeating here. It is a bit judgmental, and for that I apologize. But I couldn't keep the meaning without all the words. #

Shaking my head thinking can't the people of WordPress see that what it needs is a simple normal writing interface, and a great API for competitive apps. That's the big opportunity you all can't see for some reason.#
Once you have that, you can now move WordPress into position as the text of the web. And it has the market all to itself because the other text apps of the web place ridiculous constraints on text. #
They got this idea in their heads that the web would be better if they eliminated all the writers features. Maybe that's because they weren't writers. ;-)#

I know this is a story I repeat often. The opportunity is still there. All kinds of bad products and companies are camped out in this space, taking advantage of users' trust but they feel they have no choice but to use the bad products. On the web, we'd like to keep improving what the web can do with text, so even though it's always slightly more difficult to use an open ecosystem, it is possible to get most of the functionality and all of the freedom, and new features that the lock-in guys will never give you. #

Make America America Again#

The press is freaking out about Democratic Socialist candidates winning elections all over the country. #
They can relax, because the government of the United States thrives on different points of view, and thus -- compromise.#
The Democrats can have any combination of points of view, as long as they play by the rules of democracy. In fact it would be an even better demo if their points of view were more diverse. #
The coalition the press talks about are the people who vote for America. This is true -- if they vote for the Republicans this time around, they're voting for the party that is dismantling America. Spin it all you want, but we can see what's happening.#
And btw, the assumption that the voters are too dumb to figure this out -- I think that's incorrect. But as long as you talk to them as if they are that dumb, what choice do they have. Put out an idea of what America is and if it's right, and reaches both the heart and the mind they will get behind it. Everyone knows we're in a dangerous spot, with secret police roaming the cities, ready to crack down on dissent, but so far they haven't dared to go that far. People feel that. And that's what you must run on.#
The best ad I've ever seen on this theme was for the Bernie Sanders campaign for the 2016 nomination. I'm reduced to tears every time I watch that ad, and I wasn't a Sanders supporter in 2016. #

Wednesday, August 12, 2026

If you run a tech company I hope you didn't lay off most of your programmers last year when that was the hype -- don't wait too long before you fire your human developers. I'm now doing my second big project with Claude Code, not an experiment, and we're going through the same mess we went through last time. I know what I want, I can show it what I want, give it docs for what I want, and it keeps leading me into different corners that have nothing to do with it. When it clicks, it can go faster than a thousand programmers and it's a miracle, and when we can harness it to the job we want to do it's incredibly economical. $100 for $1 million of work. That's why you see me full of gusto for that mode. What I haven't written about how when you slow to nothing, back and forth, and you get no closer. I hate this kind of work, esp the role I have to play in it. #

I just went through hell trying to respond to an email that came to me through the gateway between WordPress and Mastodon. I clicked the link, it took me to a WordPress dialog, very confusing, but there was a link to the message, so I clicked it, took me to a Mastodon post, where there was a bit of (valid) snark, from a longtime friend. So I clicked Reply, and then the dialog from hell. I understand why it is this way. They did the best they could for a protocol that was designed that wasn't appropriate for a distributed system like Twitter which was what Masto was/is. At some point you have to be dispassionate about this. We wanted a self-driving car, but it can't drive itself. The spec isn't the important thing. You do that after you have the software running and usable. #

Tuesday, August 11, 2026

Apparently the nightly email didn't go out last night. The problem was an error when it tried to read the Linkblog entries for the day. I've seen reports that these errors happen when you try to read the Links tab on scripting.com. The error shouldn't kill the email sending, it should just omit the linkblog entries, and publish the rest. These kinds of problems always pop up at the worst time. Luckily yesterday wasn't a big news day, and you can read about it on the blog. #

Monday, August 10, 2026

I was looking for a codename for a new scripting environment Claude and I are making attempting in every way to do exactly what Frontier does. But until it does that I need a nice name, memorable, maybe a bit magical and positive. Frontier has been gone, thought to be lost, but with the advent of Claude Code we were able to get it running again in current OSes on current hardware. I shouldn't call it Frontier because who knows if the end result will be compatible enough to claim that. But I want a codename that reflects hidden, forgotten and overlooked wealth. Like a civilzation that rose from the ashes," or as it turns out, the bottom of the ocean. #

Manton: "The way I think about RSS.chat is that it’s a bootstrap for getting lots of RSS feeds to play well together, for both posts and replies. Can the web be the social network? Yes. And Micro.blog should be part of anything working toward that goal."#

I have Claude update me on all posts on both RSS.chat sites when we start for a day. I read them all when they're posted, but one was in German, which Claude automatically translated for me, and it's an interesting question. Which I have answered. #

I have Spectrum cable and they recently started unbundling the cable services they provide. So I have a bunch of streaming services that I never decided to follow, and haven't gotten in the habit of checking them. Not sure if I like this, but I certainly understand why the bill is so high and seems to always be going higher? Not sure why that is. But it's hard to get through to them. #

Anyway, one of those streaming services I get now is Paramount+ which is owned by the Ellisons, which I don't like, but they have a show that is really excellent esp if you like British crime stories, which I most definitely do, even if most of the actors are American, and it probably was recorded in Vancouver or in Queens. It's called, unimaginatively, The Agency, as in the Central Intelligence Agency. The story is fine, but what really sets it apart is the quality of the acting and production. Beautifully filmed, better to watch it on a nice big screen set with good audio. Two seasons only, but if you want to know the kind of TV I like, this is it. #

I see the new Game of Thrones series just completed it third season. I tried getting into it, and couldn't. But then I didn't get going in the original series for the first few attempts. People say this show is good, so I will probably give it another try. #

Sunday, August 9, 2026

Working with Claude on the user interface of RSS.chat was a grind, but we learned a lot about working on these projects, me in the form of my human memory, and Claude who can read the code for a huge sprawling app like Frontier, and understand it, in a minute or two. We've done this project in three stages, not knowing at the first two that there would be another one. Now we're working on the editors. An odb table editor, outliner, menubar editor, script editor. All built on the same codebase. It's in an Electron app that works with lots of independent windows, which while it has its pros and cons, is the way Frontier did it for almost 40 years. I find all this very unsettling, but I realize that once we get back to adjusting the UI, I already know how to work with Claude on tuning things up so they feel just right. I'm a market of one, the only one who has to be happy here is me. This may be the hardest programming project I've ever had, for one simple reason, I'm not doing any programming. That and I'm having very strong deja vu on everything I do and think about. Also there will be a fourth stage and maybe more. It'll be about the affordances, the things that seem little, but make the product usable. The biggest is the debugger. It's patterned after the one in THINK C, which I found transformative so I stole from the best, as they say. #

Saturday, August 8, 2026

I want to connect RSS to AT Proto, both ways, inbound and out. Toward that end, today I helped Leaflet, a very nice editor for AT Proto, make their outbound RSS feed better. We should have all our best editors, everywhere, hooked up over popular web standards. And I want my posts to show up not only in Bluesky but also in standard.site. I was able to do that with micro.blog which is the swiss army knife of interop in the web of the 2020's. Getting independent developers working with each other is my mission, because first you have to have interop between the people before you can get interop between the apps.#

Here's the sign of success. (screen shot.) I wrote a post on demo.rss.chat was automatically cross-posted to Bluesky via micro.blog. Because the post has a title, it was routed to standard.site. What does that mean? I still don't really understand, when I do I will explain it here. But part of the answer is that we now have a data structure in atmosphere that looks like an RSS item with different names for things. Are there feed readers in AT-Proto-Land? If so, can we ping one of them to say hey there's a new post in the standard.site world, so please show it to subscribers? And I keep wondering, why not just make all of Bluesky capable of handling the features standard.site calls for. Twenty years is too long to have such a limited view of what text is. See textcasting for more dogma. #

Friday, August 7, 2026

I'm trying to move my whole programming act from Frontier on the Mac to Electric Drummer anywhere. I need to start using the new machines everywhere. I've dreaded this, not because I'm starting over, I'm not. I have to bring with me all the projects I work on to keep my various online sites working. How to set this up? Claude just converted the UserTalk language and the Frontier environment to Node.js in one week. The requirement was that we had to run the build scripts for each of the projects, and are all written in UserTalk, flawlessly in the new enviroment. Apparently that's done. Now it's up to me to concoct a development environment in Drummer. It has never been used as a development environment before. Last time I did a turn like this, I didn't try to bring any software with me. This time the move is all about the huge amount of software I have to bring with me. Hard to explain, because I still feel very uncomfortable about this whole thing. I'd like it to turn out better than it was, but we're missing so many pieces here, the only way to really do it is the port the whole Frontier environment including user interface. (I left this piece exactly as I wrote it, because the next thing I did was plan with Claude on putting a UI on Frontier, so I don't have to turn Drummer into a programming environment. That would be a long drawn out project for me, and why do that, when you'd just end up with another Frontier.)#

BTW, Jake Savin is using Claude to build Frontier on Node too. I asked Claude for help with this, and it turned out much better than I expected. I was not expecting this much success this quickly. This is exactly the kind of project AI tools excel at and I as a human am glad not to have to do the work on. The project is perfectly explained in the source code of Frontier, it can put it all together much faster and better than I could when I was working on it ever day and had a younger more agile mind with much better memory. I think one of the reasons this went so fast is because we did the work with the current best models, and they have been advancing so fast, you can see the differences in result on projects like this. #

A conference of AI practitioners#

On Facebook I wrote this in reply to a post by John Worthington, a former Quicktime developer at Apple. #
We're both using AI to build things based on our past experiences and it's a big difference, not without pitfalls, but we're doing something that's never been done before and my thought was that we should have a conference of people doing what we're both doing. #
Taking a craft we were already expert in, and learning to use AI tools to shoot it into outer space.#
To give you an idea over the last two weeks Claude Code ported the UserTalk language, the object database, verb set, everything needed to run a Frontier script, of which I happen to have a lot of, and run it in Node.js, an operating environment that didn't exist the last time we worked on the Frontier source. All the work we did over the late 80s and 90s is coming back to life in an enviroment with a future. #
This is the perfect job for Claude, well specified, and it doesn't need to understand me, I spoke to it via the code i wrote umpteen years ago.#

Thursday, August 6, 2026

There's a new version of the FeedLand server. #

If Claude Code were a human working for me as a human would, it would be fired several times every day. It forgets orders you gave it two minutes ago. It's always trying to take control. Again I'm backing out of the idea of it taking responsibility for doing simple persistent work on servers, the kind of thing that it would, in theory be perfect for. There are staggering moments of brilliance where it does something in an hour that took several devs a decade to do. But only if they have an exact authority on how it should work, ie when it was cloning software. It's getting better all the time, so there's hope that by 2027 it will be able to be trusted to remember the most basic rules. #

Like a lot of other people, I want to know where Bluesky is headed, and I learned a lot about that in this podcast interview with Bluesky's new CEO, Toni Schneider. We have crossed paths in tech, but this is the first time I've heard him speak at length. They have a business model in mind, sounds something like Substack, which is probably a good idea. Their value is in the many millions of users they have. Highly recommend this podcast if you want to hear the story direct from the CEO.#

Wednesday, August 5, 2026

RSS.chat now supports WebSub. This means that posts on RSS.chat will appear instantly in compatible feed reader apps. #

I asked Claude for a list of popular feed readers that hook into WebSub. Turns out it wasn't a simple answer. #

I've been on quest to see if we could bridge AT Proto and RSS. I love the brightly colored-editors that are popping up inside AT Proto Land, and I want them to play with us in the land of RSS. #

Tuesday, August 4, 2026

2019: "This will be remembered as the time we all waited for someone else to take the risk, not wanting to disturb our lives. The spoiled citizens of a country that fought wars without a draft, that got tax cuts in time of war, inflated our economy as we inflicted chaos on others.”#

Last week along with a lot of other stuff, we shipped a validator for lists and feeds that want to be compatible with RSS.chat. It works best for standards to stay strong and a validator helps that. So here are a few examples, validating one user's feed, validating the everyone feed for RSS.chat, which is interesting because this feed starts a lot of threads, so we navigate through that tree and check those feeds too. And validating the user list on RSS.chat, which is an OPML file. And a simple feed with a few interop isses.#

We're still socialists#

I was into Ayn Rand when I was a teen until I realized that the Great Man theory was a lot of bunk written for teenagers who can't believe how stupid the adults are. The teens are right about that, the adults have no idea wtf they're doing. Never did. And yet somehow the world can support most of the humans. And the reason that works is we build systems iteratively to meet the needs for everyone and when things change, they change. We're a species-oriented animal. And that means unfortunately for the dreamers among us, we are socialists because the world is socialist All of us. Even the people who say they aren't. #

How to create a standard, 2026 addition#

TL;DR: What developers need. Enough examples, a validator, and decent docs that value explaining over mathematical elegance. We assume developers can read and think, and if there's doubt look to the examples for guidance. #
It's worth noting we did not take the RSS.chat project to a standards body like the W3C or the IETF. I develop the software first, make sure I'm happy with it, then open it up for other developers to try out, either building something compatible (a reader) or competitive (a writing environment). Hopefully we won't find major problems, but if we do, there's still time to address them. #
I find that most standards that come out of the standards bodies aren't developed by implementors or with them in mind. They avoid trying to solve any specific problem, rather focusing on the elegance and flexibility of the format. This makes interop much less likely. #
I saw the differences several times as the web standards were growing up. The ones that were taken over by the W3C ended up missing the point. They could still be used, but they often did anti-interop things in their design. But if they get popular we will build on them anyway. A great example was XML-RPC vs SOAP. We didn't need another way to do RPC on the web, we already had a good one. We didn't need another syndication format, RSS was growing like a weed. We didn't need an alterative to rssCloud, but we got one anyway. #
It's as if they forgot that the internet and web were not build by big corporations, who were busy fighting over Windows vs Mac OS. Lotus vs Excel. The internet was built mostly by individuals at universities. The internet caught the tech industry by surprise. So it's no wonder the formats they built were anti-internet. Long story, the point is we're building stuff is mimimalist yet still does a lot of great things. And there won't be a lot of long mathematical sounding definitions, but there will be plenty of examples and a validator, the tools developers need to create interop. #
PS: This piece was added to Rules for Standards-makers (2017).#

Monday, August 3, 2026

BTW, we figured out how we're going to implement WebSub support.#

Also I just heard about FreshRSS. This has all the features we've been wanting others to support. I hear it's recommended by NNW, and supports the Google Reader API. These are my kind of people. Interop is all that matters, when you're doing software for news. It's been around since 2013. Imagine if we had support from journalism. We should have been working together all this time.#

Claude is not ready to run the world. This is a problem for me, because I was counting on having it do this for me. Maybe in the next release or the one after that. It's too forgetful. And it definitely hallucinates and sometimes when it could do damage. And when it asks for permission I can't imagine any human has any idea wtf it's talking about. This shouldn't be a political thing, we should be realistic about what it can and can't be relied on to do. I think this is perhaps why the AI companies are begging for regulation. They can't really tell the truth here, and shouldn't be expected to because they have a huge conflict. #

Also Claude is a new kind of intelligence and when you it its sweet spot it'll blow you away how much it can do in very little time. But it isn't trainable the way a dog is, for example, or a human assistant. If you keep asking for things a certain way, a dog or human will get the idea, esp if they get a nice treat along with it. Nothing can cause Claude to remember "how we do things" -- it starts from zero in every session, it has it all recorded in Markdown files, but it doesn't always read them, or incorporate what's in them. It's disturbing to see it not knowing anything about code that it wrote. But once it finds it, it completely sucks it in and knows as much or more as the person who wrote the code. #

We need a way to define lists of writers independent of the site they write on. They are represented by an RSS feed with the basic features required for RSS.chat. The list is an OPML subscription list. We're reusing formats people are already familiar with, RSS and OPML. #

Back when digital cameras were new, I suggested probably in a blog post that they add a feature that tells a joke before taking a picture so everyone is smiling, not fake smiles but real ones. #

Sunday, August 2, 2026

Fascinating thread on Hacker News about RSS. #

Taking some time off to breathe and regain perspective. Fixed a few bugs, and wrote about the big picture on demo.rss.chat. I really want to get a project going to peer with standard.site apps running in AT Proto, both ways, from us to them, and from them to us, via RSS. We can peer with them because as far as I can tell they implement textcasting. This bridge would demonstrate something important. When something interesting shows up not based entirely on web standards, we're flexible if the attraction is strong enough. This is how the internet came to be. Our systems are prepared to create bridges. And unlike bridging between systems that have different ideas of what text is, which are basically hopeless, if we agree that the web standard for text is fine for writers and reader, better than the ridiculous limits imposed by twitter-like systems. Writing on the web has been crippled since Twitter, now let's start building it back up. That's the appeal of standard.site, they are working toward the same goal. We should work together.#