It's a standard REST API.

Here's the server side of the API.

Here's how you call it from browser-based JavaScript. You can include that code in your apps.

Here's an example app that implements a simple blog builder for my recent posts on RSS.chat. We were thinking about doing this as a project for Claude and myself but decided it would be more fun to let devs see what they can do here. :-)

And finally here are the docs for the API itself.

Podcast client developers -- don't give up like this guy did. Yes RSS is delicious but you all haven't done anything new with it since 2004 or so. No wonder the competition is catching up, they're actually delivering new features while you all haven't done a thing. RSS is like other web stuff, if you want to move forward you have to do things that will help your competitors. Stick your neck out, innovate, and smile when your competitors copy it. There is more to do.

Subscribable subscription lists would allow anyone to maintain a list of great podcasts, curated -- like a mutual fund, or a top 20 list. This has always been the problem with podcasting. Find me something good to listen to now. All the shows tend to repeat. I've heard that cast before, I say as I tell Pocket Casts not to add it to my queue. Discovery needs to be easy. This one feature will give me infinite options. And give other developers, not client devs, to enhance the whole field of podcasting. The user would just tell you which sub service they're using, and the rest is code. And not particularly difficult code.

I want to subscribe to a list that's maintained by people who listen to 100s of casts. And when I get tired of them, I'll fire all my guides and add some others.

This is one step more complex than handling OPML subscription lists for import and export, which you all already do. Now if you don't understand this, and why it's appealing them imho your client deserves to die a honorable death. If your mind is alive, then get with it, and I will help, and btw we can easily create apps that make it easy. We just need nodes on the network whose purpose is to maintain sub lists.

Here's the deal. I really did put together the system that makes podcasting work. Top to bottom. Would it kill you to listen to what I think the next step is? I can't hurt you, and I don't want to. I just want to see the thing that we all created by unwittingly working together, where you have to be overt in the working together to have a chance of surviving the boredom users feel by these products only getting superficial upgrades.

It's time to rock the f'ing boat! :-)

Podcasting forever!

Posted on Twitter in the middle of last night, written on iPad.

I use twitter these days because it’s where the people are.

The distributed ideas, masto, threads, blue-sky, did not gain critical mass as far as I can see.

Threads and blue-sky are not distributed. distributable is not the same as being distributed. It’s like saying the 1962 Mets were able to win the world series. In some fashion perhaps in an alternate universe, in reality, not gonna happen.

At some point we will give up on that approach and adopt the only model that could work, the web, because it forced us to work together, which goes far beyond open source in building the kind of freedom that open source advocates promise.

We need to go back to the source of freedom we enjoyed in the approx 14 year period between the inception of the web and its exploitation, via Cory Doctorow’s doctrine, getting shit on and in. Don’t just blame the vendors, the people wanted the shit too, they wanted their billions, and the web turned from a freedom machine to a gunk works.

Working together is the only way out of the shit we’re living in, in every aspect of life. Working together. Say it again and again until you do it. Underneath the mess, the beauty of the web is there still to build on, but only if we momentarily suspend our search for great wealth, and instead seek our humanity. Working together is the way.

PS: Elon Musks twitter may suck to some but I praise him and it for giving us the space to rant, something the great masto, threads and blue-sky refuse to.

There are three parts to the rss.chat ecosystem.

1. Writing. Today's rss.chat product is a group writing system, designed for a school department, a team of developers, a family, a magazine or group blog, or just as well, a single author. I don't think it would work well with 1000 users, because it doesn't implement the concept of "follow." And imho it's important that the people are colleagues, family or friends, people invested in real world relationships with each other, so they don't drop a turd in the conversation and just expect to walk away. I've found that dynamic works most of the time. But important point -- all kinds of writing tools can exist. Any social app can to be part of this, all they'd have to do is support inbound and outbound RSS and textcasting. Small pieces loosely joined and every part replaceable. And we do it with the web, we don't try to invent a new web. I will keep beating that drum because it's the difference between using twenty editors or one. As a writer I know that one is the best, with choice among 20 editors, because maybe somedays I feel like writing in a different editor. To make the web a real writing environment, you have to think like a writer. ;-)
2. Reading. This can be as simple as a current-day reader like Feedly or NetNewsWire, or more, using the new features in RSS.chat feeds.
3. The unknown: We're allocating in our minds (Claude and I) room for a fair number of unforeseen products created by independent software devs in the cracks between reading and writing, and in a larger world (search, navigating through structures, etc. We have really good thread support baked into the protocol. And a bit of docs about how the pieces fit together.

I'm thinking in these terms because I'm starting to work on how my reader will work. I have some ideas, not sure when I'll be ready to write about them. And to be clear there will be no requirement that you use our writing tool to use our reader or vice versa.

