Of course I love RSS. 😉

Ultimately AI will flatten out the differences in languages.

The month of July is history. A fine month. A coral reef was seeded.

The hardest thing for people to get about open systems is that if you move forward, not only do you benefit, but your competitors benefit equally. When one of them takes but doesn’t give back, that’s even worse. But you do it anyway because otherwise eventually, without interop, no one can move.

If you run your own RSS.chat instance, you can now add a menu of commands to the menubar. Details in the worknotes for today. I added a DW menu to rss.chat or demo.rss.chat.

A new validator for RSS.chat-compatible apps. Examples. The everyone feed on rss.chat. A user’s feed. The user list. A feed with issues.

Dave + Claude is far more powerful than either on their own.

Claude, as we’re finishing a project: “The diving is what makes it a test of the network, not just the file: it doesn’t take the feed’s word for anything, it goes and knocks on every door the feed points to.”

I wonder if anyone else is writing about Claude from a similar point of view. I’ve been writing commercial software since the early 80s. I slogged through this stuff at a comparative snail’s pace until early this year, when I got blasted into outer space. Now I had to learn how to make use of […]

Claude doesn’t iterate over UI design. It doesn’t have eyes or have a human mind. It can’t evaluate a design. It works best when you can present the whole design before it writes a any code. That does happen, for example when porting a product across OSes.

I’ve been saying this for decades. The Dems need touring comedians doing rallies all over the country. They can say whatever they want, call the president a commie. There’s been a comedy-gap.

Listened to this podcast interview with Andy Hertzfeld one of the lead devs on the Macintosh, he talks about his time at General Magic and Google too. His interviewers were surprised that he likes developing with AI tools. People think that developing is just coding, but that’s only part of it, and when you put […]

Our feed parser is updated to understand the new elements for RSSchat.

I want one social network with lots of branches where ideas flow in ways people want them to flow. Take the big corporations out of the middle. They have not served us well because they aren’t in the business of serving us. They can provide unique user interfaces for reading or writing. They should be […]

A new this.how page for RSS.chat. I’ll point to it from blog posts.

I am longtime friends and an admirer of Howard Rheingold, who expressed an interest in RSS.chat. I asked Claude to read my blog posts and summarize, in the third person. RSS.chat is a small social network built from the web’s own parts. It looks like a chat room or Twitter — you write short posts, […]

Morning: Today on RSS.chat we are knocking off quick hit bug fixes. We’ve been focusing on big hit examples for the last few sessions.

In my experience in software development, it’s good to start small with something useful, learn how it works before adding big new features. That’s the basic principle of bootstrapping. I thought that Mastodon, for example, took on too big a job. Same thing for the protocol behind it, ActivityPub. If you go all the way […]

Yesterday’s Scripting News was one of the most news-full days in a long time, maybe going back to the rollout of RSS 2.0 in Sept 2002. If you look at what’s there, a post about re-opening the Frontier object database format would be considered the top item on any other day, but it’s the last […]

BTW, I had no idea the WordPress connection was coming and here it is.

This is something. WordPress now supports RSS.chat in an interesting way, and it’s surprisingly deep. Once it’s crossposted a message to RSS.chat, any comment in response will be cross-posted to the comment thread of the post on RSS.chat. What’s great about this is that you never can tell what people will do when you are […]

Of course we have a feed for RSS.chat updates.

How we document APIs. We did a lot of work on API docs this morning. Claude had done a draft, which we published, and turned over to users, and on review realized it was insufficient. That was the word I used, and rolled up my sleeves, told Claude we’re going to get this stuff right […]

A frequently asked question about RSS.chat. How about adding external feeds to the timeline. Of course we thought of doing this, and even started development, you might even find some traces in the code of that attempt. The thing about bootstraps is you can’t anticipate all the questions in advance, and thus can’t have answers […]

A new utility that exports the contents of a Frontier object database into a single large JSON file. I needed this because I’m preparing to move my code editing suite to Drummer running on new Mac hardware. Took a long time to get here, but with Claude’s help the project looks possible, so we’re going […]

Many of the questions about RSS.chat center on how do we make this centralized. I don’t want this, I want feed readers to add some features and then we can connect these systems together in a million different ways. They just have to think differently about subscription lists. Not radically different, even.

Wanted to switch but nothing I tried is as great a driving experience the Model Y is. Instead I’ve had a lot of fender benders and haven’t gotten any of them fixed. Backed into a charging station. An act of terrorism (exaggerating) but I caused it, and paid for it, dented the well over right […]

New docs for the browser JavaScript interface to the RSS.chat API.

It’s what we used to call a coral reef. A deliberate attempt to get people to do more than it does. To think about the web the way it was meant to be thought of, as small pieces loosely joined, with the emphasis on small. If you have formats and protocols that connect the pieces, […]

A note to people who run WordCamp conferences. Get your feed act together. There should be a feed for each conference, and as you ramp up to the big day, the news should flow faster. Help people find other people to network with. Get ideas out that aren’t in the conference program.