FeedCity

Over at Cosmos Malick: The Girl’s Story. 

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 on the web. Matthias is a friend, I was on his podcast last year. If people use this connection and see how it works. Then we'll get an idea of where to go next.

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 and set a pattern as we go forward. At the end I asked Claude to summarize what we agreed on, and it's more or less exactly what I was aiming at. If you're working with Claude on docs for APIs, I offer this up as open source, feel free to point your Claude at this doc. I have a vested interest, in my job I read a lot of awful API docs.

Putting themselves in customers’ shoes today, how many ads do Apple’s executives want stuck in the results when they search for an app in the App Store?

My thanks to WorkOS for sponsoring last week at DF to promote their MCP server. Debugging SSO, managing users, adjusting auth policies, configuring branding: every configuration task has lived behind a UI that only a human can drive.

The WorkOS MCP server gives agents the same access as your dashboard login. Hundreds of operations, discoverable at runtime. Connect in one command via OAuth, with scoped tokens instead of a master API key. Pass a screenshot of your marketing site and ask your agent to match the login page. If a human had to do it before, an agent can do it now. Connect your agent today.

A shipwreck with a great deal of champagne (and other things) 

I’m teaching a class this term called Four Big Books. I describe it here. 

Mapping Trump’s crypto empire on Last Week Tonight

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...

A new utility 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. In the meantime the list of stuff I want to do with RSS.chat, while much shorter than it was, still has some juicy bits in it.

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.

1. Backed into a charging station.
2. An act of terrorism (exaggerating) but I caused it, and paid for it, dented the well over right rear wheel.
3. My right side mirror was pulled off its foundation hitting the side of the garage, used duck tape to keep it going. A new one costs $1000. I like the look.
4. A deer ran in front of my car and took out the panel over the right front wheel. I was able to force the metal back in. A friend saw the car and said "hit a deer eh?" Yup.

I don't know if it accomplishes anything but to me it feels like retribution of a sort.

Asturias, June 2026.

From the video You don't need much to go on a mini photography adventure.

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

Scott Hanson has a new service that connects RSS.chat to WordPress.

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.

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, you can make anything you want out of the pieces. If we don't try to capture our users, instead we try to serve them.

This all sounds nice in theory, I imagine, but -- there's a practical side to it. I wrote about this in a comment in a thread on rss.chat repo. The key point is this, you can do what you want with the data. And if you want to build new data that includes this stuff, go right ahead. RSS is extensible. It's all about working together in a web of people, because you can't have a web of pages if the developers aren't web'd.