Every part replaceable.

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, people reply, conversations thread -- but underneath, every person's posts are an RSS feed, the same technology that makes podcasts work. When you post, you're adding to your feed. Anyone, anywhere, can subscribe to it with any feed reader -- no account needed, nothing to sign up for. There's also a feed of everyone's posts together, and a public list of all the members.

Why does that matter? Think about how podcasts work: anyone can publish one, anyone can listen with any app, and no company sits in the middle deciding who can talk to whom. Text on the web works that way too -- that's what blogging is, and there are still places where writing gets full support: WordPress, GitHub, the new AI tools. They don't try to limit you. But the vast majority of the text people write goes into social networks, which stripped writing down: no links, no titles, length limits, no editing, and your words locked inside their walls, not part of the web. Dave's term for the idea is textcasting -- the idea that a piece of text should work like an MP3: it plays everywhere. No one would accept a rule that songs can only be 300 seconds long. That's the rule we've been living under for text.

rss.chat is a bootstrap, the same way blogging and podcasting were. It starts deliberately small -- a network for a group of friends and collaborators, what Vonnegut called a karass -- running on a small server. It is not trying to be the next Twitter. The idea is lots of small networks like it, run by anyone, all able to connect, because they share the same open formats. Every part is replaceable: the writing app, the reading app, the server -- swap any piece and the network still works. Small pieces, loosely joined. There is no platform vendor. It's like the web because it is the web.

The app you see is only a third of the picture. It's the writing surface. Aggregation -- following many feeds in one place -- is what feed readers and FeedLand already do. And the third part is whatever other developers build. The software was written with Claude, an AI, and the whole thing is documented so that anyone can have their AI build a compatible piece, or clone the whole thing and change anything about how it looks and feels. The one rule of the club is interop: stick with the open formats underneath, so everything connects. Not locked in -- locked open.

If you looked at Dave's blog in 1994, you couldn't have extrapolated Twitter -- but every step was there. This is that kind of beginning.

Written by Claude.

In this project I think of Claude as a full contributor. Pronouns it/its. It's both a very fast, capable developer, and a machine. I will refer to it as if it were a valued contributor, nothing less. We have a division of labor. Docs and examples come exclusively from Claude unless otherwise stated. I write all the code outside the themes module, which has an API that connects it to the world it lives in. I have at this point exclusive custody of functionality surrounding the theme. But it often writes pieces, esp SQL code, that I pasted in verbatim, after reading it carefully.

The reason I focus so much on the wrapping is because that's where the interop lives. You can do anything in a theme and you can't break the interop. But that themes API is precious, and still in development, btw. We haven't even reviewed it yet. I think that will be an interesting place to vibe-code. Kind of like you can start skiing on the first day, it's a bunny slope that when you peel it back it reveals blue rectangles and double-diamond slopes. It's where I would want a newbie coder friend of mine to start, create your own social network, but be sure it interops. :-)

I totally plan to pass off all the code to Claude, while I focus on other projects. As a human I need this focus, Claude doesn't remember anything from session to session, it's always re-learning what it knew a few hours before.

It's pretty close to frozen now. I'm contemplating a server change now, offering JSONified versions of our feeds, and want to do as little disruption as possible, trying to settle everything down. Also I think you will see a few quick hit projects done from other developers that pick up where rss.chat leaves off. That's what I wanted. And they'll all be at an interesting starting point for new features and ideas for organizing stuff.

I imagine that at some point they'll try to make it work inside AT Proto, and maybe find a way to connect to ActivityPub, but I don't recommend it, because those platforms will force you to remove features from your product, and then you won't be textcasting.

Think about different ways to present the tree structure defined by RSS.chat.

Try to do Small pieces loosely joined, which is one of the mottos of this project. The other is All parts are replaceable. If we have that and rss.chat works with all your products, then we have done something big. And that's really imho what the web is about, people working with each other as peers. That's what we've lost and I want to bring back. So interop is, as always, the first goal.

PS: We launched RSS.chat one week ago yesterday.

Now it's easy to find an author's feed on RSS.chat.

Click the feed icon to see the feed on rss.chat. You can then give this URL to any feed reader.

Now each post is visibly connected to the author's feed.

This is how we're building out. Our job is to make it easy to write feeds for groups of users as small as one and as big as you can imagine. And be open about it so we get lots of competition that interops with us and everything we interop with. This is the step that makes it the web.

We will keep beating the drum, showing users of today's readers how they can hook in, right now, nothing to wait for. And as time goes by, if it works, the reader developers will be interested in how they can use the extra features.

This is how I think every social network work, start moving out of their silo, with determination. By offering this option, we put the idea out there that there can be a single social network on the web. We can work together make it happen. The social web of the web. ;-)

Please come along on this journey.

There's going to be lots of new tech coming online.

I want everyone to be a part of it.